fau/1.
Wire contracts stay in Protocol overview and the
Wire specification. Do not treat boxes here as MUST/SHOULD.
Custody boundary
The Mac Node is where personal data is decrypted, classified, indexed, and policy-gated. Assistants reach it only through the Relay request/response path; the phone exchanges permission and preference state with the node. That left side of the vision (Assistants ↔ Relay ↔ Node + phone) is the protocol surface. Everything else in the diagram is node-local product scaffolding inside this monorepo (node/), not a reason to split into a new platform repo.
Vision → code seams
Classifier/indexer backends live under
FAU_HOME/artifacts/{classifiers,indexers}/<name>/.
Jev is an implementation detail behind the Protocol — swap with config.classify /
config.index without a protocol bump.
Channels are installable plugins (channels/ in this monorepo, entry point group
fedagent.channels) — outside the kernel package, still inside the Mac Node
trust boundary.
Suggested build order
Explicitly later
- Full Google / Apple ecosystem connectors
- Computer Use over Safari / Terminal / third-party apps
- Verifiers / Agents / Extensions as a plugin marketplace
- New repo or splitting
fedagentinto many packages - Protocol bump for channel types
Related
- Extend the codebase
- Node — normative runtime surface
- Concepts — custody invariants