spec: add @sensitive annotation + report redaction (RFC-001 §6.7) - #107
Merged
Conversation
Settles the secrets-annotation story (#90) before annotations.proto freezes (#58): - annotations.proto: canonical marker `annotation sensitive;` — classification, not protection; class taxonomy deferred additively - new RFC-001 §6.7: placement/propagation, normative consumer minima (render-surface redaction to [REDACTED], report redaction, no doc examples), standard 50400 carrier, chameleon orthogonality - report.proto: EnrichedViolation.value_redacted = 7 so redaction is distinguishable from three-state absence; §7 excerpt synced - §13: two new deferrals (class taxonomy; @Encrypted(key_ref) / chameleon interplay) Closes #90
71 tasks
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.
Settles the secrets-annotation story before
annotations.protofreezes (#58). Decision issue: #90.What
proto/schema/v1/annotations.proto: canonical markerannotation sensitive;(betweendeprecatedandhttp).@sensitive)": attaches to fields, type aliases (macro-expands to consuming fields), and messages (transitive through message-typed fields). Classification, not protection — wire encoding, storage, programmatic access, validation semantics unaffected.[REDACTED]; engines MUST withhold offending values from reports; doc generators MUST NOT emit values/examples (@exampleon a sensitive declaration = compile-time warning).proto/schema/v1/report.proto:EnrichedViolation.value_redacted = 7— keeps redaction distinguishable from three-state absence; §7 excerpt synced.class:param, provably additive later) and schema-level key-reference annotation (@encrypted(key_ref)) / chameleon interplay.docs/RFC-001-issues.md(new deps(vscode): bump the vscode-minor-and-patch group in /editors/vscode with 2 updates #21 entry, second commit).Key decisions
@sensitive(not@secret): doesn't overpromise key-material handling; generalizes to future classes.AnnotationListcarrier; no new extension numbers.Pre-existing
buf builderrors (report.protoimport path,annotations.protov1.2 grammar) are unchanged — verified identical on main.Closes #90