security-canon/infospace/vocabulary
tegwick e159fe7a1b Correct five import names that do not resolve upstream (T04 audit)
InfoTechCanon re-verified this boundary against its enlarged ownership index
under INFO-WP-0027-T04. The original manifest was verified by file hash, which
every entry passed; nothing checked that the named concept exists in the named
file. Five of twelve did not.

Artifact becomes CanonArtifact, which is what Core defines; bare Artifact now
resolves to the DevSecOps build artifact, a different concept. Relationship
becomes RelationshipDefinition, since the identity model owns Relationship as
its actor-linking taxonomy. Ownership moves to the Organization Model, which the
kernel map names as its owner. AccessOperations becomes Operation, the upstream
name. PrincipalType stops being an import: the identity model does not define
it, and it is SecurityCanon's own classification of the imported Principal.

Eleven imports remain, no concept is contested, and no semantic disposition
changes.

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
2026-09-20 23:27:30 +02:00
..
mode-of-authority Correct five import names that do not resolve upstream (T04 audit) 2026-09-20 23:27:30 +02:00