Developer
Developer
Section titled “Developer”CARVES is not another chat-shaped coding surface. It is a local control layer for AI-generated project work.
Why it matters
Section titled “Why it matters”- It gives AI work a stable project progression path.
- It keeps long project memory through goals, boundaries, decisions, evidence, and handoff context.
- It makes results reviewable before they are accepted.
- It lets you keep using your existing agent while CARVES provides the control structure around it.
What to read first
Section titled “What to read first”- Core advantages if you need the product value first.
- Control loop if you need the project progression model.
- Guard if you want patch admission boundaries.
- Handoff if you need session continuity.
- Audit if you need local evidence discovery.
- Shield if you need G/H/A, Lite score, and badge output.
- Matrix if you need the end-to-end local proof lane.
Developer boundary
Section titled “Developer boundary”Use normal human review for any Guard review or block decision. Matrix records local proof; it does not decide that a patch should merge.