fau/1 or user custody
guarantees.
Audience: contributors who already ran Developer getting started.
Read first
- Concepts — goals, non-goals, invariants
- Protocol overview — ownership and flows
- Wire specification — if you touch wire formats
- Security model — if you touch auth, store, or relay trust
Where code lives
Extension map
Invariants (must survive a rewrite)
From Concepts — abbreviated:- No inbox token to agents
- Relay never decrypts node-SNI TLS
- Phone decisions require device signatures (or explicit local dashboard decide)
- Push is content-free
- Resolve shapes match for known and unknown emails
- Device signatures cover full targets including query strings
- Agent nonces are single-use inside expiry
How to test
fixtures/device-vectors.json
(generator: apps/phone/scripts/gen-device-vectors.ts).
If you change tunnel frames or relay HTTP, update Wire specification
and fixtures/test-vectors.json, then run relay↔node interop tests.
Design decision discipline
When you choose a new boundary, document in the PR:- Decision
- Why
- Alternatives
- Tradeoff
fau/1.
Open questions (product / protocol)
Labeled so they are not mistaken for law — see also protocol overview:- Per-app push filtering when multiple approval apps pair to one node
- Phone-initiated device deregister API