Keiko runs a coding model inside a bounded repository workflow, observes each tool outcome, corrects the run from recorded facts, and finishes only when verification passes.
Keiko means deliberate practice: act, observe, correct, and practice again.
Keiko owns the model loop, repository context, typed tools, policy, session state, recovery, trace, and completion gate. A governance layer applies the same discipline to Keiko itself through quality of service and quality control.
Implemented: VS-001A — Deterministic provider, governed loop, tools, trace, verification Next: VS-001B — Real provider adapter and redacted smoke trace
uv sync --all-groups
uv run keiko self-check --jsonThe command creates a disposable Git fixture outside the current repository, completes one bounded coding task, verifies the final digest, and prints the compact run result and trace location.
The task harness controls coding work:
Task
-> Context
-> Model
-> Authorized tool
-> Observation
-> Recovery or verification
-> Terminal state
The harness governance layer controls Keiko:
QoS budgets
+ QC contracts
+ trace integrity
+ regression checks
-> release gate
QoS bounds turns, tool calls, latency, retries, context, and output. QC validates schemas, state transitions, traces, acceptance cases, and release artifacts. A running session cannot relax its own governance contract.
The current deterministic implementation completes one small task in a disposable fixture repository:
- Record a task, policy, and initial workspace digest.
- Assemble bounded repository context.
- Call one configured model provider.
- Support
read_file,apply_patch,run_command, andgit_diff. - Authorize every write and command before execution.
- Return each tool observation to the next model turn.
- Run one declared test command as the completion gate.
- Save a trace and report
completedonly for the verified final digest.
The automated suite uses a deterministic provider double. One real provider adapter is required before the slice is usable outside tests.
See VS-001.