Repository navigation
Read immutable policy closure with its exact custody pin - #35
Merged
EHotwagner merged 13 commits intoOct 4, 2026
Merged
Conversation
EHotwagner
deleted the
routine/bar-policy-publication-readonly-delivery-20261005
branch
October 9, 2026 16:28
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
1 participant
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 shared GrowingLog adapter refused the accepted read-only policy closure before launching a policy: its generic private reader required a0700 parent/0600 file, while canonical placement intentionally uses0500/0400. A dedicated immutable-closure reader now requires the complete original physical pin, exact byte digest, current owner, single link, no symlink components and stable open/named/parent custody. The concrete seed and policy-only contexts supply that original pin from their sealed profile. Generic private-input rules and canonical F# closure checks remain unchanged.
The next no-game attempt uses a fresh literal
/tmp/bar-policy-transport-qualification-20261005-v2, preserving the consumed prior operation. Against freshly observed protected main21c1f37c09bb9a0fc2e5ed08c9bc8a08ccf2a545, the complete diff is six helper paths,66 insertions/6 deletions. The delivery merge preserves source candidate1b125ecfa6cfa93bf01fc187a5b1ca52cb2e9238and tree1592bc099728a1bf4164797b9f77722ed6b49af6exactly; it adds protected ancestry only.Validation:99 portable Python source controls passed with real process effects prohibited, including10 focused immutable-read controls. Existing native CI invokes this exact portable roster; native checks for this head remain pending. No CLR, policy, engine, model, Node or Lua ran. The bounded source diff audit found no private evidence paths or credential-shaped literals. The fixed temporary attempt literal is an intentional implementation contract. Private supervision/configuration/evidence are not published.
Retained actual policy build and PE/PDB proof remain compilation evidence for their original scope. This new39-body helper graph needs separately accepted derived provenance placement before runtime; old e916 placement is not relabeled. Actual no-game transport, native actor/seed/browser/Arm/requested-unit and useful-play qualification remain open. SourceLink remote content and post-last-snapshot disconnect coverage remain Unknown.