docs: add layer overview and per-layer scenarios#7
Open
heijiLee wants to merge 1 commit into
Open
Conversation
Contributor
Author
|
@0xMuang Please make sure my understanding is correct. |
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
docs/layers-overview.md: onboarding-oriented summary of the five layers (Token & Identity, Compliance Policy, Execution & Routing, Venue/Adapter, Deployment & Operations) with each layer's core question, rejection point, and the components that own it.docs/layer-scenarios.md: per-layer success / pre-execution-reject / mid-execution-revert scenarios so newcomers can see what input each layer decides on and where atomic rollback happens.architecture/,MVP-v2-multi-venue.md, andROADMAP.mdas the source of truth — these are reading aids, not specs.Test plan
architecture/README.md.