Skip to content

PROBE ONLY (do not merge): observe shared-fill ledger for ATTRIBUTION-3 identities - #8563

Closed
gunbai-bot[bot] wants to merge 1 commit into
mainfrom
attribution3-shared-fill-probe
Closed

gunbai-bot[bot] wants to merge 1 commit into
mainfrom
attribution3-shared-fill-probe

Conversation

@gunbai-bot

@gunbai-bot gunbai-bot Bot commented Aug 19, 2026

Copy link
Copy Markdown
Contributor

Temporary measurement-only branch for dashboard node://adhoc-68d59f0c-bc2. Un-quarantines exactly the three witness identities under investigation so this PR's CI floor run captures real [floor-shared-fill] data (no prior CI run has both the shared-fill mechanism, #8455, and these identities admitted — #8455 merged after #8457 quarantined them). Will be closed without merging once the job log is captured.

… identities to observe [floor-shared-fill] under a real --required-floor pass

Renames drop the long_home_prefixes-matched test.claim.long. prefix for
exactly the three witness identities under investigation in
dashboard node://adhoc-68d59f0c-bc2, so this PR's CI run includes them
in required-floor discovery and captures real shared_fill ledger data
(#8455 landed after run 32177951514 quarantined these witnesses, so no
prior CI run ever had both the ledger and these identities admitted at
once). This PR will be closed without merging once the job log is
captured; the real deliverable lands separately with the typed
disposition recorded against the unchanged, still-quarantined names.
@gunbai-bot

gunbai-bot Bot commented Aug 19, 2026

Copy link
Copy Markdown
Contributor Author

Measurement captured (run 32291153434 / job 96192007757). Closing without merging — this branch only existed to observe [floor-shared-fill] for the three ATTRIBUTION-3 identities under a real --required-floor pass; see the follow-up PR for the recorded verdict.

@gunbai-bot gunbai-bot Bot closed this Aug 19, 2026
gunbai-bot Bot pushed a commit that referenced this pull request Aug 19, 2026
… witnesses

Turns PR #8495's hedged "most plausibly the corpus-wide load/index
cost" into typed verdicts, grounded in a real --required-floor pass
(#8455's shared_fill ledger post-dates #8457's quarantine of these
modules by name, so no floor run ever had both simultaneously; a
throwaway, never-merged probe PR (#8563, run 32291153434 / job
96192007757) temporarily renamed the three identities for one CI
pass to observe them, then was closed without merging).

- declared_import_closure_lists_rust_import and
  ambient_pool_provider_preserves_listed_import: every
  module_graph_facts/module_path_index/reference_edges fill either
  row touches is keyed on this witness's own narrow
  class_b_declared_import_pool_roots, paid_by exactly this module,
  consumer_modules=1 -> SharedFillExclusiveToOneModule. The run's
  TOTAL line (fills=17, shared_fill_ms=0) shows zero
  SharedFillSharedAcrossModules exemplars anywhere in that floor
  pass. Attributed fill covers ~17.4-18.5s of each row's cost; the
  remainder is real per-call cost outside the ledger's surface.

- red_seed_runner_failure_detail_projects_located_receipt: appears
  in zero of the run's 17 shared_fill rows, neither as payer nor
  consumer. The standard-pool fills its own entry resolution would
  touch are all paid_by=<outside-fold> (pre-warmed during floor
  preparation before any claim runs) -- refuting the shared-fill
  mechanism as this identity's cost source entirely. Its ~54-76s
  cost and RSS growth (worst single claim in both observed runs)
  sit outside the ledger's instrumented surface.

Both notes now report a denominator-honest verdict rather than a
plausibility, per DESIGN.md's empty-observation-narrow rule.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01ARER4f3NVk6ZwMvHNCBaUb
briansrls pushed a commit that referenced this pull request Aug 19, 2026
… witnesses (#8566)

Turns PR #8495's hedged "most plausibly the corpus-wide load/index
cost" into typed verdicts, grounded in a real --required-floor pass
(#8455's shared_fill ledger post-dates #8457's quarantine of these
modules by name, so no floor run ever had both simultaneously; a
throwaway, never-merged probe PR (#8563, run 32291153434 / job
96192007757) temporarily renamed the three identities for one CI
pass to observe them, then was closed without merging).

- declared_import_closure_lists_rust_import and
  ambient_pool_provider_preserves_listed_import: every
  module_graph_facts/module_path_index/reference_edges fill either
  row touches is keyed on this witness's own narrow
  class_b_declared_import_pool_roots, paid_by exactly this module,
  consumer_modules=1 -> SharedFillExclusiveToOneModule. The run's
  TOTAL line (fills=17, shared_fill_ms=0) shows zero
  SharedFillSharedAcrossModules exemplars anywhere in that floor
  pass. Attributed fill covers ~17.4-18.5s of each row's cost; the
  remainder is real per-call cost outside the ledger's surface.

- red_seed_runner_failure_detail_projects_located_receipt: appears
  in zero of the run's 17 shared_fill rows, neither as payer nor
  consumer. The standard-pool fills its own entry resolution would
  touch are all paid_by=<outside-fold> (pre-warmed during floor
  preparation before any claim runs) -- refuting the shared-fill
  mechanism as this identity's cost source entirely. Its ~54-76s
  cost and RSS growth (worst single claim in both observed runs)
  sit outside the ledger's instrumented surface.

Both notes now report a denominator-honest verdict rather than a
plausibility, per DESIGN.md's empty-observation-narrow rule.


Claude-Session: https://claude.ai/code/session_01ARER4f3NVk6ZwMvHNCBaUb

Co-authored-by: Brian Searls <briansearls1@gmail.com>
Co-authored-by: Claude Sonnet 5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants