Use this page when you need one mental anchor before reading the deeper docs.

Live Code ──cx mcp────► Notes ──cx bundle────► Bundle ──cx verify────► Trusted Handoff
   │                     │                      │                      │
   │                     │                      │                      │
Hypothesis           Memory                Snapshot                 Proof
Track B              Cognition Layer       Track A                 Trust Gate

Read It Left To Right

  1. Run cx mcp when you need fast interactive help on live code.

  2. Use cx notes to preserve reasoning that should survive the current session.

  3. Run cx bundle when the work must become a reproducible artifact.

  4. Run cx verify when later humans or CI need proof instead of trust-by-habit.

Choose The Entry Point

  • Start with cx mcp when you are still asking questions.

  • Move to cx notes when the reasoning should survive the current session.

  • Move to cx bundle when the work needs a frozen handoff.

  • Finish with cx verify when a later reader should receive proof instead of a claim.

Contributor System Map

Subsystem Owning commands Primary concern Canonical doc

Live workspace surface

cx mcp, cx doctor mcp, cx audit summary

scoped live agent access

Agent Operating Model

Durable reasoning surface

cx notes, cx notes check

repository memory and cognition quality

System Contracts

Planning and artifact surface

cx inspect, cx bundle, cx validate, cx verify, cx extract

reproducible handoff and proof

Mental Model

Init and workspace bootstrap

cx init

repository-local setup and templates

Manual Overview

Configuration surface

cx.toml, cx-mcp.toml

selection, overlays, and behavior knobs

Configuration Reference

Operator examples

workflow docs and release checklist

execution over time

Operator Workflows

Read It Top To Bottom

  • MCP is the live investigation surface.

  • Notes are the durable cognition layer.

  • Bundle is the frozen snapshot.

  • Verify is the proof gate.

Learn Later