Quick Start
Attach CARVES first, then let the agent run one controlled task.
Do not start with theory. Open the project folder, attach CARVES, ask the agent for a short plan, execute one bounded step, then bring evidence back for human review.
01 / Start
Create an empty folder, or open the project you want to advance.
Start where the work will actually happen. CARVES should attach to project context instead of forcing the user through theory first.
02 / Agent
Bring your AI agent into that folder.
Use the agent you already work with. CARVES is the control layer around the workflow, not a replacement for the model shell.
03 / Attach
Tell the agent: attach CARVES.
Give it the CARVES package path, for example X:\path\to\CARVES\.
The lazy path may cost a little more token because the Agent has to inspect the folder and read the initialization result.
04 / Loop
Start with one card, one plan, and one reviewable result.
Do not begin with a giant autonomous run. Pick one bounded piece of work, ask for a short plan, execute one step, then review the evidence.
Fallback
Keep a source checkout path for early testers.
If attach is not ready in your environment, run the Matrix proof lane from a source checkout and verify the summary artifact bundle.
Use this only when the attach path is not ready in your environment.
Tech
Initialize CARVES by hand.
Use the terminal when you want the shortest deterministic path.
Run this inside the project folder.
git init
X:\path\to\CARVES\carves.cmd init .Lazy
Send this to your Agent, not the terminal.
This keeps the user experience close to normal chatting: you give the CARVES package path, and the Agent decides how to initialize.
It may cost a little more token because the Agent has to inspect the folder, detect git state, run CARVES, and explain the result.
Please attach CARVES to this project.
CARVES path:
X:\path\to\CARVES\Success
What success looks like.
Seeing Initialized: True is enough for the first run.
If you want to double-check, run X:\path\to\CARVES\carves.cmd doctor.
CARVES init
Initialized: TrueLoop
Run one controlled loop first.
Do not start with a giant autonomous run.
- Keep human direction and review explicit.
- Ask for a short plan before changing files.
- Execute only one bounded step at a time.
- Inspect evidence before accepting anything.