RCF Lite
How it works
Understand the document chain, the checks the tooling performs and the decisions you and your agent make. These pages support evaluation of the method; they are not required to run it.
RCF Lite uses explicit documents on disk to connect shipped work to its requirements and tests. The rcf tooling checks the structure of this document chain. You and your agent judge whether it describes the right product. These five pages explain the chain, its checks and the build process.
- The chain The documents that connect product intent to a passing test, what each is for and the failures each helps prevent.
- What the referee guarantees What the tool proves and what you and your agent must judge together. Use these limits to assess the evidence.
- Coverage, trace, impact The three questions the chain can answer at any moment: is it covered, what does it trace to, and what breaks if it changes.
- The five-stage build cycle Define, Build, Review, Test, Finalise: how each work item ships, why every stage ends in a commit, and why the cycle only moves forward.
- Blueprints Pre-built implementation patterns your agent composes onto the chain at define time, with reviewed decisions and checks.
For an overview, see
the document model
in the shipped pack. For field-level authoring details, read the per-schema reference pages in the docs/ directory of @stravica-ai/rcf-schemas.