Skip to content

Developers

Nine ways in, one rule everywhere: the plane renders truth, owning repos own it.

I want to… Start with
Verify the plane itself in 10 minutes Quickstart (all guides indexed in Examples)
Learn by walking through real traces Tutorials
Solve a specific task (adoption, MCP wiring, packs) How-to Guides
Look up exact contracts, claims, terms Reference
Understand why it’s built this way Explanation
Integrate the Work Intelligence API API Reference
Look up request/response shapes Schemas
Give an agent programmatic access Docs MCP
Point a coding agent at these docs Agent Guide
Terminal window
git clone https://github.com/Aftergraph/docs && cd docs && npm ci
npm run build # 9 gates (page count grows; see sidebar)
node scripts/freshness.mjs # pins vs live remote state
node scripts/smoke.mjs http://localhost:4321

Everything the portal renders is derivable from the pinned sources; the build fails on leakage, broken links, or provenance gaps — see Trust & Verification.

No official SDK or unified CLI ships yet — this is the honest state, not a gap in this page. Integrate today via REST (see Schemas for request shapes) or the read-only Docs MCP for agent access. The commands that do exist and are verified are this repo’s own: npm run build (9 gates), node scripts/freshness.mjs (pins vs live remotes), node scripts/smoke.mjs (route checks).

Was this page helpful?