BONE/SEA S13: relink the SEA image with segment-local VMAs - #46
BONE/SEA S13: relink the SEA image with segment-local VMAs#46Deadbytes101 wants to merge 9 commits into
Conversation
|
S13 BRANCH CREATION AND STATIC REVIEW COMPLETE Exact parent:
Exact candidate head:
Observed connector state:
Static adversarial review found and repaired one verifier defect before the PR was opened: the first draft rejected every local VMA greater than or equal to
plus exact local and physical bounds. Acceptance is still pending actual exact-head execution: $env:RUSTFLAGS = '-Dwarnings'
cargo test `
--locked `
--all-targets `
--manifest-path .\tools\bone-sea\Cargo.toml
cargo run `
--locked `
--release `
--manifest-path .\tools\bone-sea\Cargo.toml `
--bin bone-sea-s13 `
-- `
verify `
--shinesea D:\TECHNICAL\SHINESEAExpected native total: No ring3 transfer, no REPORTS ARE CLAIMS, NOT EVIDENCE. |
|
BONE/SEA S13 EXACT-HEAD EVIDENCE Observed on exact head WORKTREE
NATIVE GATE
SEGMENT-LOCAL IMAGE
JUDGES
NON-CLAIMS PRESERVED
GitHub Actions currently exposes no pull-request workflow run for this exact head. Local exact-head evidence is attached; any head movement, rebase, retarget or integration requires fresh proof. REPORTS ARE CLAIMS, NOT EVIDENCE. |
BONE/SEA S13 SEGMENT-LOCAL IMAGE
STACKED BASE
ecosystem/shinesea-s12-n6-loader56f9697f094fd848b0cf659861f21407b3a9ea750213d2368da7c49555e62555b17496a91cea6f2b93ea5ffb59ff31e87ab7fd5ecb5570c89b29ffee581d1a6c59580fedca7fca97035449521231f9450ca4a3c2cf35d6ed076408553bc6343ecaeae27f0d01c6301cab01a0e77bfb96CLASSIFICATION
S12 proved actual BIOS publication, full-byte CRC32, SEA LDT installation and architectural
LSLread-back, but intentionally did not transfer to S10_start.The S10 image used physical addresses as VMAs while the SEA LDT already adds physical base
0x00020000. A ring3 transfer against that model would double-add the segment base for static addresses.ONE DECISION
Keep the bounded S2/S12 descriptor unchanged and relink the unchanged no_std source graph with:
S13 does not transfer to ring3.
LOCAL / PHYSICAL LEDGER
SOURCE LAW
The exact-parent source graph remains frozen:
tools/bone-sea/src/lib.rstools/bone-sea/src/s3_adapter.rstools/bone-sea/s10/image.rsS13 adds a new VMA/LMA linker authority rather than rewriting SHINESEA or the no_std image source.
OBSERVED EXACT-HEAD VALIDATION
Working tree:
.tools/,__pycache__/,sc.local.png;i686-unknown-linux-gnu: installed.Native validation:
126 / 126 PASS;0.Segment-local image:
bone_sea_s13_local_image;0x00000000;0x00020000 / 0x0006ffff;0x00000000..0x0006ffff;0x00020000..0x0008ffff;79972;22560ca0ca12aaf81e1324fe77c93d9ba01af1d7e775cb66e9b2df0ada77d4b9;35040 / 30496;458752;668f272d4035c18600dfaec211756307bd5ab18734bd093bc5a0fe41a6028cd3;7;0.Judge results:
BONE/SEA S13 SEGMENT-LOCAL IMAGE VERIFY PASS.GitHub Actions currently exposes no pull-request workflow run for this exact head. The accepted evidence is the observed exact-head local transcript.
ADVERSARIAL JUDGE
0x00020000and is rejected by the exact base-translation law;>= 0x00020000was removed because it falsely rejected the legitimate arena and zero regions.DEADBYTE ECOSYSTEM REUSE
9eadc22d03b0782373d5ca23290bb76768df5e4f: exact identity and validation-before-publication discipline;444937bd0aef2e5b17ed253deb7677a778225d7e: freestanding linker boundary, binary geometry and adversarial rejection;PROOF SURFACE
.github/workflows/bone-sea-s13-local-offset-image.ymlconfig/bone_sea_s13.jsondocs/BONE_SEA_S13.mdtools/bone-sea/s13/LICENSE-NOTICE.txttools/bone-sea/s13/link.ldtools/bone-sea/s13/prove.pytools/bone-sea/src/bin/bone-sea-s13.rsNON-CLAIMS
_startexecution: no;MERGE LAW
S13 is ready for review only against exact parent
56f9697f094fd848b0cf659861f21407b3a9ea75and exact head0213d2368da7c49555e62555b17496a91cea6f2b. Any head movement, rebase, retarget or integration requires fresh evidence.No merge is performed automatically. No S14 authorization is implied by this PR transition.
REPORTS ARE CLAIMS, NOT EVIDENCE.
NO COSTUME RIGOR.