Add controller sovereignty toolkit#33
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.
Summary
Adds the initial SourceOS controller-sovereignty toolkit to
sourceos-syncd.This PR introduces a sanitized, read-only lane for modeling autonomous platform controllers as first-class state-integrity actors. It deliberately avoids committing raw local diagnostics, private identifiers, hostnames, IPs, SSIDs/BSSIDs, packet payloads, or personal file paths.
What changed
docs/controller-sovereignty/.tools/controller-inventory.sh, a non-mutating local controller inventory collector.tools/resource-event-summary.py, a summary parser for local diagnostic reports supplied explicitly by the operator.Design thesis
No hidden autonomous controller may consume material resources without registration, budget, logging, and revocation.
This extends the
sourceos-syncdstate-integrity mission from replicated state to operating-system behavior: background controllers must become observable, attributable, budgeted, and explainable before automation is allowed to act.Safety / privacy boundaries
Validation
Connector-side compare shows this branch is 6 commits ahead of
mainand adds six files:docs/controller-sovereignty/README.mddocs/controller-sovereignty/case-file-template.mddocs/controller-sovereignty/controller-registry.schema.yamldocs/controller-sovereignty/sovereignty-dashboard.mdtools/controller-inventory.shtools/resource-event-summary.pyA CI workflow was intentionally not landed in this PR because the connector blocked the workflow payload. The tooling itself remains read-only and reviewable.