onekeyhq/hardware-js-sdk/hardware-architecture

Hardware Architecture

1. Read the architecture overview and

current architecture decisions.

1. State the target runtime, transport, device family, protocol version, and lifecycle phase.
2. Identify the owning layer before editing:

• Protocol Session owns encoding, framing, sequencing, serialization, and link lifecycle.
• Platform transports own physical I/O and platform error mapping.
• Core owns Device lifecycle, state, public methods, events, wallet sessions, and orchestration.
• Entry SDKs select transports and expose integration APIs.

1. Map affected packages and public compatibility surfaces.
2. Reuse the closest current implementation. Do not duplicate protocol state in a transport.
3. Validate affected packages in dependency order and test both protocols when shared code changes.

Before finishing, confirm that public APIs, events, errors, package entry points, V1 behavior, and transport cleanup remain intentional.