Mythic entry, local proof
AI replaces human work. CARVES brings humans back to the console.
Let AI execute. Keep direction, plan, evidence, and final approval inside a human-controlled console.
- Agent output looks complete, but nobody knows what changed. CARVES asks for evidence before acceptance.
- The chat keeps moving, but the project direction drifts. CARVES keeps goal, card, plan, and review visible.
- The next session starts from vibes and memory fragments. Handoff keeps continuity packets for the next human or agent.
- Confidence becomes authority before anyone reviews it. Guard, Audit, Shield, and Matrix keep the local proof path inspectable.
Public Preview prep / control-loop / evidence-first
AI replaces human work.CARVES brings humans back to the console.
CARVES is not another agent. It is a local control layer for AI agent work: stable project progression, durable project memory, evidence before acceptance, and human review before the work becomes authority.
Progress
A project advancement architecture, not another chat.
CARVES turns a loose request into a visible progression loop: one bounded card, one plan, one evidence-backed result, then human review.
This keeps the project moving as a structured loop instead of collapsing into a long chat transcript.
Memory
Long project memory for large codebases.
CARVES keeps project context durable: goals, boundaries, decisions, evidence, handoff notes, and what must not be repeated.
This is engineering continuity memory, not a universal memory database.
Evidence
Every accepted result needs proof.
CARVES makes the agent bring back inspectable evidence before the human accepts the work.
The user does not have to trust that the agent sounded confident; they can inspect why the result may be accepted.
Review
The human remains the acceptance gate.
CARVES keeps accept, reject, and replan as explicit human decisions after evidence returns.
AI can execute, but it should not silently become the project authority.
Any Agent
Use the agent you already trust.
CARVES is a control layer around existing agents, not a replacement shell. The user can keep using Codex, Claude, Cursor, Copilot, or another agent.
The value is making existing agents more controllable, not forcing users to switch tools.
Local
Local-first by default.
CARVES starts from local project files and summary evidence so early users can inspect what happened before accepting the result.
The first public path should be something developers can run, inspect, and verify locally.
Local ritual, local count
0 prayers offered
We are not relying on AI. We just believe this run will land, right?
- Agent output looks complete, but nobody knows what changed. CARVES asks for evidence before acceptance.
- The chat keeps moving, but the project direction drifts. CARVES keeps goal, card, plan, and review visible.
- The next session starts from vibes and memory fragments. Handoff keeps continuity packets for the next human or agent.
- Confidence becomes authority before anyone reviews it. Guard, Audit, Shield, and Matrix keep the local proof path inspectable.