Repository navigation
Document POC assumptions - #1
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
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 changed
Adds a prominent POC assumptions table to the public README and links it to the
detailed assumptions register and threat model.
Why
The prototype depends on hypotheses about its HTTP boundary, available identity
and telemetry, latency and failure behavior, enforcement options, error costs,
retention, scale, and synthetic evaluation. Making those assumptions visible
near the top of the repository lets reviewers judge the design without
mistaking POC choices for production facts.
Impact
Documentation only. No runtime behavior changes.
Validation
git diff --checkREADME.md