Repository navigation
Close the V4.1 Engram membership: srv8's index-selection receipt becomes the live reading - #12152
Merged
Merged
Conversation
…eceipt as the live reading fleet-converge run 35877813088 (spark_v41_checkpoint_materialize, srv8, main a0a4819) ran the spark_v41_index_selection step #12012 added: it verified model.safetensors.index.json against its manifest row, read it back, and parsed it with parse_json_document under a hard memory.max of 27917287424 bytes (the runner slot's, read from actions-runner@srv1-09.service). Its receipt: sha256=74b0686a... bytes=7470294 names=96085 and 12 .engram. members (layers 1 and 14, six each). v41_index_engram_selection_reading carries those values with the run as provenance; the extdeps fold compares them against the pin, so the observed Engram population now closes against the full index. The live-reading witness flips from Unread-and-scoped to Read-and-closed. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
… is the oracle (review 70580) Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
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.
What.
gunbc.spark.v41_index_engram_selectionv41_index_engram_selection_readinggoes fromUnreadto the receipt of the enrolled route that #12012 added. That closes the V4.1 Engram membership against the full published index.The source. Fleet-converge run 35877813088, mode
spark_v41_checkpoint_materialize, target srv8, at maina0a4819, stepspark_v41_index_selection:v41_observe), then read it back.parse_json_documentread it in 8m18s.memory-fence hard memory.max=27917287424 at /sys/fs/cgroup/system.slice/system-actions\x2drunner.slice/actions-runner@srv1-09.service. The ancestor levels aremax/max, and the service level hasmemory.max=27917287424 memory.high=26843545600. That equalsgunbc.runner_slot_allocationgunbc_runner_slot_memory_max_bytes, so the runner slot's grant is the fence, as ruled.index-selection sha256=74b0686a3d2891980d5e303251b075a3bccae2c2ff650747db2620a649b98fa8 bytes=7470294 names=96085 selector=.engram., with 12 members. Layers 1 and 14 each haveembed.weight,embed.scale,q_weight,k_weight,wkv.weightandwkv.scale, on shards 47 and 48.Why this is not a restatement of the pin. The row carries the receipt's values and the run as
observed.extdeps.deepseek.deepseek_v4_1_flashdeepseek_v4_1_flash_engram_membership_closure_ofcompares them against the pin (sha256, size, tensor count), and the existing claims keep the discriminating REDs: another file's sha, one fewer name, and a thirteenth.engram.name each refuse or stay scoped.Witness change.
the_live_reading_is_unread_and_the_observed_population_stays_scopedbecomesthe_live_reading_closes_the_observed_population. It asserts the row isRead, with 96085 names, 12 members and this run as provenance, and that the observed population's closure carries no obligation.v41_runtime_candidatestill names the published-shard row-store obligation. The key for that is bold-newt-50's encoded-store digest work and is not in this PR.Fleet status for context. srv5, srv6 and srv7 are fully materialized: all 52 files verify, and the four Engram span sha256s are byte-identical across the three. srv8 is reattaching for its last two shards.
🤖 Generated with Claude Code