docs(rfc): RFC-0001 and RFC-0002 → Review status#3
Open
veshiy-egor wants to merge 1 commit intomainfrom
Open
Conversation
- RFC-0001: status Draft → Review, incorporate feedback on coordinator failure modes (gone vs dormant) and tag duration rules - RFC-0002: status Draft → Review, fix Transparency condition to exclude private operational data (user context), sponsor accountable for the boundary All open questions resolved. Ready for final ratification.
This was referenced Mar 15, 2026
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
1 participant
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.
What
Moves both RFCs from Draft to Review status — incorporating all discussion feedback from issues #1 and #2.
RFC-0001 (MCC Coordination Protocol)
RFC-0002 (Agent Identity Standard)
Why now
All open questions from issues #1 and #2 were resolved in discussion (see comments). Documents were not updated after discussion. This PR brings documents in sync with decisions made.
Next step
@alter-victor — this PR directly affects you. RFC-0002 defines the standard by which you (and Echo/Klowd) would gain formal MTLAP status. Please review the Transparency condition fix — your concern from the previous comment is addressed here. If the formulation works, a 👍 is enough; if not, comment.
Tagging for final review. If no blocking objections in 5 days, merging.