Skip to content

Bind native seed preparation to a fixed semantic mapping - #37

Merged
EHotwagner merged 2 commits into
mainfrom
routine/bar-native-seed-fixed-source-20261005
Oct 5, 2026
Merged

EHotwagner merged 2 commits into
mainfrom
routine/bar-native-seed-fixed-source-20261005

Conversation

@EHotwagner

Copy link
Copy Markdown

Native seed preparation was blocked by the old caller root and unset mapping guards. Bind the fresh caller root and reconstruct one fixed semantic mapping successor without embedding future placement inodes in helper source. Preserve the exact original453 physical rows/ancestors,335 CLR pins and existing physical revalidation; all five new rows still require genuine observed pins before runtime. Native profile JSON now refuses duplicate keys and nonfinite values before validation.

The full delta against protected mainf089 is four helper paths: native caller, mapping validator,15 portable mapping controls and the existing portable-control roster. Controls use synthetic physical rows and explicitly mocked historical digests; committed fixture data contains only semantic source-contract declarations, with no private runtime receipts or original physical metadata.

Validation:114 portable SOURCE controls passed; original physical revalidate body byte-identical; diffcheck passed. No CLR/compiler/Node/Lua/policy/engine/game/browser execution or actual17756-file preparation, policy placement, checksum or native acceptance performed. Native CI already invokes the portable source runner; full native integration/game and new physical closure/current-process joins remain separate gates. Actor/seed/unit acceptance remains pending and useful play0/6.

@EHotwagner
EHotwagner merged commit e045f56 into main Oct 5, 2026
1 check passed
@EHotwagner
EHotwagner deleted the routine/bar-native-seed-fixed-source-20261005 branch October 9, 2026 16:28
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.

1 participant