← RCF Lite docs

RCF Lite

How it works

The model, before the tooling. Read here to judge the method; nothing on these pages is needed to drive it.

RCF Lite keeps every piece of shipped work connected, through explicit documents on disk, to the requirement that asked for it and the test that verifies it. The documents form a chain; the rcf tooling referees the chain's structure mechanically; you and your agent supply the judgement. These five pages explain each part of that sentence.

  1. The chain

    The layers between "I want to build" and a passing test, what each one is for, and the class of failure each one closes.

  2. What the referee guarantees

    The line between what the tool proves and what you and your agent judge together. Read this to know exactly how much to trust.

  3. 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.

  4. 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.

  5. Blueprints

    Pre-built implementation patterns your agent composes onto the chain at define time: proven decisions and checks instead of blank-page invention.

For the full per-type specification your agent authors against, see the document model in the shipped pack.