@jjanczur/tyran 0.1.40 → 0.1.42

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -256,8 +256,10 @@ open one.
256
256
  the next report, review or merge clears it.
257
257
  - **Scout `DURABLE:` findings, you journal** as `finding` events — the
258
258
  required keys are `area` + `claim` (the area is the path or subsystem the
259
- scout's proof points at), plus that `proof` — scouts write nothing
260
- themselves. Implementers and reviewers append their own. An operator
259
+ scout's proof points at), plus that `proof` — and, when the scout proved
260
+ it by running something, the `command` and its `exit_code`. Scouts write
261
+ nothing themselves; implementers, reviewers and verifiers append their
262
+ own. An operator
261
263
  CORRECTION — a premise you had wrong, a step they had to undo — is a
262
264
  `finding` too, with `area: process`: it is the densest mistake signal
263
265
  there is, and the retrospective is where it becomes a `MISTAKES.md`
@@ -6,6 +6,11 @@
6
6
  #
7
7
  # kind: fact | convention | gotcha | command | decision
8
8
  #
9
+ # To merge two entries that say one thing, APPEND a third that states it once
10
+ # and carries `supersedes: [K-3, K-7]`. The named entries drop out of every
11
+ # brief while keeping their bytes and counters, so deleting the new file
12
+ # brings them back. Never edit or delete the originals to merge them.
13
+ #
9
14
  # Validate: node scripts/schema.mjs validate knowledge .tyran/knowledge/*.yaml
10
15
 
11
16
  entries: