tegwick
8ab4891043
Insert DevOps Secrets Management Canon v1.0 unchanged, with a placement preface that keeps shared roots upstream. Publish it on the federation card. Assistant: grok Assistant-Session: 01a12ce1-7ded-7e03-a845-2ece8a573af4
2 KiB
Canon federation interface
The interface card publishes this canon's federation boundary under accepted ADR-006.
- info-tech-canon interface — shared-concept upstream
- SecurityCanon boundary review — InfoTechCanon-side acceptance of this extension boundary
- interface-canon interface
- commerce-canon interface
- the-custodian interface
SecurityCanon exports two surfaces. sec-authority is the architecture-layer
Mode of Authority
vocabulary. sec-dsm is the
DevOps Secrets Management Standard.
It imports shared roots from InfoTechCanon and redefines none of
them; the pinned manifest records
each vocabulary source path and content hash at the declared commit.
Reciprocal navigation does not imply reciprocal semantic imports. InfoTechCanon retains the shared roots, CARING, the access-control model and the identity model; see SEC-ADR-001.
The G7 validator in prj-canon-federation currently pins card paths for
info-tech-canon, commerce-canon and the-custodian. Adding security-canon to
CARD_PATHS is that project's change to make; this card is written to satisfy
the same contract in the meantime.
Concept placement across the two canons — one owning canon and one import direction per shared concept — is recorded in concept-placement.md (SECURITY-DEC-2026-003).