Repository navigation
feat(enforcement): persist original-owner operation journal - #954
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Add a live protected operation journal associated with the original installed owner, caller completion and VM registration. The installer preprovisions an exact empty epoch file and a protected registration binding its original directory/file identities. The native lease retains an exclusive writer and verifies the full acknowledged prefix before bounded append, real flush and readback. Uncertain writes or lost original authority permanently refuse; acknowledgments carry metadata persistence only.
Installer staging, upgrade, rollback and cleanup track at most two exact original journal files. Retirement consumes the original administrative cleanup fence and preserves bounded closed bytes in the retained administrative context; failed capture or capacity exhaustion refuses removal. This in-memory evidence is not a durable archive. Original caller, owner and journal gates order acknowledgments and disposal without the reverse lock order. Ordinary inspect-owned remains read-only; no VM effects, restart adoption or recovery authority are added.
Validation: 447 distinct passing Windows controls across composed receipts: 401 controls in eight unchanged neighboring suites plus 46 fresh journal/installed-owner controls after fixture repairs. The earlier combined run remains recorded as 445 passed and 2 failed; its failures are not relabeled. All 24 frozen input hashes reconcile before/after, all seven production helpers build, and independent Astra review passes. Controls include actual held-file I/O, actual installer-produced registration parsing, staging/commit/rollback and deterministic disposal races; installed authority/protection and selected failure responses remain modeled. Production C# excludes test seams. Targeted formatting/lint pass. No service/account/VM, power-loss/reboot, durable archive or active mutation qualification is claimed; A1-A4 remain UNREVIEWED and launchAllowed=false.