Skip to content

Run record

Used in the playbook Project foundation.

Download run-record.md — the source, as in the repository.

How to use

The template's own instructions:

Template from the UASK Engineering Hub, playbook mgmt.project-foundation, rule R1 and the Tailoring section. Save next to the artefacts (for example project/RUN.md). It holds what an issue would hold when the project has no tracker or repository: the brief, the tailoring and the state of each stage; and it is where gaps in the playbook, skill and templates are written down for the Hub. Replace every [bracketed] value. When the record leaves the project, remove client names, contacts and other details.

Fields

Front-matter fields and sections of the document the template creates. A section marked Optional in the template may be deleted from a copy; every other field and section stays (tools/check_artifacts.py checks this for the kinds it knows).

Field or sectionWhereRequired
titlefront matterrequired
statusfront matterrequired
versionfront matterrequired
datefront matterrequired
ownerfront matterrequired
Conditionssectionrequired
Briefsectionrequired
Tailoringsectionrequired
Stagessectionrequired
Checkssectionrequired
Gaps in the playbook, skill and templatessectionoptional
Independent reviewsectionoptional
Next stepssectionrequired

Example

A filled-in copy for an invented product, templates/examples/run-record.md, in the Hub repository.It shows the level of detail to aim for, not text to reuse.

example-run-record.md
---
title: Foundation run record — Fieldnotes
status: draft
version: 0.1.0
date: 2026-03-02
owner: Alex Doe
---
# Foundation run record — Fieldnotes
## Conditions
| Field | Value |
|---|---|
| Hub release | v1.0.0 |
| Playbook | `mgmt.project-foundation` 1.0.0; items read: `arch.adr`, `arch.c4-model` |
| Skill | `project-foundation` 1.0.0; invoked as a skill |
| Templates | vision, prd, blueprint, roadmap, adr, agents; not used: run-record of an earlier run |
| Agent | one lead session, no subagents; independent reviewer: yes |
| Kind of work | new product |
| Governance tier | standard — `mgmt.governance-tiers`; chosen by the owner on 2026-03-01 |
| Sources read | the owner's brief and five tester interviews; no competitor code was read |
| Recall hits with personal data | none |
## Brief
"A note app that works offline and never locks my notes in" — the owner, 2026-03-01 (full text in `project/brief.md`).
## Tailoring
- **Roles:** owner: Alex Doe; client: none; technical lead: Sam Roe; lead developer: the agent.
- **Stages:** all kept; Research merged into Requirements because the interviews were short.
- **Where the artefacts live:** `project/`.
- **Language and ids:** English; default ids.
- **Without tracker or repository:** not applicable.
- **Confirmed by the owner:** 2026-03-01, in the chat.
## Stages
| # | Stage | What was done | Exit criteria |
|---|---|---|---|
| 1 | Intake | the brief was read back and confirmed | met |
| 2 | Vision | `project/VISION.md` written | met |
| 3 | Requirements | PRD with 3 FR, 2 NFR, 3 AC | met |
| 4 | Research | five interviews summarised | met |
| 5 | Blueprint | `project/BLUEPRINT.md` | met |
| 6 | Decisions | ADR-0002 proposed | not met — the owner has not accepted it |
| 7 | Roadmap | two milestones | met |
| 8 | Bootstrap | `AGENTS.md` and `tests/run.sh` | met |
| 9 | Gate | waiting for ADR-0002 | not met |
## Checks
`python3 tools/check_artifacts.py project --strict` — OK, 0 errors, 0 warnings, 2026-03-02.
## Gaps in the playbook, skill and templates
1. The PRD template has no line for the supported Android versions; added to constraints by hand.
## Independent review
A second session read the PRD and the blueprint on 2026-03-02 and raised 4 findings, all fixed.
## Next steps
- The owner accepts or rejects ADR-0002.

Completion checks

A copy is complete when:

  • every required field and section above is present, in the same order, and no bracketed placeholder is left;
  • the exit criteria of its stage of the playbook Project foundation are met;
  • the owner has approved it, where the playbook asks for approval. Only the owner sets approved.

Source

templates/run-record.md, as in the repository. Placeholders are in square brackets; comments carry the instructions.

run-record.md
---
title: Foundation run record — [project]
status: draft # draft | final
version: 0.1.0
date: YYYY-MM-DD
owner: [owner]
---
# Foundation run record — [project]
<!-- Template from the UASK Engineering Hub, playbook mgmt.project-foundation, rule R1 and the Tailoring section.
Save next to the artefacts (for example project/RUN.md). It holds what an issue would hold when the
project has no tracker or repository: the brief, the tailoring and the state of each stage; and it is
where gaps in the playbook, skill and templates are written down for the Hub. Replace every [bracketed]
value. When the record leaves the project, remove client names, contacts and other details. -->
## Conditions
| Field | Value |
|---|---|
| Hub release | [vX.Y.Z-rc.N, pin and checksum, or commit] |
| Playbook | [`mgmt.project-foundation` version; items read: `arch.adr`, `arch.c4-model`, …] |
| Skill | [`project-foundation` version; invoked as a skill / read as a file and followed by hand] |
| Templates | [which were used; which were not and why] |
| Agent | [model, number of sessions, subagents; independent reviewer: yes / no] |
| Kind of work | [new product / re-foundation of a running product / large new work] |
| Governance tier | [lightweight / standard / high-assurance — `mgmt.governance-tiers`; chosen by whom, when] |
| Sources read | [what the run was based on; what was deliberately not read] |
| Recall hits with personal data | [how many hits of the recall step held another person's data; none of it copied here] |
## Brief
<!-- The owner's brief verbatim, or a link to the file that holds it (R1). -->
## Tailoring
- **Roles:** [owner, client, technical lead, lead developer — who holds each]
- **Stages:** [kept / merged / skipped, one line each, with the reason]
- **Where the artefacts live:** [paths, when they differ from `project/`]
- **Language and ids:** [language of the text; id scheme if not the default of the playbook; temporary marks used]
- **Without tracker or repository:** [what replaces the issue, the pull request and CI]
- **Confirmed by the owner:** [date and where, or "not confirmed"]
## Stages
| # | Stage | What was done | Exit criteria |
|---|---|---|---|
| 1 | Intake | [ … ] | [met / not met — why] |
| 2 | Vision | [ … ] | [ … ] |
| 3 | Requirements | [ … ] | [ … ] |
| 4 | Research | [ … ] | [ … ] |
| 5 | Blueprint | [ … ] | [ … ] |
| 6 | Decisions | [ … ] | [ … ] |
| 7 | Roadmap | [ … ] | [ … ] |
| 8 | Bootstrap | [ … ] | [ … ] |
| 9 | Gate | [ … ] | [ … ] |
## Checks
<!-- The commands run and their results, for example `check_artifacts.py`, and any script written for the run
(coverage of requirements in the blueprint and the roadmap, secrets). Say what no check covers. -->
## Gaps in the playbook, skill and templates
<!-- Optional. One numbered item per gap, most important first: where it was found, what happened, what you did
instead, what you propose. This is the input for the Hub; no client details. -->
1. …
## Independent review
<!-- Optional. Who reviewed, when, the number of findings by severity, the verdict, the link to the report, and
what the review found that the author had not. -->
## Next steps
- …