HQ — the mesh's own documentation

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.
2026-08-22 22:01:32 +02:00
commit cf9357e8e9
22 changed files with 2376 additions and 0 deletions
@@ -0,0 +1,16 @@
+# 01-RESEARCH
+
+Investigations that have not yet hardened into design.
+
+## Structure
+
+Each effort lives in `NNN-descriptive-name/` and **must** contain `status.md` with:
+
+- a short summary of the effort
+- who initiated it
+- the areas it touches
+- current status: `ONGOING`, `GRADUATED`, or `ABANDONED`
+
+An effort graduates by producing an ADR and a `02-DESIGN` entry. It is abandoned in
+place — never deleted. What was rejected, and why, is the more expensive half to
+rediscover.