Specify loaded runtime image custody #100
No reviewers
Labels
No labels
alpha-1
bug
ci
docs
duplicate
enhancement
help wanted
invalid
performance
phase-6
question
refactor
security
wontfix
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
erix/docs!100
Loading…
Reference in a new issue
No description provided.
Delete branch "feature/loaded-runtime-images"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Specify BootKernel 2.3 loaded-image and segment descriptions, exact compatibility and construction order. Distinguish whole allocation custody, precise mapping maxima, normalized cache selectors and original handover ownership. Preserve earlier extension positions and register the source in the bounded manual input list.
Based on #99; documents LibHandoff #13 and its design. Producer: Bootloader #33; coordinated native activation: Kernel #123.
WIP: Specify loaded runtime image custodyto Specify loaded runtime image custodyThe complete manual builds to 3,954 pages without final-pass warnings. Rendered pages 178 and 181–188 were checked, including all three new tables, corrected section references and the cache-selector expression. Current-head CI passes. The text keeps original allocation custody and native enforcement separate from the codec contract.