This directory is the maintained documentation source for Flow v7 and Session v5. The public overview and installation instructions live in the README.
- Positioning — what Flow is for, and when not to use it.
- What Flow guarantees — the guarantee map: which claims are enforced, attested, declared, judged, or unenforced.
- Release qualification — the published eval thresholds and the release cadence.
- Development — repository structure and verification.
- Maintainer contract — runtime and release invariants.
- Validation and review — the evidence, review, and closure invariants, split out of the contract.
- Troubleshooting — configuration and session recovery.
- ADR 0001 — the minimal-runtime direction.
- ADR 0002 — current toolchain and layer boundaries; its older lifecycle decision is superseded.
- ADR 0005 — the current simplicity-first lifecycle and its intentional tradeoffs.
- ADR 0006 — bounded host-native worker waves inside one serial durable feature lifecycle.
- ADR 0007 — reviewer-owned result submission with host-checked reviewer identity and no additional protocol.
- ADR 0008 — authority-bound host continuation, derived retry selection, source-drift freshness, and process-local timing.
- ADR 0009 — a
broadclaim vetoes review until that same command passes. - ADR 0010 — the plan declares the canonical gate, and the two claims that rested on prose are measured.
- ADR 0011 — the plan declares acceptance evidence this host cannot produce, as a command and the platform that observes it.
- ADR 0012 — acceptance evidence names the test cases whose passing is the observation, so exit zero for a skipped case discharges nothing.
- Allowed cross-layer dependencies — source ownership.
Completed implementation plans, QA-scribe case-study material, prompt labs, replay reports, causal-transport reports, and the Session v4 review/harness ADRs were removed in v6. They are repository history, not current product contracts. The bounded wave contract does not restore those systems.