What the mesh is, what it is becoming, and why. Implementation lives in the code repositories; the reasoning lives here. 00-GENESIS mission, engineering context, effect, and the rules that hold 01-RESEARCH investigations, before they harden into design 02-DESIGN the authoritative specification adr numbered decisions — what was chosen, and what was rejected DECISIONS.md the ledger: every decision, in the order it was taken Written for a reader who is not its author and has no access to the mesh it describes. Addresses use the documentation ranges of RFC 5737 and RFC 1918; nodes are named by role. Single initial commit by intent. The prior history came from a private repository and carried operational detail — a routable address identified as a VPN hub, real domain names, a hosting provider — which sanitising a tip commit would not have removed from the log.
31 lines
964 B
Markdown
31 lines
964 B
Markdown
# Architecture Decision Records
|
|
|
|
One file per decision, numbered, never deleted. A superseded ADR gets its status changed
|
|
and a pointer to what replaced it — the reasoning that was rejected is the expensive half
|
|
to rediscover.
|
|
|
|
## Format
|
|
|
|
```
|
|
# N. Title in plain language
|
|
|
|
- **Status:** Proposed | Accepted | Superseded by ADR-XXXX
|
|
- **Date:** YYYY-MM-DD
|
|
- **Deciders:**
|
|
|
|
## Context what is true today, with evidence
|
|
## Considered Options numbered, each with why it was rejected
|
|
## Decision what we are doing
|
|
## Consequences what follows, including what gets harder
|
|
## References code, data, prior art
|
|
```
|
|
|
|
State evidence, not assertion. "Zero of 124 modules declare `brain` as a dependency"
|
|
outranks "the dependency rule is not followed".
|
|
|
|
## Index
|
|
|
|
| ADR | Title | Status |
|
|
|-----|-------|--------|
|
|
| [0001](0001-mesh-brokers-nodes-host-agents-think.md) | The mesh brokers capabilities; nodes host; agents think | Accepted |
|