This guide is intentionally split into the two real starting points: a repo that has no existing agent instructions yet, and a repo that already has them.
cd your-repo
rkp doctorrkp initThis creates the checked-in .rkp/config.yaml, the .rkp/overrides/ directory, and the local SQLite index under .rkp/local/.
rkp status
rkp preview --host codexPreview includes unreviewed claims, but intentionally hides suppressed and tombstoned ones.
Interactive:
rkp reviewFast demo path:
rkp review --approve-all --threshold 0.95rkp apply --host claude --yesapply only writes claims in approved or edited review state.
rkp serveExample MCP client config:
{
"mcpServers": {
"rkp": {
"command": "rkp",
"args": ["serve"]
}
}
}If the repo already has AGENTS.md, CLAUDE.md, Copilot instructions, or Cursor rules, still start with init:
rkp init
rkp import
rkp statusImported claims enter as declared-imported-unreviewed, which is intentionally lower authority than executable config and CI evidence until a human reviews them.
Then continue with the same governance flow:
rkp review
rkp apply --host codex --yesrkp refresh
rkp audit
rkp preview --host copilot.rkp/
├── config.yaml # checked in
├── overrides/ # checked in
└── local/ # gitignored
└── rkp.db