Closes soc-dec2.4 — PG4 (Public launch claims need exported proof
under docs/releases/).
Why
- All 5 AOP-CLAIM-README-* markers were narrative-only — pointing
nowhere a public reader could verify them. The A1 audit (bead
soc-waod, cycle 20) had already classified them as unverified;
PG4 is the public-evidence output layer.
- Local .agents/ notes are gitignored, so they cannot back claims
made on the public surface.
What
- docs/releases/v2.39.0-claims/README.md (NEW): manifest mapping
each AOP-CLAIM-README-* marker → evidence file + verification
gate.
- docs/releases/v2.39.0-claims/factory-context.md (NEW): backs
AOP-CLAIM-README-FACTORY-CONTEXT.
- docs/releases/v2.39.0-claims/competitive-memory.md (NEW): backs
AOP-CLAIM-README-COMPETITIVE-MEMORY.
- docs/releases/v2.39.0-claims/first-validated.md (NEW): backs
AOP-CLAIM-README-FIRST-VALIDATED (links to PG1 journey test).
- docs/releases/v2.39.0-claims/evolve-autonomous.md (NEW): backs
AOP-CLAIM-README-EVOLVE-AUTONOMOUS (links to cycle history +
LC1 work).
- docs/releases/v2.39.0-claims/autonomous-flywheel.md (NEW): backs
AOP-CLAIM-README-AUTONOMOUS-FLYWHEEL (links to G1 snapshot gate +
live σρ=0.0488 vs δ/100=0.0274).
- docs/documentation-index.md: cataloged the manifest per the
contracts-must-be-catalogued rule.
- tests/install/test-five-minute-journey.sh: shellcheck fixes
(SC2164 cd-fallback, SC2155 separate declare/assign).
Each evidence file names the repo surface backing the claim plus
the verification gate that protects it from drift. The pattern
generalizes to other public surfaces (PRODUCT.md, landing pages) —
file under docs/releases/<version>-claims/<claim-id>.md.
Companion: A1 audit (soc-waod) — discovery layer; this is the
output layer for the 5 README-scope claims.
Closes soc-dec2.1 — PG1 (First-value path 5-minute install→validated
journey).
Why
- PRODUCT.md gap: there was no measurement of whether the install→
/rpi→artifact path actually completes in 5 minutes. The narrative
claim existed; the gate did not.
What
- tests/install/test-five-minute-journey.sh (NEW): structural journey
test with 7 checkpoints (install.sh syntax, ao version, rpi skill,
quickstart skill, ao quickstart --help, skill install dir, .agents/
rpi artifact slot). Hard floor: total wall-clock < 300s.
Per-step elapsed-time logging so a regression names the slowest
step. set +o pipefail in step() prevents SIGPIPE from `head`
marking a successful upstream command as failed.
- .github/workflows/install-e2e.yml: fix `ao --version` typos to
`ao version` (the actual subcommand; --version is not a flag).
Same fix that the new test surfaced.
Current measurement: 7/7 pass in 1 second.
Companion bead: soc-dec2.1 (PG1).
Directive #1 (multi-runtime): Promote 2 runtime smoke tests from quarantine to
tests/skills/ — test-runtime-opencode-smoke.sh (install script + skill structure)
and test-runtime-claude-code-smoke.sh (plugin manifest + hooks + frontmatter).
Both standalone, no live runtime required. Remaining gap documented: Codex CLI
and live execution need external infra.
Directive #2 (install path): Add runtime execution tests to test-install-smoke.sh
— when cli/bin/ao exists, verifies `ao version`, `ao help`, and that flywheel/
goals/inject subcommands are registered. End-to-end install execution (clean env
+ network) documented as out-of-scope for local gate.
Directive #4 (knowledge lifecycle): Extend check-flywheel-lifecycle.sh with
stage 5 (citation in downstream work) — checks cross-citations between learnings,
briefings directory population, and corpus density. Soft-fail on sparse corpus;
hard-fail only when corpus is populated but citations are structurally absent.
Gate now traces 5 stages end-to-end. Live run shows 58 cross-citations found.
Boden Fuller