The Psyntient Node.

The Psyntient Node is the deterministic runtime that sits between applications and the Neural Vault + the Noetic Archive. Every researcher, lab, institution, and developer runs their own Node. Applications communicate with the user's Node; the Node owns the connections to the user's Vault and to the Archive.

The result is a federated architecture: computation and data ownership at the edge, collective scientific knowledge in the shared kernel.

• Local API — How on-device applications talk to the Node.
• Remote API — How remote applications and services talk to the Node.
• Vault API — Uniform access to Observation Packets, recordings, and metadata inside the user's Vault.
• Storage abstraction + Storage Drivers — Local disk, Google Drive, iCloud, Dropbox, OneDrive, Amazon S3, institutional storage, future decentralized storage — the app doesn't need to know.
• Encryption — At rest and in transit, applied consistently across every storage backend.
• Authentication — A single trust boundary shared across every application that touches the Vault.
• Provenance — Every packet carries an auditable trail — where it came from, when, and under what consent.
• Archive communication — Standardized submission, retrieval, and version-compatibility handling against the Noetic Archive.
• Networking — The transport layer that lets Nodes speak to applications and to the Archive.

• Applications never own research data. The user does.
• Build once, work everywhere. An app that speaks Node speaks to every user's Vault and, with consent, the Archive.
• Consent and provenance are architectural — not features an application has to implement itself.
• The Architect never accesses private Vaults. It only sees Observation Packets a user has explicitly published through their Node.