Architecture
Capability roadmap
Reconcile the original Node API plans with the consolidated library and optional applications.
Verified 16 October 2026
The original goal was a generic capability host: any app can offer services to any authorized peer while continuing to work locally. That shared communication layer is already in one P2P library. A cloud-like service still needs its own handler, policy and acceptance evidence.
Implemented in source
- P2P: stable device keys, direct and topic discovery, transactional scoped invites, named app networks, reconnect, bidirectional calls, grants, cancellation and bounded admission; optional /rpc adds typed validated procedures.
- P2P /db: experimental Autobase adapter with local writes, app-owned views, founding-writer membership controls and real convergence tests. Collaborative backup and migration remain separate work.
- P2P /sync: persisted resource manifests, data/file replication, protection checkpoints, peer-scoped status/usage, pause/resume and diagnostics.
- Personal Node: local settings, trust and quota administration, metadata export/import, and optional delegated QVAC/mock completion streaming.
- Desktop shell: operator dashboard, approval and grant controls, tray lifecycle and Bare sidecar hosting the same Personal Node.
Planned services with no built-in API
- Files and recovery: scoped list/read/range streaming, partial-data behavior, restore planning, encrypted payload/identity backups and explicit keep/delete retention.
- Status and events: a generic remote subscription service and service directory; current EventEmitter events are local.
- Compute: model listing, embeddings, vision, transcription, RAG, durable jobs and remote build workers. Completion streaming does not imply these services exist.
- Search/indexing, wallet payments/signing, stable binary artifact helpers and node federation. Existing experiments and scaffold stubs do not provide supported P2P packs.
- Cross-device onboarding and recovery UX, full schema/version negotiation and resource-level selective policies.
Consolidation decisions
The old node-core and node-caps-sync source became @unstoppable-stack/p2p and /sync; the separate client was absorbed into the symmetric runtime. The old AI pack became Personal Node internal code. Keep native AI, wallets, app schemas, renderer IPC and operator administration with their owners. Shared capability contracts belong in packages/p2p/docs; moving every host service into that dependency would not complete the missing APIs.
Specify restore with a consumer
Choose normal replication or a scoped file stream, then define missing/partial/stale data, limits and cancellation.
Define retention and identity recovery
Specify shared-resource ownership, explicit keep/delete choices and recovery evidence before claiming complete backup.
Extend the existing capability bus
Add remote events or new compute services when real consumers establish their contracts. Validate native providers and packaged UI separately.