Quickstart
This quickstart uses the Knowledge Plane to verify the Knowledge Plane. By the end you will have: cloned a canonical source, compared a pinned SHA against live remote state, read a provenance block, and consumed a machine-readable context pack — the exact loop every Aftergraph consumer runs.
Prerequisites
Section titled “Prerequisites”- Git, Node.js 24, and
ghauthenticated (gh auth statussucceeds). - 10 minutes.
1. Clone the plane
Section titled “1. Clone the plane”git clone https://github.com/Aftergraph/docs.gitcd docsnpm ci2. Read the source registry
Section titled “2. Read the source registry”Every canonical source is pinned at a full 40-character SHA in
src/data/sources.ts. Each pin carries owner, kind and visibility — private
repos are allowlist-blocked at build time.
cat src/data/sources.ts3. Verify freshness against live remote state
Section titled “3. Verify freshness against live remote state”node scripts/freshness.mjsOutput is one line per source:
CURRENT Aftergraph/aieSOURCE_MOVED_CONTENT_UNCHANGED Aftergraph/work-intelligence-v2Statuses follow ADR-004:
repository movement is not semantic movement — only consumed-artifact blob
changes count as content drift. UNKNOWN never counts as CURRENT.
4. Read a page’s provenance
Section titled “4. Read a page’s provenance”Open any page on docs.aftergraph.org and find the provenance block (owner · source repo@SHA · semantic version · evidence cut). It is machine-readable too:
curl -s https://docs.aftergraph.org/status.json | head -205. Consume a context pack (the agent surface)
Section titled “5. Consume a context pack (the agent surface)”curl -s https://docs.aftergraph.org/context/index.jsoncurl -s https://docs.aftergraph.org/context/standards.contract-graph.jsonEach pack carries the page’s owner, source commit, dependency contracts, related claims and freshness constraints — a portable, provenance-complete bundle (ADR-005).
6. Build and verify the gates yourself
Section titled “6. Build and verify the gates yourself”npm run buildnode scripts/smoke.mjs http://localhost:4321All nine validation gates must pass: schema, links, ownership, provenance, private leakage, OpenAPI, catalog, graph consistency, context packs.
- Tutorials — trace a claim to its registry commit
- How-to guides — adopt a moved source, wire the MCP
- Contract Graph — the governance edges