Maturity from run history, pack revision digests, attribute sets, projects and templates (RBT-WP-0008)
Also fixes run lists and scores mixing runs of different packs in one repository. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> Assistant: claude-code Assistant-Model: sonnet Assistant-Process: 295952@bnt-lap001 Assistant-Session: e93f64ad-516c-46eb-9666-aad8d300c477
This commit is contained in:
parent
2f60d47746
commit
0203bf553c
19 changed files with 1311 additions and 33 deletions
|
|
@ -105,3 +105,13 @@ Rules the engine enforces:
|
|||
- **Stalled**: an unfinished run is counted as `stalled` in the score, and as `abandoned` after a week.
|
||||
- **Modes** are `manual` and `auto-confirm`. Auto-confirm applies confirmation only; running the step's own
|
||||
command is a separate, later level ("auto-pilot with execution", RBT-WP-0006).
|
||||
|
||||
## Context and revision
|
||||
|
||||
Every run (v0.1 and v0.2) records `pack_digest`, the revision of the pack directory it used (a hash of its files,
|
||||
excluding review records, local state and `exercise_status:` lines), and `context`: the optional non-secret
|
||||
`project`, `target` and `environment` class (`rehearsal | staging | production`) it was applied to. Maturity and project
|
||||
state are derived from these (`docs/maturity-and-projects.md`). Run records of all packs in a repository share one
|
||||
folder; a pack's runs are those whose `pack_id` matches.
|
||||
|
||||
Run timestamps have microsecond precision, so runs and feedback made within the same second still sort correctly.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue