Architecture Decision Records

How to work against this pack (engineering / build-with-quality agents start here):

The ADR pack for this repo is its living governing document in docs/ plus the ledger records below that amend it. The living doc is normative — its Invariants section is the compliance surface and its Change process section says how to amend it:

Domain	Governing document
What VisionFlow is, the static website, the canon/governance role, CI gates	../BASELINE-visionflow.md

Lookup order: governing doc → its file:line citations into code/config → the ledger records below → docs/archive/adr/ only for rationale and history — never as authority (the archive is the pre-2026-08-31 ADR-001..007 corpus, frozen precisely because it drifted from the code; see ../archive/adr/README.md for the legacy-record map).

Making a decision: copy TEMPLATE.md to ADR-NNNN-slug.md (next free number), fill the three-axis status honestly, update BASELINE-visionflow.md in the same change, and regenerate this index (node scripts/adr-index-gen.cjs docs/adr — it fails CI on invalid frontmatter).

The estate status/evidence contract defines the independent decision, implementation and activation axes and distinguishes lineage from supersession (2026-09-07).

19 record(s). Regenerate with node scripts/adr-index-gen.cjs docs/adr.

ID	Title	Date	Decision	Impl	Activation	Supersedes	Superseded by	Owner	Repo
ADR-2001	Consolidate the ADR corpus into a living baseline plus a thin ledger	2026-08-31	accepted	complete	live	—	—	DreamLab AI maintainers	visionflow
ADR-2002	Ship the website as a copy-only static build — no compiler, bundler, or WASM	2026-08-31	accepted	complete	live	—	—	jjohare	visionflow
ADR-2003	Deploy the website via the GitHub Pages artifact/deploy actions, never a gh-pages branch	2026-08-31	accepted	complete	live	—	—	jjohare	visionflow
ADR-2004	Gate diagrams on a committed light-theme baseline rendered by a vendored Mermaid; re-render only to detect drift	2026-08-31	accepted	complete	live	—	—	jjohare	visionflow
ADR-2005	Police canon self-description counts with an allowlist-anchored, substrate-sourced, fail-open drift counter	2026-08-31	accepted	complete	live	—	—	jjohare	visionflow
ADR-2006	VisionFlow is canon-only — it owns the cross-repo view and evidence-bounded maturity, never substrate implementation truth	2026-08-31	accepted	complete	live	—	—	jjohare	visionflow
ADR-2007	Bind estate closeout to decision lineage and system evidence	2026-09-04	accepted	partial	live	—	—	estate architecture maintainers	visionflow
ADR-2008	Estate health is collected nightly by CI and read, not collected, by the dream cycle	2026-09-06	accepted	complete	live	—	—	jjohare	visionflow
ADR-2009	The webgl-mesh deep is sidecar-only and leaves the nightly rotation until a browser runner exists	2026-09-07	accepted	complete	live	—	—	jjohare	visionflow
ADR-2010	The six augmentation conditions are the canon's audit lens for human judgement	2026-09-14	accepted	complete	staged	—	—	jjohare	visionflow
ADR-2011	Operator-declared task properties set the human–agent boundary, not the requesting agent's self-tier	2026-09-14	accepted	complete	staged	—	—	jjohare	visionflow
ADR-2012	The financial substrate is our own sidestr sidechains: record the decision in canon, mirror the kind registry, and retire Lightning-first and the SHA-256d-only anchoring note	2026-09-21	proposed	partial	inactive	—	—	jjohare	visionflow
ADR-2013	One corpus, one build, one gate — the sovereign corpus is ecosystem canon, authored in Obsidian and published as OKF v0.2	2026-09-22	accepted	partial	staged	—	—	jjohare	visionflow
ADR-2014	Own shared ontology capabilities in one Rust workspace	2026-10-11	accepted	partial	staged	—	—	jjohare	visionflow
ADR-2015	Separate ontology meaning from documents and presentation	2026-10-11	proposed	none	inactive	—	—	jjohare	visionflow
ADR-2016	Make Obsidian a local application of the shared ontology core	2026-10-11	accepted	partial	staged	—	—	jjohare	visionflow
ADR-2017	Admit visiontouch-rs as a private proof-of-principle haptic input study, with node grab in VisionClaw as a future integration	2026-10-17	accepted	none	inactive	—	—	jjohare	visionflow
ADR-2018	A parity claim names its comparator; the JSS plugins forge is a separate comparator, and solid-pod-rs forge features reach consumers only through a release	2026-10-19	accepted	partial	inactive	—	—	jjohare	visionflow
ADR-2019	The solid-pod-rs forge and mirror are on in shipped pods; open edit, mainnet and any follow list stay opt-in	2026-10-20	accepted	partial	inactive	—	—	jjohare	visionflow