- schemes/README.md: note the wire vocabulary (sensitive) is the lowest-common-
denominator floor and schemes refine it; producers are encouraged to emit both.
- schemes/data-class.md: add an explicit emit-both guideline in graceful
degradation; correct the changelog date 2026-06-17 -> 2026-06-16.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
- schemes/data-class.md: skeleton for the structured classification taxonomy the
trust-annotations 'sensitive' boolean deliberately omits (class + regulatory
scope + org labels), shaped as open questions and attributed to the SEP-1913
reviewers who pushed for it (JustinCappos, olaservo, Mossaka, krubenok, localden).
- schemes/README.md: list data-class under 'Schemes here'; add verified label-
scheme candidates (Permissive IFC 2410.03055, AirGapAgent 2405.05175); move
CaMeL and the design-pattern catalogue into a new 'Not schemes: host
architectures' section, since they govern host control-flow rather than
producing a per-result data label.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Move the FIDES information-flow-control draft out of
specification/draft/ and into schemes/ifc-fides.md, reframed from a
sibling extension into one data-labelling scheme that fills the
trust-annotations evidenceRef slot (type ifc.fides.v1). FIDES is not an
extension and not a peer of the extensions; it is one interchangeable
filler of the slot.
Add schemes/README.md as the index for the folder: it states what a
scheme is, lists FIDES as the worked example, records the range of
candidate schemes raised in SEP-1913 review (data classification,
design-pattern controls, ShardGuard, capability tokens, cosigning,
sequence-shape, attestation), and sets the bar a scheme doc must meet.
The reviewed normative body (label payload, semantics, reader-set
resolution, reference implementation, open questions) is preserved
verbatim from the JoannaaKL / Rul1an review rounds.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
