Positioning
CARVES is not another agent. It is the project control layer around agents.
CARVES helps long-running projects keep AI work moving through a stable loop: goal, card, plan, evidence, and review. Guard checks patch boundaries, Handoff preserves continuity, Audit gathers summary evidence, Shield turns that evidence into a local self-check, and Matrix proves the chain composes.
CARVES is
What CARVES currently claims.
CARVES keeps AI-assisted project work progressing through a local control layer.
- A stable project progression architecture around existing AI agents
- A long project continuity layer for goals, boundaries, decisions, evidence, and handoff
- A set of source-first CLI tools for patch admission, handoff, audit, and local badge output
- A way to keep AI-generated project work reviewable, transferable, and auditable
- A summary-only proof chain that keeps private source, raw diffs, prompts, and secrets out by default
CARVES is not
What CARVES refuses to claim.
The public promise stays narrow so the site does not inflate local proof into certification.
- An operating-system sandbox
- A model safety benchmark
- A public certification or leaderboard
- A semantic proof that generated code is correct
Bring humans back to the console.
The current public claim is intentionally narrow. CARVES does not replace human review. It gives AI work a repeatable project progression path, keeps project memory durable enough for the next session, and makes evidence local, inspectable, and harder to inflate.