Repository navigation
docs: declare governed-runtime boundaries and streamline portfolio README - #193
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
This docs-only change makes current governed-runtime scope boundaries explicit and streamlines the repository landing pages for faster portfolio review.
README alignment
README.mdsemantically aligned in English;v1.3.0) distinct from post-v1.3 hardening on currentmain.New accepted boundary ADRs
These ADRs document current limits, intended future designs, and explicit revisit triggers. They do not claim that signing/hash chaining, distributed approval, reconciliation, idempotency, or an external PDP are already implemented.
Scope
Exactly six documentation files differ from
main:README.md;README.pt-br.md;docs/adr/0009-tamper-evident-execution-evidence.md;docs/adr/0010-approval-authority-is-single-process.md;docs/adr/0011-uncertain-external-side-effects-idempotency-and-reconciliation.md;docs/adr/0012-exact-scope-authorization-and-external-pdp-boundary.md.No production code, dependencies, workflows, benchmark artifacts, tags, or published release metadata are changed.
Closes #192