Retain original reader Scope activity in the C producer #107
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/lib-cstd!107
Loading…
Reference in a new issue
No description provided.
Delete branch "feature/raw-live-scope-freshness"
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?
Summary and rationale
Select the complete command-owner family that records standalone reader activity before its first raw mask effect. The producer and both workflows now use the same composed Integration source and all ten actual body hashes.
A standalone reader that has used its original Scope can no longer hand that Scope to another command as fresh. The private selected cohort exercises actual acquisition, output delivery and close before checking that refusal without a new spawn.
Tracking and scope
Companion to Integration reader freshness, composed in the root build. Builds on the pure C owner companion; its earlier source pair and artifact evidence remain separate. Related: native owner compatibility.
Architecture, authority and failure behavior
The private cohort retains one actual module/class/registry family. Recording use grants no process, descriptor or mask authority and cannot certify cleanup. Original ABI, OFD, physical restoration, close and native lifetime outcomes remain required. Existing finite budgets and refusal behavior remain intact; there is no ambient repository fallback.
Validation evidence
Source selections and documentation are updated. Paired owner controls and the source-backed memory object/archive are qualified; guest execution and self-hosting remain separate requirements.
WIP: Retain original reader Scope activity in the C producerto Retain original reader Scope activity in the C producerThe companion now selects the same complete command-owner family as the composed root build. Actual private-cohort reader use remains irreversible after close, and source-backed memory object/archive production succeeds through that original owner. The earlier pure-owner source pair remains independently usable.
The memory job identified
runtime/posix-io/coreas the extra source entry. The intentional SIGILL child now disables its own core dumps, using the change from #102. The parent still checks for SIGILL and verifies that no core was dumped; source-closure checks remain strict.Updated the workspace controls to load all ten declared process-owner modules from the selected source instead of a synthetic partial cohort. Cache refusal now checks the defining command_native_runner source and the original module namespace. The hash-before-execution, ambient-module restoration and initializer/slot nonmutation checks remain intact. Published in
fbbc6928.