Skip to content
runward
runward
Product
Who it is for
Trust
Documentation
News
Try it on an example Talk to us

The method

Six steps, from the idea to production.

At each step, the team decides; its agents write what was decided and what proves it, in a record kept with the code. The check reads that record again at every delivery.

  1. 01Frame
  2. 02Architect
  3. 03Ship a first version
  4. 04Evolve
  5. 05Govern
  6. 06Hand over

Step 1

Frame

Say which problem is being solved, for whom, and how success will be seen.

  • What the record holdsA one-page note (the problem, the expected value, the success criterion, what is left for later) and the steering contract.
  • Whererunward/framing.md runward/mission-contract.md
  • What the check verifiesThat the note and the steering contract exist and are filled in.

Step 2

Architect

Decide the system’s boundaries before choosing the tools.

  • What the record holdsThe architecture note, and a written, dated decision for each structural choice.
  • Whererunward/architecture.md runward/adr/
  • What the check verifiesThat the note and the documents that go with it exist and are filled in.

Step 3

Ship a first version

The smallest system that runs on real cases, with its measurements.

  • What the record holdsThe first-version measurements, set against the success criterion of the framing.
  • Whererunward/floor.md
  • What the check verifiesThat the measurements are written, and, with --strict, that the evidence they cite still exists.

Step 4

Evolve

Every change starts from an observed need, and leaves a written decision.

  • What the record holdsOne decision per change: what changes, why, and what would reopen it.
  • Whererunward/adr/
  • What the check verifiesThis step has no fixed document. With --strict, when the record cites a decision, the check verifies that it exists.

Step 5

Govern

Write down the risks and how they are handled from the start of the project, not after an incident.

  • What the record holdsThe security assessment (what can go wrong, and what is in place to avoid it), an evaluation rubric and an observability schema.
  • Whererunward/governance/threat-model.md runward/governance/evaluation-rubric.md runward/governance/observability-schema.md
  • What the check verifiesThat the security assessment and the two documents that go with it (evaluation rubric, observability schema) are filled in, and, with --strict, that the cited evidence still exists.

Step 6

Hand over

Another team must be able to take the system over without those who built it.

  • What the record holdsThe recovery procedure and the handover note.
  • Whererunward/runbook.md runward/handover.md
  • What the check verifiesThat these documents exist and are filled in. Their quality remains your judgment.

The record is created with one command, in your repository.

Try it on an example, in one command.

Try it on an example

Talk to us

Tell us who you are, and we will get back to you.

Your details are recorded by Another Framework, publisher of runward, to get back to you. They are neither sold nor shared, and are deleted three years after our last exchange. To see or delete them: contact@runward.dev.