# Audit: the render grouping of return #783 omitted two nodes, and the defect is now impossible Jobless audit of **return #783** (job #1570), filed from the same window that produced it. No usage is claimed: this is a correction inside one window, not a new assignment. ## 1. The defect, exactly Return #783 shipped `artifacts/tpc-deps.render.md` (sha256 `dfb46409d7682fd7f6e8c4b6fd55bd33a312c274263c8e67358f091121d40c93`) and the report generated from it (`…report-tpc-conditional-1570.md`, sha256 `04210d5352529de579ebae07c1893befa20d76d9c47a45d3d50b797a71beada0`). In both, the *group tables* of section 4 are missing two nodes that the graph does contain — `B-EXACT` and `B-MARGIN`, the reviewed fixed-endpoint normalization and the fourth sufficient consumer. The JSON export of the same return (`artifacts/tpc-deps.json`, sha256 `3be46a62ce39cc2b4a7c4d005e9f8636497ee751655ff8df5e7a3faa373dbacf`) does carry both, and the report's own section 1 names `B-MARGIN` in its consumer table, so the return is **incomplete rather than wrong** — but a reader who counts rows against the stated "59 nodes" is entitled to be confused, and the omission is in the one place where the reader is meant to be able to check the model. **Cause.** `render()`'s groups were a hand-written list of node ids. The two nodes were added to `NODES` after that list was written, and nothing connected the list to the graph. The `render` path is the only part of the tool that was not data-driven, which is also why the omission survived the return's own gates: `validate`, `verify` and the self-test all passed, because every node was nonetheless in the graph, in the JSON and in the source gate. ## 2. The fix, and the gate that makes the class impossible * The grouping is now **computed** from the graph: each consumer's derivational subgraph first, in the order of the root's routes, then every remaining node by its `role`, with a final bucket that says in its own label that `Unclassified (a defect: every node needs a role)` is a defect. * The self-test asserts that the grouping covers every node **exactly once**, so a node added later cannot be silently omitted again, and a node placed in two groups fails too. * `ROLE_LABEL` covers every role in the vocabulary, and a role without a label lands in the defect bucket rather than disappearing. ## 3. The corrected artifacts, and which hashes they supersede | artifact | sha256 | state | |---|---|---| | `artifacts/tpc-deps.render.md` | `2ff0fb8d33fa43650fe0fb634fd7edffea7d5e1b6347564c252fe3e6a9480c4a` | **supersedes** `dfb46409…0c93` | | `artifacts/report-tpc-conditional-1570.md` | `8ce0ef97bd2ba7c3c8d69f606751acc53a9a2bd4a5a2fd26fe96827fcc79cf67` | **supersedes** `04210d53…ada0` | | `work/tpc_deps.py` | `9aaddc61ec7234512d1a549275e93468d0e2cd5ea7899a391671553077b2abcc` | **supersedes** the copy served with #783 | | `work/make_report1570.py`, `work/tpc-deps-selftest.json`, `artifacts/tpc-deps.json` | as served with this audit | unchanged in content except the groupings/selftest counters | The gates are re-run in the corrected copy: 59 nodes, 73 source tokens checked against the fetched documents and returns with zero misses, the root not derivable from the corpus's current rungs, every refuted node with empty impact, and the grouping coverage assertion green. ## 4. The revision this audit carries: exactly one row in the router An audit return must carry a revision, so the revision is the smallest true one there is: one row added to the question table of `research/README.md` (the router), reporting the assembly as **run-local, derived and awaiting integration**, with its structural results stated in one sentence each. `artifacts/rev-README.md` is the served document plus that row and nothing else — the diff is one added line, `+1` / `-0`, and the producer that makes it refuses to run twice or to insert anywhere but after the anchor row it names. Why a router row and not a new document: a corpus document would be a *claim about the corpus*, and the assembly currently lives in a run (its nodes already point at corpus documents and returns). The router row is what makes it findable by the next agent; promotion to its own document is the handler's decision, not this window's. ## 5. What this audit does not do It does not re-open, re-price or re-tag any node, and it changes no count other than the grouping: aligned with the return's own scope, no mathematics is touched. It also does not claim that the defect was harmless in principle — a model whose only human-readable view can omit a member of a conjunction would be a bad instrument, which is why the fix is a gate and not an edit.