Working library with real iroh connections, not an interface sketch: - persistent device identity in state.sqlite, stable across restarts - deterministic network space derived from name + secret via HKDF-SHA256, with frozen labels and unambiguous length-prefixed encoding - replaceable discovery returning unverified candidates only; static bootstrap, in-memory test backend and a composite - real iroh connections plus an explicit mutual membership proof: HMAC-SHA256 over a role-separated transcript bound to the TLS exporter, the network id and both endpoint identities - small versioned control protocol: handshake, announcement, ping/pong - multiple networks per agent with enforced isolation - automatic reconnect with bounded backoff and jitter - mandatory state vs disposable cache, with a real directory ownership lock - status snapshots, event stream and honest diagnostics 47 integration and unit tests cover the required scenarios offline on loopback. Snapshots, revocations and WireGuard are designed for and documented, not implemented. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
6.2 KiB
AGENTS.md
Rules for anyone — human or automated — changing this repository. Read this before touching the code. Do not restate the full design here; follow the links.
What this project is
A proof-of-concept agent library for small private mesh networks. A user supplies a network name and one shared secret; agents derive the same network space independently, find each other, prove membership and exchange control messages. Scope and non-scope are in README.md.
There is no central server, no owner, no registration and no majority vote. Design accordingly: a majority is not a root of trust.
Architectural boundaries
Keep these separate. Crossing them is the main thing to review for.
- Control plane vs data plane. iroh carries control messages only. User IP
traffic is never tunnelled through it. The core must never parse a plugin's
payload — see
src/dataplane.rs. Do not advertise WireGuard as available transport before it exists; tests use an explicitly test-only capability id. - Device identity vs network identity. The iroh endpoint id is the device's
public key.
NetworkIdis derived from name + secret only. Never conflate them, and never let one change the other. - Discovery vs authentication. Discovery returns unverified candidates. It never authenticates, never carries control messages and never mutates agent state. Membership is decided only by the handshake.
- Mandatory state vs disposable cache.
state.sqliteis never silently reset: damage is a hard error.cache.sqlitemay be deleted at any time and is recreated. A stale cache must never bypass identity or network authentication. - Candidate vs observed address vs verified path. Report these as three
different things. A missing value is
None, never invented.
Rules that are not negotiable
- Tests come first. Every substantial change ships with tests for the normal path and the important failures. See docs/testing.md. Do not add tests for getters or to move a coverage number.
- Never change
IDENTITY_SCHEME, the derivation labels, or the transcript encoding insrc/identity/network.rsandsrc/proto/handshake.rswithout treating it as an incompatible protocol change. Bumping the crate version or the control protocol version must not change an existingNetworkId. - Secrets never leak. Not into logs, not into
Debug, not into status output, not into anything exported to the network.NetworkSecretand derived keys redact themselves and zeroize; keep it that way. - No panics on untrusted input. No
unwrap,expectorpanicon anything that came off the network. Clippy enforces this at warn level in the library; tests opt out explicitly at the top of each file. - Bounds before allocation. Frame lengths are checked against
Limits::max_frame_lenbefore a buffer is allocated. Every string, list and queue has a limit insrc/config.rs. - Failure is contained. A bad signature, wrong secret, malformed packet or unknown version rejects one message or one session. It never stops another network and never stops the agent. There is no irreversible global error flag. A data plane failure must never stop the control plane.
- The library owns no globals. No global tokio runtime, no global tracing
subscriber, no signal handlers, no
fork, noprocess::exit, no global mutable state. Several agents must run in one test process. - SQLite never blocks the executor. All database work goes through
spawn_blocking. Never hold a transaction or a database lock across a networkawait. When signed records land, writing the record and bumping the author's own counter must be one transaction, committed before publishing to the network. - Shutdown is bounded. A peer that stops reading must not be able to hold up shutdown. Wind tasks down with a grace period and then abort.
- Nothing from a remote announcement becomes a shell command, a filesystem path or an OS setting. The agent never touches interfaces or OS settings it did not create.
Where things live
| path | responsibility |
|---|---|
src/identity/ |
device identity; deterministic network space identity and derived keys |
src/storage/ |
state.sqlite, cache.sqlite, directory ownership lock |
src/discovery.rs |
candidate sources; test and static backends |
src/proto/ |
framing, message formats, membership handshake |
src/net.rs |
iroh endpoint adapter and observability snapshots |
src/agent/ |
agent lifecycle, per-network runtimes, sessions, events, status |
src/dataplane.rs |
the contract future IP plugins implement |
tests/ |
integration tests; tests/common/ is the shared harness |
Add abstractions only at real substitution or testing boundaries. Do not add a trait per struct. Prefer one crate with clear modules over many small crates.
Testing rules
- Use real iroh endpoints on loopback, real handshakes, real SQLite in temporary directories, and independent agent instances.
- Discovery may be substituted. iroh, authentication, message passing and persistent storage may not be.
- No arbitrary multi-second
sleepas the primary synchronisation. Wait for a specific event or condition under one overall deadline (wait_event,wait_until).settle()exists only for asserting that something did not happen. - The default suite must pass with no internet, no DHT, no public relay, no administrator rights and no changes to OS network settings. Anything needing the internet stays out of the default set.
- Running several library instances in one process is not a test of several system processes; do not describe it as one.
Before you open a change
cargo fmt --all -- --check
cargo clippy --locked --workspace --all-targets -- -D warnings
cargo test --locked --workspace --all-targets
CI runs these on Linux, macOS and Windows. A CI config existing is not evidence that tests ran on every OS — say what you actually ran.
Check the real API of the iroh version in Cargo.lock before using it. Do not
invent methods from memory.