Skip to content

Commit 0993bb0

Browse files
thymikeeclaude
andcommitted
docs(adr): name the spine symbols the pinned harness reads
At d9959f5 the harness derives R5/R6 from model.ts's RANKED_ZONES and zoneRank, not TARGET_DAG_RANK, and writes the other rules' paths inline (R77's from RUNNER_SUBTREE) rather than reading the rule tables. Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>
1 parent 478fbd8 commit 0993bb0

1 file changed

Lines changed: 6 additions & 5 deletions

File tree

‎docs/adr/0032-layering-graph-engine.md‎

Lines changed: 6 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -20,11 +20,12 @@ whose production tree is `7dda0c2bf`'s; the harness lives only at that commit
2020

2121
The edge-set, parity, clean-tree and runtime numbers are the output of the spike harness run at
2222
`d9959f510`. Retrieve it with `git show d9959f510:scripts/layering/boundary-engine-spike.ts`, after
23-
`git fetch origin pull/3286/head` if the commit is not local; usage is in its header. It builds both
24-
engine configs from `TARGET_DAG_RANK` and the rule tables, runs only on exactly the tracked
25-
production tree (1,837 files, 41 zones), and gives recorded R6 and R78 edges to each engine's
26-
known-violations baseline. The deletion table and the `.fallowrc.json` field count are counts of
27-
files at the same commit.
23+
`git fetch origin pull/3286/head` if the commit is not local; usage is in its header. It derives
24+
both engines' R5 and R6 rules from `model.ts`'s `RANKED_ZONES` and `zoneRank`, writes the other
25+
rules' paths inline (R77's from `RUNNER_SUBTREE`), runs only on exactly the tracked production tree
26+
(1,837 files, 41 zones), and gives recorded R6 and R78 edges to each engine's known-violations
27+
baseline. The deletion table and the `.fallowrc.json` field count are counts of files at the same
28+
commit.
2829

2930
### Edge-set diff against `resolveImportEdges`
3031

0 commit comments

Comments
 (0)