All tasks resolved: T01, T02, T03, T04, T06 and T07 done, T05 cancelled. The workplan delivered the governed repository, the Mode of Authority vocabulary at v0.2.0, the federation interface card, three decisions, the concept-placement record and the reference-impact survey. It also concluded that the migration it was preparing should not happen. The material this canon was meant to receive is load-bearing where it sits, and SecurityCanon's real contribution is an architecture-layer vocabulary that InfoTechCanon does not have, so it is an extension canon rather than a destination for extracted material. Nothing moves; the boundary holds by declared imports, twelve InfoTechCanon concepts pinned and nine owned here. SCOPE.md carries the three open questions to their answers rather than leaving them carried, and points at the placement record and the survey. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Assistant: claude-code Assistant-Model: opus Assistant-Process: 3588@bnt-lap001 Assistant-Session: 24b80f66-e5a7-4e61-99fe-2d422e6d17da |
||
|---|---|---|
| .repo-manager | ||
| decisions | ||
| docs | ||
| history | ||
| infospace | ||
| research | ||
| workplans | ||
| .custodian-brief.md | ||
| .repo-classification.yaml | ||
| AGENTS.md | ||
| INTENT.md | ||
| README.md | ||
| SCOPE.md | ||
| WORK-RECORDS.md | ||
security-canon
Orthogonal vocabulary and canonical model for security-related concepts.
SecurityCanon extends InfoTechCanon with a focused security domain model, in the same architectural role that CommerceCanon holds for commercial terminology and InterfaceCanon for interface terminology.
Its subject is architecture, not implementation: the relationships in which
authority is exercised, described before and independently of the mechanisms
that enforce them. Its first contribution is the Mode of Authority vocabulary
— seven auth modes (USE, OBSERVE, OPERATE, ADMINISTER, GOVERN,
CONSTRUCT, SOVEREIGN) read relative to a scope. CARING and the access-control
and identity models stay in InfoTechCanon, at the implementation layer and as
shared roots; see SEC-ADR-001.
| Flavor | project |
| Domain | infotech |
| Workplan prefix | SECURITY-WP- |
| Upstream canon | InfoTechCanon |
| Service surface | none — reuses InfoTechCanon's |
Start with INTENT.md and SCOPE.md. Agent instructions are in AGENTS.md; active work is in workplans/.
| Document | What it holds |
|---|---|
| SEC-ADR-001 | the boundary decision — what stays upstream, and why |
| SEC-ADR-002 | the terminology separation — why AuthorityContext, not Subject |
| Mode of Authority assessment | review of the v0.1 draft and the proposed canon structure |
| Actor/Subject implications | the one open terminology question, analysed |
Status
Draft. The Mode of Authority vocabulary is published as a canon artifact with
machine-readable modes and dimensions; the v0.1 research draft is retained in
research/ as provenance. Stable promotion needs reviewed mappings and concrete
consumer evidence. See
SECURITY-WP-0001.
Orientation
| Start here | For |
|---|---|
| Vocabulary card | the seven modes and the notation, on one page |
| Mode of Authority | the canon artifact |
| Disambiguation | operator or OPERATE? role, plane, or mode? |
| Mapping to InfoTechCanon | how it relates to the access-control model and CARING |