Repository navigation
docs: align README and canonical docs with current governed runtime - #191
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.
Phase 55 — current capability documentation alignment
This docs-only phase updates the portfolio landing pages and canonical engineering documents to match the actual current
mainbehavior after v1.2/v1.3 and the post-v1.3 hardening through Phase 54.Concrete gap
Several public documents still described the active security surface as the v1.1 governed-action snapshot or stopped at the earlier authenticated MCP experiment, while the code and canonical Governed Agent Actions document already include approval lifecycle/revocation, approver authorization, typed executor-failure evidence, authenticated failure composition, MCP uncertain-execution protocol handling, Agno failure-provenance preservation, and cross-framework failure conformance.
Updated documentation
README.mdandREADME.pt-br.mdare synchronized around the current trust model and project status;docs/README.mdnow maps authentication, source-aware authorization, approval lifecycle, approver authorization, and typed executor-failure evidence;docs/EXECUTIVE_OVERVIEW.mdnow presents the current governed-runtime capabilities and evidence boundaries;docs/ARCHITECTURE.mdnow documents the complete authority chain from presented credential/authentication through authorization, approval lifecycle, approver authorization, execution, and typed governed failure evidence;docs/MCP.mdnow documents the authenticated experiment and uncertain post-executorMCPErrorprotocol classification;docs/DEVELOPMENT.mdnow defines mutable executor-failure provenance and retry-ownership invariants;docs/AGENTIC_FAST_TRACK.mdnow summarizes the current implemented state;docs/FRAMEWORK_DECISION_MATRIX.mdnow incorporates governed-action conformance into its qualitative framework/security interpretation.docs/security/GOVERNED_AGENT_ACTIONS.mdremains the detailed canonical source because it was already current and no factual inconsistency was found.Release/evidence discipline
The documentation explicitly distinguishes:
v1.3.0 — Human Approval Lifecycle;main: v1.1/v1.2/v1.3 capabilities plus post-v1.3 hardening for approver authorization, typed executor-failure provenance, authenticated failure composition, MCP uncertain-execution handling, Agno failure-provenance preservation, and cross-framework failure conformance.No published release metadata or accepted historical provider-backed evaluation artifact is rewritten.
Security boundaries preserved
The updated docs do not claim remote transport-bound identity, OAuth/OIDC/JWT/mTLS, durable/distributed approval, production IAM, idempotency, rollback/compensation, two-phase commit, external transactionality, or signed/tamper-proof audit evidence.
They preserve the current invariants that:
execution_attempted=true,failure_reason=executor_error, andexternal_side_effect_state=unknown;Final scope
The clean PR diff contains exactly nine documentation files:
README.md;README.pt-br.md;docs/AGENTIC_FAST_TRACK.md;docs/ARCHITECTURE.md;docs/DEVELOPMENT.md;docs/EXECUTIVE_OVERVIEW.md;docs/FRAMEWORK_DECISION_MATRIX.md;docs/MCP.md;docs/README.md.No production code, dependency, workflow helper, historical artifact, tag, or published release remains changed.
CI evidence
Final clean CI #495 passed on exact head:
383f73012e840ae9deddf09540d02efb1c74a312Quality evidence:
Temporary guarded documentation helpers were removed before this final CI.
Closes #190