docs: reprioritize post-v1.0 roadmap by risk (security first, feature…#13
Merged
Conversation
…s last) Reorganize the post-v1.0 queue in DESIGN.md sec.7 and the v1.0-review.md follow-ups table into five tiers ordered by risk rather than by milestone number: * Tier S - security & correctness (next patch line, v1.0.x): SEC-PROXY-1 (proxy query/body fidelity + deny redaction, sibling repo), SEC-MTLS-1 (XFCC trust=true must require an anchor), TEST-RACE-1 (root-cause the configstream race flake). * Tier A - hardening (v1.1): F-PLUGIN-2, K-AUTHN-2, K-DOS-1, M10-PLUGIN-LIFECYCLE supervisor half, K-CRYPTO-2. * Tier B - quality / coverage (v1.1): M12-CONF-MATRIX, M12-BROKER-MW, DOC-OPENAPI-1. * Tier C - new features (v1.1+): M7-SPICEDB, DOC-COOKBOOK-1. * Tier X - experimental (no firm target): eBPF data plane, WASM plugins. Original numeric IDs (16-27) preserved in parentheses so existing references resolve. Added a 'Prioritization rationale' subsection capturing the rule: never ship a new feature on top of a known security or correctness gap; tier C cannot be picked up while any tier-S item is open. The sibling repos (proxy, idp, plugins, ebpf) inherit this ordering.
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.
…s last)
Reorganize the post-v1.0 queue in DESIGN.md sec.7 and the v1.0-review.md follow-ups table into five tiers ordered by risk rather than by milestone number:
Tier S - security & correctness (next patch line, v1.0.x): SEC-PROXY-1 (proxy query/body fidelity + deny redaction, sibling repo), SEC-MTLS-1 (XFCC trust=true must require an anchor), TEST-RACE-1 (root-cause the configstream race flake).
Tier A - hardening (v1.1): F-PLUGIN-2, K-AUTHN-2, K-DOS-1, M10-PLUGIN-LIFECYCLE supervisor half, K-CRYPTO-2.
Tier B - quality / coverage (v1.1): M12-CONF-MATRIX, M12-BROKER-MW, DOC-OPENAPI-1.
Tier C - new features (v1.1+): M7-SPICEDB, DOC-COOKBOOK-1.
Tier X - experimental (no firm target): eBPF data plane, WASM plugins.
Original numeric IDs (16-27) preserved in parentheses so existing references resolve. Added a 'Prioritization rationale' subsection capturing the rule: never ship a new feature on top of a known security or correctness gap; tier C cannot be picked up while any tier-S item is open. The sibling repos (proxy, idp, plugins, ebpf) inherit this ordering.