Project Intelligence lives here.
The docs carry the full hierarchy: Project Intelligence First, Workflow Continuity as the execution mechanism, outcome-weighted judgment as proof, and memory, MCP, APIs, Sandbox, orchestration, and agent workflows as supporting surfaces.
Context, retrieval, and memory
Start from project source truth, retrieve only what the task needs, keep active work in workflow continuity, and reserve reviewed memory for durable outcomes.
Architecture
The required path and optional layers: AI client, Hosted MCP or API, Project Intelligence, Companion, Orchestrator, Sandbox, and runtime targets.
Project Intelligence
The five-question model for AI agent work: what changed, why, impact, next step, and whether it is safe to proceed.
Workflow continuity
How Project Intelligence turns into execution through Start Work Briefs, What Changed For Me, PR/MR Answer Packs, Decision Ledger, context authority, and collision risk.
PR/MR Answer Packs
The product artifact for pull requests and merge requests: what changed, impacted symbols, source links, stale warnings, tests, reviewers, and repository context.
Context Authority
The product contract for source_url, commit_sha, freshness, confidence, validation state, and stale warnings.
134-tool MCP reference
The lean agent manifest advertises 13 tools by default. The full catalog contains 134 canonical names and 134 wire definitions across specialist surfaces and compatibility aliases.
Nothing is hidden from the docs. The product can be simple at the top of the site and still expose every primitive, protocol, package, workflow, boundary, and advanced surface once a technical reader enters the documentation.
Every public docs surface, grouped by why you came here.
The pages that explain the Project Intelligence model and its supporting surfaces.
How a developer or agent starts work, resumes context, runs workflows, and keeps handoffs durable.
Client, editor, package, and SDK wiring. Hosted MCP stays the default path for agents.
Reference surfaces for software integration, authentication, and hosted MCP contracts.
The advanced surfaces that should be discoverable in docs without becoming homepage positioning.
Reviewed memory and multi-agent concepts stay available as inputs to the Project Intelligence layer.