Repository navigation
Five observation_emit_census rows red after the floor unmask: finish or retire the observation emitter migration census - #9274
Merged
Conversation
…k reported four code moves as census events — and hid the one real one, a migration reverting to raw emits Five `gunbc.observation_emit_census` rows went red at once. Measured: exactly one was a census event. `CensusedEmitSite` carried `source_file: NonEmptyStr`, whose only consumer in the corpus was the witness's `census_marker_present` — read that one file, grep it. That is a positional citation in the sense DESIGN §3 rules against, and it rots in the way this census cannot tolerate: it goes false when an emit MOVES, which is not a census fact. #9228 deleted claim_executor's unreachable plan/walk surface (21,366 -> 11,508 lines) and four rows reded while their tag families sat untouched in sibling seed files ([receipt], [resolve-split], [assembly-split], [witness-row-cost]). Four false reds beside one true one is worse than no check: the true one is indistinguishable in the noise. THE ONE REAL EVENT, and it is a REGRESSION, not the retirement it looks like. [floor-memory] was a MigratedToObservation row: the floor's periodic progress line rendered through `ci_heartbeat_line` via the seed mirror `render_heartbeat_line_mirror`. Neither the marker nor the mirror occurs anywhere under src/ any more (one doc comment names the mirror). Read no further, that is a retirement. It is not: the floor still emits a periodic progress line and a per-claim RSS line, now as raw `[floor-heartbeat]` and `[floor-claim-memory]` eprintlns in cli_run.rs with no projection behind them. A projection was deleted and raw emits took its job under new names. Deleting the row as a completed retirement — which is what marker-absence alone supports — would have booked a reversal as progress. WHAT LANDS - `source_file` deleted from the type. Presence is asked of the SEED (`seed_emit_sources`, folded), so a marker that moves stays green and a marker that leaves reds. Fail-closed on its own denominator: a new witness reds if any listed source stops reading non-empty. - `floor_heartbeat_site` and `floor_claim_memory_site` enrolled as CountedFrontierSite; frontier count rises by two, which is the honest direction. `w_the_floor_heartbeat_projection_is_absent_from_the_seed` is the discriminating probe — three conjuncts, because marker-absent and mirror-absent alone cannot tell retirement from regression; only a raw successor emitting can. It reds when the debt is paid, forcing reclassification in the same change. - The floor-memory raw-shape probe is deleted with its subject. Not the §4b(4) keep-the-evidence case: nothing climbed, so there is no rung to hold. - `claim_executor discovery_claim_result`, cited as [witness-row-cost]'s grounding, RESOLVES TO NOTHING — fabricated 2026-08-22 and copied into the retirement acceptance, so one invented symbol became two files' evidence. Corrected to the `witness_cost_*` helpers in cli_run.rs, in both. - Raw-shape probes: mirror positives widened to the seed; the three negatives measured to be ambiguous seed-wide (`t_ms=`, `current={}`, `bytes (VmHWM)` — 4, 3 and 2 unrelated occurrences) stay file-scoped. WHAT IS DECLARED, NOT FIXED. The bidirectional claim is false as stated: 57 bracket-tag spellings live in the six seed sources against 13 rostered tags, so 44 are unrostered — an UPPER BOUND from a spelling grep, not the frontier debt, and quoted as the shape of the gap rather than its size. It is not repaired by hand-authoring 44 rows, which multiplies the surface that rots. The next-rung trigger is a substrate capability rather than effort: the interpreter registers `string_contains` and `string_length` and nothing else over strings, so a fold can ask whether text contains a pattern and cannot ask where, how many, or what else of this shape. Membership is decidable; enumeration is not reachable. Occurrence-grain discovery — the durable fix this module has named as its residue three times — is not expressible in .dag today. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_016BTuU9MJgDAtC2h3akqzLD
…ent answered: ask for the call form Executed, the probe returned false. `render_heartbeat_line_mirror` still occurs once in cli_run.rs -- in a doc comment, in backticks, naming the deleted mirror. A substring test cannot tell a call from a mention. The conjunct now asks for `render_heartbeat_line_mirror(` with the open paren: an approximation of 'a call site, not a mention', not a fix, and one that fails toward red rather than green. WHY IT WAS WRONG WHEN WRITTEN: the first draft was verified by shell grep over src/ and reded when executed. The difference was the denominator -- the check folds seed_emit_sources, which includes cli_run.rs where the comment lives. A measurement taken with a different instrument than the check runs is not evidence about the check. 18 of 18 witness identities green by execution. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_016BTuU9MJgDAtC2h3akqzLD
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The census pinned each row to a file, so #9228's claim_executor shrink reported four code moves as census events — and hid the one real one, a migration reverting to raw emits
Five
gunbc.observation_emit_censusrows went red at once. Measured: exactlyone was a census event.
CensusedEmitSitecarriedsource_file: NonEmptyStr, whose only consumer inthe corpus was the witness's
census_marker_present— read that one file,grep it. That is a positional citation in the sense DESIGN §3 rules against,
and it rots in the way this census cannot tolerate: it goes false when an emit
MOVES, which is not a census fact. #9228 deleted claim_executor's unreachable
plan/walk surface (21,366 -> 11,508 lines) and four rows reded while their tag
families sat untouched in sibling seed files ([receipt], [resolve-split],
[assembly-split], [witness-row-cost]). Four false reds beside one true one is
worse than no check: the true one is indistinguishable in the noise.
THE ONE REAL EVENT, and it is a REGRESSION, not the retirement it looks like.
[floor-memory] was a MigratedToObservation row: the floor's periodic progress
line rendered through
ci_heartbeat_linevia the seed mirrorrender_heartbeat_line_mirror. Neither the marker nor the mirror occursanywhere under src/ any more (one doc comment names the mirror). Read no
further, that is a retirement. It is not: the floor still emits a periodic
progress line and a per-claim RSS line, now as raw
[floor-heartbeat]and[floor-claim-memory]eprintlns in cli_run.rs with no projection behind them.A projection was deleted and raw emits took its job under new names. Deleting
the row as a completed retirement — which is what marker-absence alone
supports — would have booked a reversal as progress.
WHAT LANDS
source_filedeleted from the type. Presence is asked of the SEED(
seed_emit_sources, folded), so a marker that moves stays green and amarker that leaves reds. Fail-closed on its own denominator: a new witness
reds if any listed source stops reading non-empty.
floor_heartbeat_siteandfloor_claim_memory_siteenrolled asCountedFrontierSite; frontier count rises by two, which is the honest
direction.
w_the_floor_heartbeat_projection_is_absent_from_the_seedis thediscriminating probe — three conjuncts, because marker-absent and
mirror-absent alone cannot tell retirement from regression; only a raw
successor emitting can. It reds when the debt is paid, forcing
reclassification in the same change.
§4b(4) keep-the-evidence case: nothing climbed, so there is no rung to hold.
claim_executor discovery_claim_result, cited as [witness-row-cost]'sgrounding, RESOLVES TO NOTHING — fabricated 2026-08-22 and copied into the
retirement acceptance, so one invented symbol became two files' evidence.
Corrected to the
witness_cost_*helpers in cli_run.rs, in both.measured to be ambiguous seed-wide (
t_ms=,current={},bytes (VmHWM)—4, 3 and 2 unrelated occurrences) stay file-scoped.
WHAT IS DECLARED, NOT FIXED. The bidirectional claim is false as stated: 57
bracket-tag spellings live in the six seed sources against 13 rostered tags,
so 44 are unrostered — an UPPER BOUND from a spelling grep, not the frontier
debt, and quoted as the shape of the gap rather than its size. It is not
repaired by hand-authoring 44 rows, which multiplies the surface that rots.
The next-rung trigger is a substrate capability rather than effort: the
interpreter registers
string_containsandstring_lengthand nothing elseover strings, so a fold can ask whether text contains a pattern and cannot ask
where, how many, or what else of this shape. Membership is decidable;
enumeration is not reachable. Occurrence-grain discovery — the durable fix
this module has named as its residue three times — is not expressible in .dag
today.
Co-Authored-By: Claude Opus 5 (1M context) noreply@anthropic.com
Claude-Session: https://claude.ai/code/session_016BTuU9MJgDAtC2h3akqzLD