Noise Protocol

Step 1: Define the channel contract

1. DEFINE new integration | pattern/suite selection | interoperability | authentication | PSK | zero-RTT | fallback | framing | rekey | datagram transport | migration | security review.
2. IDENTIFY initiator/responder, one-way/interactive flow, authenticated identities, prior static-key knowledge, identity-hiding requirement, replay tolerance, early payloads, transport ordering, session termination, key rotation/storage, and adversary capabilities.
3. READ Noise revision 34, especially Sections 7, 13, and 14. Treat deferred patterns as unstable and extensions as separate specifications.
4. STATE peer-authentication policy outside Noise: certificate, pinned key, allowlist, or key continuity. Static-key possession alone does not decide whether a key belongs to an acceptable peer.
5. ROUTE raw X25519/AEAD/hash implementation to a primitive specialist, Ristretto work to ristretto255, primitive vectors to wycheproof/nist-cavp, and post-handshake ratcheting to its protocol-specific guidance.

Completion: roles, authentication, secrecy/identity/replay properties, early-data policy, trust store, framing, and session lifetime are explicit.

Step 2: Inspect the integration and choose a library

RUN from the target repository root:

python3 scripts/inspect-project.py --root . --json