CX Documentation

Agent-driven note mutation is a full review loop, not a single write operation: inspect through MCP first, enable mutation intentionally, write durable notes, then run cx notes check and graph review before trusting the updated cognition…​

The bundle to verify to extract path is a contract, not just a convenient command sequence.

cx needs a single front-door explanation that tells operators which surface to use before they learn the deeper internals.

The CLI command lifecycle in cx is built on yargs and a centralized command dispatch model.

Obsidian is a human navigation lens for the note graph, not the authority for repository semantics.

make test is the fast local feedback loop, make verify is the normal pre-merge gate, and make release VERSION=vX.Y.Z is the repository-local two-phase release wizard. Keeping those roles separate keeps the common command quick while maki…​

Provenance becomes convincing when shown across time instead of as a static label.

The Friday-to-Monday path is a workflow contract for turning live investigation into a trusted handoff.

The CI workflow runs on every branch push and on pull requests, but not on v* tag pushes. Tag finalization belongs to the release workflow instead of the main CI pipeline. Pages publishes the unified /schemas/ and /coverage/ site from su…​

When reviewing repository notes, use manifest-first selection and live MCP note tools instead of opening every Markdown file.

The MCP read path must remain available as the primary live exploration workflow.

The MCP test and debug cockpit is a dedicated Vitest UI entrypoint for the MCP-heavy suite, not a generic replacement for the Bun lanes. It exists so operators can rerun MCP failures interactively, inspect coverage inside the UI, and tra…​

The MCP Vitest UI troubleshooting flow is intentionally small: use the broad MCP cockpit when you need coverage and import visibility across the MCP boundary, and switch to the adversarial cockpit when the failure is explicitly about sta…​

cx uses a unified deterministic identity model but bifurcates operation into two distinct paths: Track B generates hypotheses against live state, while Track A generates proof that can survive review, CI, and handoff.

Safe note mutation is a two-part workflow: explicit authority first, graph review second.

Safe note mutation is a contract because cognition changes must stay reviewable and bounded.

cx-cli release management should separate preparation from publication. develop prepares the versioned candidate and absorbs release-fix commits until the full CI and release-assurance surface is green. The release tag then finalizes tha…​

Operator workflows should be treated as contracts when later automation depends on them.