Plan TLS writes from retained registry input #10
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/dynlinkd!10
Loading…
Reference in a new issue
No description provided.
Delete branch "feature/registry-bound-tls-plans"
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?
Validate retained registry bytes against original graph identities and derive TLS geometry from their actual prefixes. Borrow committed ordinary and TLS output only for the immutable transaction lifetime, preserving caller storage and cleanup ownership.
Depends on #9 (
feature/exact-relocation-patch-records).Keep this feature and its contract separate from the preceding changes.
Plan TLS writes from the retained registry and preserve exact patch widths and transaction lifetimes.
WIP: Plan TLS writes from retained registry inputto Plan TLS writes from retained registry inputThe actual dispatch and transaction controls cover original registry validation, mixed patch widths, failed commit, refusal and abort cleanup. Current component CI passes. Executing the resulting TLS plans in native processes remains separate consumer acceptance. Ready for review.