Spec: Mutation and Evidence Accountability v0.1#96
Draft
Conversation
This was referenced May 6, 2026
Open
Contributor
Author
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.
Summary
This draft PR adds the first SourceOS Mutation and Evidence Accountability specification slice.
It includes:
MutationReceipt,ExecutionContextReceipt,ServiceWorkReceipt, andEvidencePipelineReceipt, with specialized subtypes for browser writes, delegated I/O, sync cycles, folder sizing, archive extraction, diagnostic self-noise, UI/compositor work, path boundaries, evidence routing, and related receipt families.Mutation Evidence Accountability.Motivation
This is based on the forensic design review of opaque OS logs. The core lesson is that an OS can enforce policy, collect telemetry, and still fail the operator if it cannot explain actor, object, operation, policy, resource cost, causality, delegated mutation, execution context, and evidence gaps.
The key security doctrine captured here is:
The Firefox extension-inventory correction is also captured:
The broader stack doctrine is:
Validation
GitHub Actions is passing on the latest head commit.
Mutation Evidence Accountability3b27da4bf00f7a614a4cdb942e131015f9b8be67The validator now covers:
Follow-up implementation targets
After this spec lands, implementation should fan out to:
SourceOS-Linux/BearBrowserfor browser coalition/profile/storage/origin receipts and no-extension attribution guardrails.SourceOS-Linux/TurtleTermfor terminal/session/archive/diagnostic mutation receipts.SourceOS-Linux/sourceos-shellforsourceosctl explain, evidence topology, and mutation graph UI.SourceOS-Linux/sourceos-syncdfor delegated sync, full-sync-risk, scheduler, object-transfer, and temp-artifact receipts.SourceOS-Linux/sourceos-devtoolsfor validators, CLI tooling, CI gates, and anti-pattern fixtures.SourceOS-Linux/sourceos-bootfor boot evidence topology and cross-reboot session IDs.SocioProphet/prophet-platformfor evidence-console and FogStack manifest integration.ontogenesisfor ontology classes and SHACL gates.Exodusfor migration artifact taxonomy and temp/cache exclusion logic.Notes
This PR intentionally lands the contract first. It does not yet implement runtime instrumentation.