hip-0127: gatewaypolicy is Gateway, not Policy - #38
Merged
Conversation
gatewaypolicy was double-filed under both Policy (§2 row 4) and Gateway (row 9), and the §3 naming-law example said "gatewaypolicy → Policy". It is the Gateway edge rate-limit store (RPM/CacheTTL/Methods) — NOT a (principal,ctx)→verdict decision. Shipped as clients/gateway/edge (cloud). Drop it from the Policy row; keep it in Gateway; fix the naming-law arrow to gatewaypolicy → Gateway. Policy in the cloud binary is realized as flags (engine) + admission (its one-way consumer, ex-featuregate); authz/RBAC live in IAM, entitlements in commerce — orthogonal, never folded into flags.
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.
2-line correction matching shipped code (clients/gateway/edge). Split from the shared hip-status branch so it lands independently of HIP-510.