The question
How do you turn an intent into a real system without losing clarity, context, evidence, and learning along the way? Working with agents makes that question more urgent. An agent executes fast, but it executes what it understood, and what it understood depends on what was written before.
The cycle
Radiant organizes the work into stages, each with its own document.
- Frame. The Project Frame records the intent, the problem, and what is out of scope. The Design Frame does the same for the experience of the people who will use it.
- Specify and plan. The Spec and the Plan describe the system and the build order. The experience specification lives in a separate document.
- Contract. Each task becomes a contract with a single observable change as its objective, the allowed scope, the expected outputs, what not to do, and how to verify it.
- Build. An agent executes the contract, and only the contract.
- Verify. Automated checks, a focused verification of what changed, a readback of the result, and an independent critique.
- Learn. What went right or wrong goes back to the place responsible for it: the contract, the template, the procedure, or the method itself.
# Radiant Task Contract Status: READY | HOLD | IN_PROGRESS | VERIFY | DONE | FAIL Risk tier: 0 | 1 | 2 | 3 ## 1. Objective Descreva uma única mudança observável. ## 6. Non-goals
Rules that apply to everything
Above the documents sits a constitution, with the method's invariants and the order of precedence when two rules conflict. It separates system design from experience design and holds that a lesson only becomes a general rule when it recurs. An isolated problem is fixed in the project where it showed up.
Updates
- First published.