Aftergraph Knowledge Plane v1.1.0 — production hardening

Aftergraph Knowledge Plane v1.1.0 — production hardening

Live: https://docs.aftergraph.org

Second production release. Builds on v1.0.0 with real section overviews,
linked Golden Mission walkthrough, SEO surfaces, and a branded 404.

Added / changed

• Real overview pages: Research (evidence-class table from the graph),
  Standards (track table + interop position), Catalog (pinned SHAs + system
  view), Company (explicit non-declarations), Developers (Diataxis hub).
• Golden Mission walkthrough: each of the 10 steps now links its owner
  page, its contract (with verified-binding checkmark from the system map),
  and the API reference.
• robots.txt with sitemap reference; branded 404 page with agent pointer
  (context packs index).
• Generated surfaces emit to dist/ only — git tree stays clean across builds
  (landed in the v1.0.0 line, hardened here).

Verification state at release

• CI green on main (all 9 gates + production smoke)
• Freshness: 8/9 CURRENT, 1 benign churn, 0 drift, 0 stale
• Production smoke: 14/14 routes passing

Aftergraph Knowledge Plane v1.0.0

Aftergraph Knowledge Plane v1.0.0 — production release

Live: https://docs.aftergraph.org

First tagged production release. A compiler/rendering/discovery layer over
canonical Aftergraph sources — repositories own truth, governance owns
boundaries, evidence owns claim strength. The plane resolves and renders;
it owns no truth.

What ships

Human surface (28 pages)

• Quickstart: verify the plane itself in 10 minutes (dogfood loop)
• Tutorials: trace a claim to its registry commit byte-for-byte; consume the plane via MCP
• How-to guides: freshness verification, explicit source adoption, MCP wiring, context packs, adding canonical sources
• Reference: 31 contract edges, C-001..C-008 claim register (verbatim audit statuses incl. STUDY-011 live reversals), glossary
• Explanation: the four clocks, compiler-not-owner, two-status projection
• Trust and Verification: 9 mechanical gates, what the plane will not do
• API reference (Scalar, from canonical OpenAPI), FAQ, Troubleshooting, Contributing, Changelog, Brand

Machine surfaces

• llms.txt + 5 scoped agent indexes (with freshness boundary)
• 27 ACC-shaped context packs (/context/, ADR-005)
• /status.json, /source-state.json, /build-manifest.json
• Read-only Docs MCP: 7 tools, stdio, build-bounded answers

Verification machinery

• 9 build gates + CRLF/private-leakage scan + 14-route production smoke
• Every page provenance-bound to owner repo@full-SHA
• Freshness policy (ADR-004): repository churn is not semantic drift; UNKNOWN never counts as CURRENT
• Scheduled verifier (6h): append-only history, immutable artifacts, auto-report adoption issues, never auto-pins
• Claims render registry-verbatim; projection can only weaken, never upgrade

Verification state at release

• CI: green on main (all gates + production smoke)
• Freshness: 8/9 CURRENT, 1 SOURCE_MOVED_CONTENT_UNCHANGED (benign churn), 0 semantic drift, 0 stale
• Production smoke: 14/14 routes passing

Verify it yourself

git clone https://github.com/Aftergraph/docs && cd docs && npm ci
npm run build && node scripts/smoke.mjs http://localhost:4321