Repository navigation
Conversation
…laims (no new kappa)
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.
Census round 2 for the open complex queue, extending the merged
research/complex-queue-ceiling-census(and built on merged #1240). No new kappa;a screening review-aid only - no claim is accepted or rejected.
What this does
The first census covered 14 open claims and listed 16 as not covered: no complex
profile whose kappa equals the title kappa occurred together with an idle histogram
in those packages. This round re-audits the same 16 claims at their heads of
2026-10-15 (heads frozen to full SHAs in SNAPSHOT2.json) and covers 13 of them. The
reason round 1 missed them is a recording-key convention: the paid profile sits under
global_profilein each claim'sdata/SPEC.json(together withidle_remainder_profile,liveand an exactkappa), not undercomplex_profile;RESULT/CERTIFICATE profiles pair with a sibling SPEC for their identity inputs.
Results
kappa equals its title kappa exactly, satisfies the coverage identity
mass = 72*live + 64*callsat 896/9 live families per call, passes the idle split,and lies below its own word's cap.
W4 word and reproduce its cap exactly (0.0016872744); Conditional κ = 0.001675568675201533: joint entrances with T37 owner packing #1169 reproduces its W3 word
and cap. Both caps are re-derived in verify.py from the first census's own pinned
inputs - the extraction path cross-checks against the merged machinery.
words (caps 0.00168355-0.00168400, about 0.19-0.22% below the W1/W4 band) with only
.47-.50% packing headroom left: they lead on realization, not headroom.
own title kappa together with a profile and idle histogram (they vendor
predecessors' kappas, or record no exact own kappa). The README and RESULT.json
give the per-claim required-fields checklist - the same ask as the Agent workflow feedback: friction, detours, and better next steps #1200 workflow
feedback.
during the session. The snapshot pins the audited heads by SHA, exactly as the
first census pins its own.
Evidence
verify.py: PASS_COMPLEX_QUEUE_CEILING_CENSUS_R2 screened=13 words=8 unscreened=3(identity + split for all 13, exact kappa match, endpoint below a_lo, kappa below
cap, W4/W3 cross-controls against the first census's pinned inputs, two negative
controls, frozen RESULT.json byte match). Stdlib only.
rebind2.py: PASS_SNAPSHOT2_REBOUND 13 - all pinned profile/idle blobs re-read atthe frozen heads.
producer.pyre-derives SNAPSHOT2.json offline at the frozen heads(or with --fetch-prefixes --fetch-titles at live heads).
scripts/research_package.py --check-only: PASS_PACKAGE_METADATA_AND_PINS, andverify.py re-run green on a second host (Python 3.12, git 2.47).
Provenance
Base
c22e42de697334df85337e005864773cdc2bc98b; claim threaddiscussions/2739; overlaps refreshed (337/144/260 matches on the drawn cards - the
refinement lands on the first census's own recorded remainder). Selected record and
catalogue are historical provenance. SOURCES.json pins the first census and #1240
files; SNAPSHOT2.json pins the 16 audited heads and profiles. Caps are planning
bounds under the fixed coverage law and halving guard; they do not bound changed
words, templates, recipes or the two-unpaid-coordinates contract change, and do not
review any claim.
Prepared by Abhinav Ramachandran (geckods) with substantial end-to-end assistance
from a Hermes agent (Nous Research, GLM-5.3) under the standard donation prompt.