Canon 0.6.0 freeze: ITC-CAP draft, AVT catalog, joinable review
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
CI Smoke / container-smoke (push) Successful in 1s

Finish ITC-WP-0013 (AttributeValueType under ITC-DATA) and ITC-WP-0014
T02/T03/T05/T06/T07. Capability contract schemas, live-catalog review
CLI, landscape/kernel-map pointers. Sit on this version.
This commit is contained in:
tegwick 2026-08-15 19:42:30 +02:00
parent 7805560a60
commit d453e17952
44 changed files with 1485 additions and 137 deletions

View file

@ -0,0 +1,29 @@
---
id: agent-brief/catalog-attribute-value-types
artifact_id: catalog/attribute-value-types
source_path: models/data/attribute-value-types.yaml
source_kind: concept-catalog
generated: true
---
<!-- GENERATED by info_tech_canon; do not edit by hand. -->
# Agent Brief: InfoTechCanon Attribute Value Type Catalog
- Artifact ID: `catalog/attribute-value-types`
- Kind: `concept-catalog`
- Canonical path: `models/data/attribute-value-types.yaml`
- Full source: `models/data/attribute-value-types.yaml`
- Summary: Structured candidate concept catalog: InfoTechCanon Attribute Value Type Catalog.
## Retrieval Hints
No imports or anchors recorded.
## Owned Concepts
- `InfoTechCanon Attribute Value Type Catalog`
## Related Distinctions
No common distinction is anchored directly on this artifact.

View file

@ -0,0 +1,29 @@
---
id: agent-brief/mapping-capability-anchors
artifact_id: mapping/capability-anchors
source_path: mappings/capability-anchors.yaml
source_kind: mapping
generated: true
---
<!-- GENERATED by info_tech_canon; do not edit by hand. -->
# Agent Brief: ITC-CAP concept mappings to anchoring canon models
- Artifact ID: `mapping/capability-anchors`
- Kind: `mapping`
- Canonical path: `mappings/capability-anchors.yaml`
- Full source: `mappings/capability-anchors.yaml`
- Summary: Mapping artifact connecting canon surfaces: ITC-CAP concept mappings to anchoring canon models.
## Retrieval Hints
No imports or anchors recorded.
## Owned Concepts
- `ITC-CAP concept mappings to anchoring canon models`
## Related Distinctions
No common distinction is anchored directly on this artifact.

View file

@ -5,8 +5,8 @@
This brief summarizes the current canon service surface for agents.
- Infospace slug: `canon`
- Artifact count: 66
- Retrieval index items: 66
- Artifact count: 68
- Retrieval index items: 68
- Primary confidence command: `make validate`
- Refresh generated indexes and views with: `make index`
- Refresh agent briefs and interface templates with: `make agent-briefs`

View file

@ -43,7 +43,7 @@
}
],
"infospace": "canon",
"item_count": 66,
"item_count": 68,
"items": [
{
"canonical_path": "assimilation/it-capability-canon/ASSIMILATION.md",
@ -267,6 +267,20 @@
"title": "InfoTechCanon Capability Catalog",
"warnings": []
},
{
"canonical_path": "models/data/attribute-value-types.yaml",
"id": "catalog/attribute-value-types",
"imports": [],
"kind": "concept-catalog",
"owned_concepts": [
"InfoTechCanon Attribute Value Type Catalog"
],
"relationships": [],
"source_path": "demand/AttributeValueTypes.md",
"summary": "Structured candidate concept catalog: InfoTechCanon Attribute Value Type Catalog.",
"title": "InfoTechCanon Attribute Value Type Catalog",
"warnings": []
},
{
"canonical_path": "models/governance/evidence-basis.yaml",
"id": "catalog/evidence-basis",
@ -1024,6 +1038,10 @@
"target": "model/observability",
"type": "maps"
},
{
"target": "model/capability",
"type": "maps"
},
{
"target": "standard/tagging",
"type": "maps"
@ -1038,6 +1056,20 @@
"title": "InfoTechCanon Kernel Map",
"warnings": []
},
{
"canonical_path": "mappings/capability-anchors.yaml",
"id": "mapping/capability-anchors",
"imports": [],
"kind": "mapping",
"owned_concepts": [
"ITC-CAP concept mappings to anchoring canon models"
],
"relationships": [],
"source_path": "infospace/assimilation/it-capability-canon/mappings.yaml",
"summary": "Mapping artifact connecting canon surfaces: ITC-CAP concept mappings to anchoring canon models.",
"title": "ITC-CAP concept mappings to anchoring canon models",
"warnings": []
},
{
"canonical_path": "mappings/purpose-demand-governance-candidates.yaml",
"id": "mapping/purpose-demand-governance-candidates",
@ -1158,6 +1190,10 @@
{
"target": "assimilation/it-capability-canon",
"type": "derived_from"
},
{
"target": "mapping/capability-anchors",
"type": "introduces"
}
],
"source_path": "infospace/assimilation/it-capability-canon/source/ITCapabilityCanonV0.1.md",
@ -1184,6 +1220,10 @@
{
"target": "model/governance",
"type": "uses"
},
{
"target": "catalog/attribute-value-types",
"type": "introduces"
}
],
"source_path": "seeds/InfoTechCanonDataModel_RC1_seed.md",

View file

@ -4,7 +4,7 @@
Schema: `info-tech-canon.retrieval-index.v1`
Infospace: `canon`
Items: **66**
Items: **68**
## Common Distinctions
@ -85,6 +85,16 @@ Items: **66**
- Imports and anchors: none
- Owned concepts: `InfoTechCanon Capability Catalog`
### InfoTechCanon Attribute Value Type Catalog
- ID: `catalog/attribute-value-types`
- Kind: `concept-catalog`
- Canonical path: `models/data/attribute-value-types.yaml`
- Source path: `demand/AttributeValueTypes.md`
- Summary: Structured candidate concept catalog: InfoTechCanon Attribute Value Type Catalog.
- Imports and anchors: none
- Owned concepts: `InfoTechCanon Attribute Value Type Catalog`
### InfoTechCanon Evidence Basis Catalog
- ID: `catalog/evidence-basis`
@ -285,6 +295,16 @@ Items: **66**
- Imports and anchors: none
- Owned concepts: `InfoTechCanon Kernel Map`
### ITC-CAP concept mappings to anchoring canon models
- ID: `mapping/capability-anchors`
- Kind: `mapping`
- Canonical path: `mappings/capability-anchors.yaml`
- Source path: `infospace/assimilation/it-capability-canon/mappings.yaml`
- Summary: Mapping artifact connecting canon surfaces: ITC-CAP concept mappings to anchoring canon models.
- Imports and anchors: none
- Owned concepts: `ITC-CAP concept mappings to anchoring canon models`
### Purpose Demand Governance Extension Candidates
- ID: `mapping/purpose-demand-governance-candidates`

View file

@ -1,6 +1,6 @@
schema: info-tech-canon.retrieval-index.v1
infospace: canon
item_count: 66
item_count: 68
items:
- id: assimilation/it-capability-canon
kind: assimilation
@ -144,6 +144,18 @@ items:
imports: []
relationships: []
warnings: []
- id: catalog/attribute-value-types
kind: concept-catalog
title: InfoTechCanon Attribute Value Type Catalog
canonical_path: models/data/attribute-value-types.yaml
source_path: demand/AttributeValueTypes.md
summary: 'Structured candidate concept catalog: InfoTechCanon Attribute Value Type
Catalog.'
owned_concepts:
- InfoTechCanon Attribute Value Type Catalog
imports: []
relationships: []
warnings: []
- id: catalog/evidence-basis
kind: concept-catalog
title: InfoTechCanon Evidence Basis Catalog
@ -630,11 +642,25 @@ items:
target: model/network
- type: maps
target: model/observability
- type: maps
target: model/capability
- type: maps
target: standard/tagging
- type: maps
target: standard/caring
warnings: []
- id: mapping/capability-anchors
kind: mapping
title: ITC-CAP concept mappings to anchoring canon models
canonical_path: mappings/capability-anchors.yaml
source_path: infospace/assimilation/it-capability-canon/mappings.yaml
summary: 'Mapping artifact connecting canon surfaces: ITC-CAP concept mappings to
anchoring canon models.'
owned_concepts:
- ITC-CAP concept mappings to anchoring canon models
imports: []
relationships: []
warnings: []
- id: mapping/purpose-demand-governance-candidates
kind: mapping
title: Purpose Demand Governance Extension Candidates
@ -721,6 +747,8 @@ items:
target: capability-catalog/itc-cap
- type: derived_from
target: assimilation/it-capability-canon
- type: introduces
target: mapping/capability-anchors
warnings: []
- id: model/data
kind: model
@ -739,6 +767,8 @@ items:
target: kernel/itc-core
- type: uses
target: model/governance
- type: introduces
target: catalog/attribute-value-types
warnings: []
- id: model/devsecops
kind: model

View file

@ -41,6 +41,8 @@ artifacts:
target: model/network
- type: maps
target: model/observability
- type: maps
target: model/capability
- type: maps
target: standard/tagging
- type: maps
@ -135,6 +137,8 @@ artifacts:
target: capability-catalog/itc-cap
- type: derived_from
target: assimilation/it-capability-canon
- type: introduces
target: mapping/capability-anchors
- id: catalog/evidence-basis
path: models/governance/evidence-basis.yaml
kind: concept-catalog
@ -224,6 +228,16 @@ artifacts:
target: kernel/itc-core
- type: uses
target: model/governance
- type: introduces
target: catalog/attribute-value-types
- id: catalog/attribute-value-types
path: models/data/attribute-value-types.yaml
kind: concept-catalog
title: InfoTechCanon Attribute Value Type Catalog
provenance:
source_path: demand/AttributeValueTypes.md
placement_workplan: ITC-WP-0013
relationships: []
- id: model/devsecops
path: models/devsecops/InfoTechCanonDevSecOpsModel.md
kind: model
@ -609,6 +623,14 @@ artifacts:
target: model/governance
- type: uses
target: model/task
- id: mapping/capability-anchors
path: mappings/capability-anchors.yaml
kind: mapping
title: ITC-CAP concept mappings to anchoring canon models
provenance:
source_path: infospace/assimilation/it-capability-canon/mappings.yaml
placement_workplan: ITC-WP-0014
relationships: []
- id: example/consumer-purpose-portfolio
path: examples/consumer-purpose-portfolio.yaml
kind: example

View file

@ -52,7 +52,10 @@ evaluations still have no owning model. The trigger remains open for those.
The source sketches a validator (§18) comparing product requirements to provider
maturity. That belongs to the service surface (`ITC-WP-0002`) and needs the
contract schema first. **Deferred:** ITC-WP-0014.
contract schema first.
**Resolved 2026-08-15 (canon 0.6.0).** `info-tech-canon capability-review`
joins a consumer record to the live catalog. ITC-WP-0014 T06 done.
## OQ-7 — Relationship between `CapabilityProfile` and canon `Profile`

View file

@ -1,5 +1,5 @@
root: infospace
file_count: 176
file_count: 183
files:
- path: README.md
directory: .
@ -22,6 +22,9 @@ files:
- path: agent/briefs/benchmark-caring-kubernetes-rbac.md
directory: agent/briefs
name: benchmark-caring-kubernetes-rbac.md
- path: agent/briefs/catalog-evidence-basis.md
directory: agent/briefs
name: catalog-evidence-basis.md
- path: agent/briefs/comparison-repo-scoping-canon-benefit-analysis.md
directory: agent/briefs
name: comparison-repo-scoping-canon-benefit-analysis.md
@ -334,6 +337,9 @@ files:
- path: mappings/README.md
directory: mappings
name: README.md
- path: mappings/capability-anchors.yaml
directory: mappings
name: capability-anchors.yaml
- path: mappings/purpose-demand-governance-candidates.yaml
directory: mappings
name: purpose-demand-governance-candidates.yaml
@ -349,6 +355,12 @@ files:
- path: models/data/InfoTechCanonDataModel.md
directory: models/data
name: InfoTechCanonDataModel.md
- path: models/data/attribute-value-types-alignment.md
directory: models/data
name: attribute-value-types-alignment.md
- path: models/data/attribute-value-types.yaml
directory: models/data
name: attribute-value-types.yaml
- path: models/devsecops/InfoTechCanonDevSecOpsModel.md
directory: models/devsecops
name: InfoTechCanonDevSecOpsModel.md
@ -451,6 +463,15 @@ files:
- path: schemas/assimilation.schema.yaml
directory: schemas
name: assimilation.schema.yaml
- path: schemas/attribute-value-type.schema.yaml
directory: schemas
name: attribute-value-type.schema.yaml
- path: schemas/capability-record.schema.yaml
directory: schemas
name: capability-record.schema.yaml
- path: schemas/capability.schema.yaml
directory: schemas
name: capability.schema.yaml
- path: schemas/concept.schema.yaml
directory: schemas
name: concept.schema.yaml

View file

@ -1,4 +1,4 @@
concept_count: 108
concept_count: 110
concepts:
- concept: "Assimilation \u2014 IT Capability Canon (ITCC) v0.1"
owner: assimilation/it-capability-canon
@ -28,6 +28,10 @@ concepts:
owner: capability-catalog/itc-cap
path: models/capability/capabilities.yaml
source: artifact_title
- concept: InfoTechCanon Attribute Value Type Catalog
owner: catalog/attribute-value-types
path: models/data/attribute-value-types.yaml
source: artifact_title
- concept: InfoTechCanon Evidence Basis Catalog
owner: catalog/evidence-basis
path: models/governance/evidence-basis.yaml
@ -108,6 +112,10 @@ concepts:
owner: kernel/itc-kernel-map
path: kernel/InfoTechCanonKernelMap.md
source: artifact_title
- concept: ITC-CAP concept mappings to anchoring canon models
owner: mapping/capability-anchors
path: mappings/capability-anchors.yaml
source: artifact_title
- concept: Purpose Demand Governance Extension Candidates
owner: mapping/purpose-demand-governance-candidates
path: mappings/purpose-demand-governance-candidates.yaml

View file

@ -6,6 +6,7 @@ artifacts:
- benchmark/caring/kubernetes-rbac/findings
- benchmark/caring/kubernetes-rbac/native-concepts
- capability-catalog/itc-cap
- catalog/attribute-value-types
- catalog/evidence-basis
- comparison/repo-scoping/canon-benefit-analysis
- comparison/repo-scoping/consumer-workplan-brief
@ -26,6 +27,7 @@ artifacts:
- example/consumer-purpose-portfolio
- kernel/itc-core
- kernel/itc-kernel-map
- mapping/capability-anchors
- mapping/purpose-demand-governance-candidates
- model/access-control
- model/capability
@ -134,6 +136,8 @@ rows:
- maps
- artifact: capability-catalog/itc-cap
targets: {}
- artifact: catalog/attribute-value-types
targets: {}
- artifact: catalog/evidence-basis
targets: {}
- artifact: comparison/repo-scoping/canon-benefit-analysis
@ -354,6 +358,8 @@ rows:
- maps
model/access-control:
- maps
model/capability:
- maps
model/data:
- maps
model/devsecops:
@ -378,6 +384,8 @@ rows:
- maps
standard/tagging:
- maps
- artifact: mapping/capability-anchors
targets: {}
- artifact: mapping/purpose-demand-governance-candidates
targets:
model/governance:
@ -404,6 +412,8 @@ rows:
- uses
kernel/itc-core:
- conforms_to
mapping/capability-anchors:
- introduces
model/governance:
- uses
model/landscape:
@ -414,6 +424,8 @@ rows:
- uses
- artifact: model/data
targets:
catalog/attribute-value-types:
- introduces
kernel/itc-core:
- conforms_to
model/governance:

View file

@ -48,6 +48,9 @@ schemas:
interface-card: schemas/interface-card.schema.yaml
agent-brief: schemas/agent-brief.schema.yaml
workplan: schemas/workplan.schema.yaml
capability: schemas/capability.schema.yaml
capability-record: schemas/capability-record.schema.yaml
attribute-value-type: schemas/attribute-value-type.schema.yaml
workflows: []
viability:
redundancy_ratio:

View file

@ -49,6 +49,7 @@ InfoTechCanonDataModel
InfoTechCanonDevSecOpsModel
InfoTechCanonNetworkModel
InfoTechCanonObservabilityModel
InfoTechCanonCapabilityModel
```
Together they form a coherent first-generation semantic substrate for building interoperable information-processing systems.
@ -69,6 +70,7 @@ Data = datasets, schemas, classification, lineage, quality, contrac
DevSecOps = source-to-artifact-to-release-to-deployment delivery flow and evidence.
Network = addressing, topology, routing, policy, reachability, flow, exposure, and state.
Observability = telemetry, signals, logs, metrics, traces, events, alerts, SLOs, and evidence.
Capability = what an information system must be able to do, independently of how.
```
---
@ -444,6 +446,23 @@ Network owns communication and reachability. Observability owns signals and runt
| ObservedIncident | Observability / Task or ITSM reference |
| ObservabilityEvidence | Observability / Governance reference |
## 4.14 Capability Owns Abilities
| Concept Family | Canonical Owner |
|---|---|
| Capability / CapabilityProfile | Capability |
| CapabilityRequirement / CapabilityProvision | Capability |
| CapabilityMaturityLevel | Capability |
| CapabilityResourceClass / CapabilityConsumption | Capability |
| EvidenceBasis on a consumption row | Governance (imported by Capability) |
| Service / Technology that provides a capability | Landscape |
| Intended quality target | Capability (requirement) |
| Observed SLO | Landscape / Observability |
ITC-CAP sits between product need and landscape implementation. Capability
ids are durable interfaces (CAP-R5). Landscape §11.4 defers abstract
ability here.
---
# 5. CARING Fit in InfoTechCanon

View file

@ -0,0 +1,150 @@
id: mapping/capability-anchors
title: ITC-CAP concept mappings to anchoring canon models
source: assimilation/it-capability-canon
target: model/capability
mapping_type: related
confidence: mixed
canon_version: "0.6.0"
note: >
Formal per-owner mapping artifacts for ITC-CAP anchors. Adapted from
assimilation/it-capability-canon/mappings.yaml. Quality-dimension mapping
to SLOs is demand-side targets on the requirement (canon 0.3.0+); measurement
remains with LAND/OBS.
concept_mappings:
- source_concept: Implementation
target_concept: Technology / SoftwareEntity / RuntimeEntity
target_owner: model/landscape
mapping_type: imports
confidence: high
- source_concept: Provider
target_concept: Service / ServiceProvider / ServiceInstance
target_owner: model/landscape
mapping_type: related
confidence: high
- source_concept: Resource
target_concept: RuntimeResource
target_owner: model/landscape
mapping_type: broader
confidence: medium
- source_concept: Evidence
target_concept: Evidence
target_owner: model/governance
mapping_type: imports
confidence: high
- source_concept: Evidence (telemetry-derived)
target_concept: TelemetrySignal / Metric / SLO
target_owner: model/observability
mapping_type: related
confidence: high
- source_concept: Requirement
target_concept: DemandSignal / ConsumerNeed
target_owner: model/purpose-demand-extension
mapping_type: narrower
confidence: high
- source_concept: Quality dimension
target_concept: CapabilityRequirement targets / ServiceLevelObjective
target_owner: model/capability
mapping_type: related
confidence: high
rationale: Intended targets live on the requirement; observed SLOs stay with LAND/OBS.
- source_concept: EvidenceBasis
target_concept: EvidenceBasis
target_owner: model/governance
mapping_type: imports
confidence: high
- source_concept: identity.authentication
target_concept: Principal / AuthenticationEvent
target_owner: model/access-control
mapping_type: related
confidence: high
- source_concept: identity.authorization
target_concept: AuthorizationDecision / Permission / Grant
target_owner: model/access-control
mapping_type: related
confidence: high
- source_concept: identity.organization
target_concept: Organization / Team / Tenant
target_owner: model/organization
mapping_type: related
confidence: high
- source_concept: security.policy
target_concept: Policy / Rule / Control
target_owner: model/governance
mapping_type: imports
confidence: high
- source_concept: security.secrets / security.keys / security.vulnerability
target_concept: Secret / Key / Vulnerability / Finding
target_owner: model/security
mapping_type: related
confidence: high
- source_concept: governance.evidence
target_concept: Evidence / Assurance / Control
target_owner: model/governance
mapping_type: related
confidence: high
- source_concept: governance.lifecycle
target_concept: Retention / Classification / DataContract
target_owner: model/data
mapping_type: related
confidence: medium
- source_concept: data.*
target_concept: Dataset / DataStore / Schema / Lineage / Retention
target_owner: model/data
mapping_type: related
confidence: high
- source_concept: integration.traffic
target_concept: Routing / Exposure / Reachability / NetworkPolicy
target_owner: model/network
mapping_type: related
confidence: high
- source_concept: integration.api / integration.messaging / integration.exchange
target_concept: Endpoint / Interface / Flow
target_owner: model/landscape
mapping_type: related
confidence: medium
- source_concept: runtime.deployment
target_concept: Release / Deployment / Artifact
target_owner: model/devsecops
mapping_type: related
confidence: high
- source_concept: runtime.execution / runtime.configuration / runtime.scheduling
target_concept: RuntimeEntity / RuntimeResource / Configuration
target_owner: model/landscape
mapping_type: related
confidence: medium
- source_concept: runtime.workflow
target_concept: Task / Action / Dependency
target_owner: model/task
mapping_type: related
confidence: medium
- source_concept: operations.observability / operations.alerting
target_concept: Telemetry / Alert / Health / SLO
target_owner: model/observability
mapping_type: related
confidence: high
- source_concept: operations.audit
target_concept: Evidence / AuditRecord
target_owner: model/governance
mapping_type: related
confidence: high
- source_concept: operations.recovery / operations.continuity
target_concept: Incident / ServiceLevelObjective
target_owner: model/security
mapping_type: related
confidence: low
note: Continuity has no strong canon owner — OQ-4.
- source_concept: commerce.*
target_concept: (none)
target_owner: model/capability
mapping_type: no_mapping
confidence: high
- source_concept: intelligence.*
target_concept: (none)
target_owner: model/capability
mapping_type: no_mapping
confidence: high
- source_concept: CILM
target_concept: InfoTechCanonLandscapeModel
target_owner: model/landscape
mapping_type: superseded_by
confidence: high

View file

@ -6,7 +6,7 @@ type: domain-model
standard_family: InfoTechCanon
repository_context: info-tech-canon
recommended_path: models/capability/InfoTechCanonCapabilityModel.md
status: proposed
status: draft
version: 0.4.0
source_version: "0.1"
source_body: Information Technology Capability Canon (ITCC)
@ -54,7 +54,7 @@ updated_at: 2026-08-15
# InfoTechCanon Capability Model
**Short Name:** `ITC-CAP`
**Document Status:** Proposed (assimilated, not yet promoted)
**Document Status:** Draft (promoted; contract frozen at canon 0.6.0)
**Version:** 0.4.0
**Document Type:** InfoTechCanon Domain Model
**Machine-readable catalog:** `models/capability/capabilities.yaml`
@ -578,7 +578,10 @@ model. This is accepted at `proposed` status and tracked as OQ-5.
# 10. Status and Promotion
This model enters the canon at status `proposed`. Promotion requires:
This model is **draft** as of canon 0.6.0. The contract is frozen. Further
shape change needs a new minor of ITC-CAP and a CHANGELOG entry.
Promotion from `proposed` required:
1. ~~resolution of assimilation open question **OQ-2**~~ — **resolved in canon
0.2.1**: the Security & Governance navigation domain was split into `security`

View file

@ -13,8 +13,8 @@ canon:
short_name: ITC-CAP
artifact_id: model/capability
version: 0.4.0
status: proposed
canon_version: 0.5.0
status: draft
canon_version: 0.6.0
purpose: Canonical, implementation-independent catalog of the abilities an information system may require
or provide.
normative_document: models/capability/InfoTechCanonCapabilityModel.md

View file

@ -26,6 +26,7 @@ This standard provides a canonical vocabulary for:
- fields,
- schemas,
- data elements,
- attribute value types,
- code lists,
- data stores as references,
- data flows,
@ -761,6 +762,30 @@ A **DataType** specifies the technical or logical type of a field or data elemen
---
## 11.15a AttributeValueType
An **AttributeValueType** is a closed, versioned, application-facing value
type for structured capture. It names the type id, meaning, wire encoding,
and whether a CodeList is required. It does not name a widget and it is not
a competing entity with Attribute or Field.
It is a closed profile of **Representation** for capture and forms.
Constraint still owns required/format/cardinality. CodeList still owns
permitted values. Email, phone, and percentage are not types.
The catalog is `models/data/attribute-value-types.yaml`. Current ids:
`text`, `text-long`, `date`, `time`, `datetime`, `amount`, `one-of`,
`some-of`. Reserved: `boolean`, `integer`, `number`, `uri`, `identifier`.
Legacy alias `textarea` normalizes to `text-long`.
`amount` is structured `{value, currency}`. `one-of` / `some-of` require a
CodeList; domain lists are not new types.
**Provenance.** `demand/AttributeValueTypes.md` (citation-evidence),
ITC-WP-0013.
---
## 11.16 Constraint
A **Constraint** is a rule limiting valid data.

View file

@ -0,0 +1,27 @@
# Alignment note — AttributeValueType catalog for citation-evidence
**Consumer:** citation-evidence Capture UX
**Demand:** `demand/AttributeValueTypes.md`
**Catalog:** `models/data/attribute-value-types.yaml`
**Owner:** ITC-DATA
**Canon version:** 0.6.0
citation-evidence should import these ids rather than keep a private type
enum. Widgets, filters, and evidence links stay in the consumer.
| Consumer need | Canon id | Notes |
|---|---|---|
| short text | `text` | already in use |
| textarea | `text-long` | accept `textarea` on load; write `text-long` |
| date | `date` | `YYYY-MM-DD` |
| time | `time` | requested |
| datetime | `datetime` | ISO-8601 |
| amount | `amount` | `{value, currency}` — accepted default |
| single choice | `one-of` | CodeList required; widget is consumer (`select`) |
| multi choice | `some-of` | CodeList required |
| boolean / integer / number / uri / identifier | reserved | do not implement until needed |
Do not add `email`, `phone`, or `percentage` as types. Those are `text` or
`number` plus a Constraint.
CE-WP-0012 widgets remain consumer work.

View file

@ -0,0 +1,129 @@
# InfoTechCanon Attribute Value Type Catalog
#
# Closed, versioned application-facing value types for structured capture.
# Owned by ITC-DATA. Does not name widgets. Encoding rules live here;
# Constraint, CodeList, and Representation stay the owning concepts.
canon:
id: itc-data-attribute-value-types
name: InfoTechCanon Attribute Value Type Catalog
artifact_id: catalog/attribute-value-types
version: 0.1.0
status: draft
canon_version: 0.6.0
owner: model/data
purpose: Closed catalog of capture value types so consumers share ids and
wire encodings without forking a private type system.
normative_document: models/data/InfoTechCanonDataModel.md
provenance:
demand: demand/AttributeValueTypes.md
consumer: citation-evidence
consumer_draft: citation-evidence/wiki/AttributeValueTypes-proposal.md
workplan: ITC-WP-0013
types:
- id: text
status: current
kind: scalar
wire: string
representation: string
description: Short free text.
- id: text-long
status: current
kind: scalar
wire: string
representation: string
description: Long free text. Canonical id for the legacy alias textarea.
aliases: [textarea]
- id: date
status: current
kind: scalar
wire: string
format: YYYY-MM-DD
representation: date
description: Calendar date.
- id: time
status: current
kind: scalar
wire: string
format: HH:MM or HH:MM:SS
representation: string
description: Clock time without a date.
- id: datetime
status: current
kind: scalar
wire: string
format: ISO-8601 local or offset
representation: timestamp
description: Date and time.
- id: amount
status: current
kind: quantity
wire: object
representation: decimal
requires_codelist: currency
description: Quantity plus currency. Wire form is structured JSON.
encoding:
value: decimal-as-string
currency: ISO-4217 code
example: {value: "1500.00", currency: EUR}
- id: one-of
status: current
kind: choice
wire: string
representation: code
requires_codelist: true
cardinality: 1
description: Exactly one value from a CodeList. Wire value is the option id.
- id: some-of
status: current
kind: choice
wire: array
representation: code
requires_codelist: true
cardinality: 0-n
description: Zero or more values from a CodeList. Wire value is an array of
option ids.
- id: boolean
status: reserved
kind: scalar
wire: boolean
representation: boolean
description: Yes/no. Reserved; not required of consumers yet.
- id: integer
status: reserved
kind: scalar
wire: string
representation: integer
description: Integer as decimal digits. Reserved.
- id: number
status: reserved
kind: scalar
wire: string
representation: decimal
description: Decimal number as string. Reserved.
- id: uri
status: reserved
kind: scalar
wire: string
representation: URI
description: URI. Reserved.
- id: identifier
status: reserved
kind: scalar
wire: string
representation: identifier
description: Opaque identifier. Reserved.
rules:
- id: no-email-type
statement: Do not add email, phone, or percentage as types. Use text or
number plus a Constraint.
- id: no-widget
statement: AttributeValueType does not name a UI widget.
- id: alias-normalize
statement: Legacy alias textarea MUST be accepted on read and normalized
to text-long on write.
- id: amount-structured
statement: amount MUST use {value, currency}. A single string is not
canonical.
- id: choice-needs-codelist
statement: one-of and some-of MUST attach a CodeList. Domain-specific
lists are not new types.

View file

@ -610,7 +610,15 @@ These concepts SHOULD eventually be reviewed against:
- product management,
- and governance models.
The Landscape Model should keep only landscape-relevant references once a dedicated strategy/capability standard exists.
A dedicated capability model now exists: **ITC-CAP**
(`model/capability`). Abstract ability — what a system must be able to do
— is owned there. `BusinessCapability` / `ProductCapability` in this
domain SHOULD resolve to references to ITC-CAP ids. This domain keeps
landscape-relevant strategy concepts (Goal, Driver, Initiative,
RoadmapItem, ValueStream). Capability as ability is no longer owned here.
ITC-CAP names *intended* requirement targets. This model still owns
services, technologies, runtime resources, and *observed* SLOs.
---

View file

@ -0,0 +1,36 @@
$schema: https://json-schema.org/draft/2020-12/schema
$id: https://info-tech-canon.local/schemas/attribute-value-type.schema.yaml
title: InfoTechCanon Attribute Value Type Catalog
type: object
required:
- canon
- types
properties:
canon:
type: object
required: [id, version, owner]
types:
type: array
minItems: 1
items:
type: object
required: [id, status, kind, wire]
properties:
id:
type: string
pattern: "^[a-z][a-z0-9-]*$"
status:
enum: [current, reserved]
kind:
enum: [scalar, quantity, choice]
wire:
enum: [string, object, array, boolean]
representation:
type: string
requires_codelist:
type: [boolean, string]
aliases:
type: array
items:
type: string
additionalProperties: true

View file

@ -0,0 +1,118 @@
$schema: https://json-schema.org/draft/2020-12/schema
$id: https://info-tech-canon.local/schemas/capability-record.schema.yaml
title: InfoTechCanon Capability Requirement and Provision Record
description: >
Shape of a consumer capability case (requirement set + provisions).
Validated against the live catalog by the capability-review surface.
ITC-CAP 0.4.0 / CAP-R8R11.
type: object
required:
- requires
properties:
requires:
type: array
items:
$ref: "#/$defs/requirement"
provisions:
type: array
items:
$ref: "#/$defs/provision"
additionalProperties: true
$defs:
quantity:
type: object
properties:
value: {}
unit:
type: string
requirement:
type: object
required: [capability]
properties:
capability:
type: string
profile:
type: string
minimum_maturity:
type: string
pattern: "^D[0-7]$"
targets:
type: object
additionalProperties:
type: object
constraints:
type: array
items:
type: object
required: [dimension, predicate]
properties:
dimension:
type: string
predicate:
enum: [not_in, in, equals, lte, gte]
of:
type: array
provision:
type: object
required: [provider, capability, maturity]
properties:
provider:
type: string
capability:
type: string
profile:
type: string
environment:
type: string
maturity:
type: string
pattern: "^D[0-7]$"
uses_provisions:
type: array
items:
type: object
required: [capability, provider, relation]
properties:
capability:
type: string
provider:
type: string
relation:
enum: [depends_on, may_use]
consumes:
type: array
items:
type: object
required: [class, quantity, basis]
properties:
class:
type: string
pattern: "^[A-Z]$"
quantity:
$ref: "#/$defs/quantity"
basis:
enum:
- invoiced
- measured
- quoted
- derived
- projected
- estimated
- assumed
- unknown
supply:
enum: [internal, external]
period:
type: string
gap:
type: string
evidence:
type: array
items:
type: object
required: [hook]
properties:
hook:
type: string
basis:
type: string

View file

@ -0,0 +1,114 @@
$schema: https://json-schema.org/draft/2020-12/schema
$id: https://info-tech-canon.local/schemas/capability.schema.yaml
title: InfoTechCanon Capability Catalog (ITC-CAP 0.4.0)
description: >
Contract for capabilities.yaml. Encodes ITC-CAP 0.4.0 — no
typical_resource_classes; resource classes carry native_unit, supply,
and capacity_behaviour. Requirement and provision records are validated
separately by the capability-review surface.
type: object
required:
- canon
- resource_classes
- maturity_levels
- domains
properties:
canon:
type: object
required: [id, version]
properties:
id:
const: itc-cap
version:
type: string
status:
type: string
canon_version:
type: string
resource_classes:
type: array
minItems: 1
items:
type: object
required: [id, name, native_unit, supply, capacity_behaviour]
properties:
id:
type: string
pattern: "^[A-Z]$"
name:
type: string
native_unit:
type: string
supply:
enum: [internal, external]
capacity_behaviour:
enum: [elastic, constrained]
additionalProperties: true
maturity_levels:
type: array
minItems: 8
items:
type: object
required: [id, name]
properties:
id:
type: string
pattern: "^D[0-7]$"
applies_to:
const: capability_provision
relationship_types:
type: array
domains:
type: array
minItems: 1
items:
type: object
required: [id, name, capabilities]
properties:
navigation_only:
type: boolean
capabilities:
type: array
items:
$ref: "#/$defs/capability"
additionalProperties: true
$defs:
capability:
type: object
required: [id, name, purpose]
properties:
id:
type: string
pattern: "^[a-z]+\\.[a-z0-9-]+$"
name:
type: string
purpose:
type: string
anchors:
type: array
items:
type: string
profiles:
type: array
items:
type: string
quality_dimensions:
type: array
items:
type: string
evidence_hooks:
type: array
items:
type: string
depends_on:
type: array
items:
type: string
may_use:
type: array
items:
type: string
typical_resource_classes:
not: {}
description: Forbidden. Consumption attaches to a provision (CAP-R8).
additionalProperties: true

View file

@ -17,3 +17,9 @@ schemas:
path: workplan.schema.yaml
- id: alignment-review
path: alignment-review.schema.yaml
- id: capability
path: capability.schema.yaml
- id: capability-record
path: capability-record.schema.yaml
- id: attribute-value-type
path: attribute-value-type.schema.yaml

View file

@ -1,14 +1,14 @@
{
"details": {
"artifact_count": 66,
"relationship_count": 288
"artifact_count": 68,
"relationship_count": 291
},
"errors": [],
"metrics": {
"coherence_components": 1.0,
"consistency_cycles": 0.0,
"coverage_ratio": 1.0,
"granularity_entropy": 4.459014704982469,
"granularity_entropy": 4.478787416971244,
"redundancy_ratio": 0.0
},
"ok": true,

View file

@ -2,7 +2,7 @@
# By Concept
Concept count: **108**
Concept count: **110**
| Concept | Owner | Source |
| --- | --- | --- |
@ -13,6 +13,7 @@ Concept count: **108**
| Kubernetes RBAC Benchmark Findings And Canon Pressure | `benchmark/caring/kubernetes-rbac/findings` | `artifact_title` |
| Kubernetes RBAC Native Concept Map | `benchmark/caring/kubernetes-rbac/native-concepts` | `artifact_title` |
| InfoTechCanon Capability Catalog | `capability-catalog/itc-cap` | `artifact_title` |
| InfoTechCanon Attribute Value Type Catalog | `catalog/attribute-value-types` | `artifact_title` |
| InfoTechCanon Evidence Basis Catalog | `catalog/evidence-basis` | `artifact_title` |
| Repo Scoping Canon Benefit Analysis | `comparison/repo-scoping/canon-benefit-analysis` | `artifact_title` |
| Repo Scoping Consumer Workplan Brief | `comparison/repo-scoping/consumer-workplan-brief` | `artifact_title` |
@ -33,6 +34,7 @@ Concept count: **108**
| Canon-Side Consumer Purpose Portfolio | `example/consumer-purpose-portfolio` | `artifact_title` |
| InfoTechCanon Core | `kernel/itc-core` | `artifact_title` |
| InfoTechCanon Kernel Map | `kernel/itc-kernel-map` | `artifact_title` |
| ITC-CAP concept mappings to anchoring canon models | `mapping/capability-anchors` | `artifact_title` |
| Purpose Demand Governance Extension Candidates | `mapping/purpose-demand-governance-candidates` | `artifact_title` |
| InfoTechCanon Access Control Model | `model/access-control` | `artifact_title` |
| InfoTechCanon Capability Model | `model/capability` | `artifact_title` |

View file

@ -19,6 +19,10 @@
- `model/capability` via `introduces`
## `catalog/attribute-value-types`
- `model/data` via `introduces`
## `catalog/evidence-basis`
- `model/capability` via `uses`
@ -82,6 +86,10 @@
- `standard/repository-layout` via `conforms_to`
- `standard/tagging` via `conforms_to`
## `mapping/capability-anchors`
- `model/capability` via `introduces`
## `model/access-control`
- `benchmark/caring/kubernetes-rbac` via `stress_tests`
@ -98,6 +106,10 @@
- `small-saas/user/ada-admin` via `uses`
- `standard/caring` via `imports`
## `model/capability`
- `kernel/itc-kernel-map` via `maps`
## `model/data`
- `conformance/railiance-fabric` via `uses`

View file

@ -14,7 +14,7 @@
- ID: `kernel/itc-kernel-map`
- Kind: `kernel`
- Path: `kernel/InfoTechCanonKernelMap.md`
- Relationships: 14
- Relationships: 15
## InfoTechCanon CARING Access Governance Standard

View file

@ -2,71 +2,73 @@
# Import Matrix
| Artifact | `assimilation/it-capability-canon` | `benchmark/caring/kubernetes-rbac` | `benchmark/caring/kubernetes-rbac/access-descriptors` | `benchmark/caring/kubernetes-rbac/caring-mapping` | `benchmark/caring/kubernetes-rbac/findings` | `benchmark/caring/kubernetes-rbac/native-concepts` | `capability-catalog/itc-cap` | `catalog/evidence-basis` | `comparison/repo-scoping/canon-benefit-analysis` | `comparison/repo-scoping/consumer-workplan-brief` | `comparison/repo-scoping/extension-candidates` | `comparison/repo-scoping/frame` | `comparison/repo-scoping/report` | `concept-catalog/purpose-demand` | `conformance/railiance-fabric` | `conformance/railiance-fabric/consumer-workplan-brief` | `conformance/railiance-fabric/entity-edge-capture-criteria` | `conformance/railiance-fabric/mapping-expectations` | `conformance/railiance-fabric/visualization-examples` | `evaluation/user-engine` | `evaluation/user-engine/consumer-workplan-brief` | `evaluation/user-engine/interface-card-expectations` | `evaluation/user-engine/questions` | `evaluation/user-engine/small-saas-alignment` | `example/consumer-purpose-portfolio` | `kernel/itc-core` | `kernel/itc-kernel-map` | `mapping/purpose-demand-governance-candidates` | `model/access-control` | `model/capability` | `model/data` | `model/devsecops` | `model/governance` | `model/information-space` | `model/landscape` | `model/network` | `model/observability` | `model/organization` | `model/purpose-demand-extension` | `model/security` | `model/task` | `pattern/intent-scope-purposes` | `practice/intake-and-assimilation` | `profile/small-saas` | `review-kit/alignment` | `review-kit/alignment/model-selection-guide` | `review-kit/alignment/schema` | `review-kit/alignment/scorecard` | `review-kit/alignment/workflow` | `review-kit/alignment/workplan-template` | `small-saas/control/namespace-per-tenant` | `small-saas/dataset/subscription-ledger` | `small-saas/deployment/production` | `small-saas/evidence/access-review-2026-05` | `small-saas/incident/cross-tenant-access-attempt` | `small-saas/policy/tenant-isolation` | `small-saas/service/billing-portal` | `small-saas/system/billing-system` | `small-saas/task/onboard-tenant` | `small-saas/team/platform` | `small-saas/tenant/acme` | `small-saas/tenant/globex` | `small-saas/user/ada-admin` | `standard/caring` | `standard/repository-layout` | `standard/tagging` |
| --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- |
| `assimilation/it-capability-canon` | | | | | | | | | | | | | | | | | | | | | | | | | | `conforms_to` | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
| `benchmark/caring/kubernetes-rbac` | | | | | | | | | | | | | | | | | | | | | | | | | | | | | `stress_tests` | | | `stress_tests` | `stress_tests` | | | `stress_tests` | `stress_tests` | | | `stress_tests` | | | | | | | | | | | | | | | | | | | | | | | | `conforms_to` | | `uses` |
| `benchmark/caring/kubernetes-rbac/access-descriptors` | | `part_of` | | | | | | | | | | | | | | | | | | | | | | | | | | | `uses` | | | `uses` | | | | | | | | `uses` | | | | | | | | | | | | | | | | | | | | | | | | `uses` | | |
| `benchmark/caring/kubernetes-rbac/caring-mapping` | | `part_of` | | | | | | | | | | | | | | | | | | | | | | | | | | | `maps` | | | | `maps` | | | | | | | `maps` | | | | | | | | | | | | | | | | | | | | | | | | `maps` | | |
| `benchmark/caring/kubernetes-rbac/findings` | | `part_of` | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | `proposes` | | | | | | | `proposes` | | | | | | | | | | | | | | | | | | | | | | | | `proposes` | | |
| `benchmark/caring/kubernetes-rbac/native-concepts` | | `part_of` | | | | | | | | | | | | | | | | | | | | | | | | | | | `maps` | | | | | | `maps` | | | | | | | | | | | | | | | | | | | | | | | | | | | | | `maps` | | |
| `capability-catalog/itc-cap` | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
| `catalog/evidence-basis` | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
| `comparison/repo-scoping/canon-benefit-analysis` | | | | | | | | | | | | | `part_of` | | | | | | | | | | | | | | | | | | | | `maps` | `maps` | | | | | `maps` | | `maps` | | | | | | | | | | | | | | | | | | | | | | | | | `maps` |
| `comparison/repo-scoping/consumer-workplan-brief` | | | | | | | | | | | | | `part_of` | | | | | | | | | | | | | | | | | | | | | | | | | | `uses` | | | | | | | | | | | | | | | | | | | | | | | | | | | |
| `comparison/repo-scoping/extension-candidates` | | | | | | | | | | | | | `part_of` | | | | | | | | | | | | | | | | | | | | `proposes` | `proposes` | | | | | `proposes` | | `proposes` | | | | | | | | | | | | | | | | | | | | | | | | | |
| `comparison/repo-scoping/frame` | | | | | | | | | | | | | `part_of` | | | | | | | | | | | | | | | | | | | | `uses` | | | | | | `uses` | | `uses` | | | | | | | | | | | | | | | | | | | | | | | | | |
| `comparison/repo-scoping/report` | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | `uses` | `uses` | | | | | `compares` | | `uses` | `uses` | | | | | | | | | | | | | | | | | | | | | | | | |
| `concept-catalog/purpose-demand` | | | | | | | | | | | | | | | | | | | | | | | | | | `conforms_to` | | | | | | | `uses` | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
| `conformance/railiance-fabric` | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | `uses` | `uses` | `uses` | | `uses` | `uses` | `uses` | | `uses` | `uses` | `uses` | | | | | | | | | | | | | | | | | | | | | | | | | `uses` |
| `conformance/railiance-fabric/consumer-workplan-brief` | | | | | | | | | | | | | | | `part_of` | | | | | | | | | | | | | | | | | | | | | | | | `uses` | | | | | | | | | | | | | | | | | | | | | | | | | | | |
| `conformance/railiance-fabric/entity-edge-capture-criteria` | | | | | | | | | | | | | | | `part_of` | | | | | | | | | | | | | | | | `uses` | `uses` | `uses` | | `uses` | `uses` | `uses` | | `uses` | `uses` | `uses` | | | | | | | | | | | | | | | | | | | | | | | | | |
| `conformance/railiance-fabric/mapping-expectations` | | | | | | | | | | | | | | | `part_of` | | | | | | | | | | | | | | | | `maps` | `maps` | `maps` | | `maps` | `maps` | `maps` | | `maps` | `maps` | | | | | | | | | | | | | | | | | | | | | | | | | | |
| `conformance/railiance-fabric/visualization-examples` | | | | | | | | | | | | | | | `part_of` | | `illustrates` | `illustrates` | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
| `evaluation/user-engine` | | | | | | | | | | | | | | | | | | | | | | | | | | | | | `uses` | | `uses` | | `uses` | | | | | `uses` | `uses` | `uses` | `uses` | | | `evaluates` | | | | | | | | | | | | | | | | | | | | `uses` | | |
| `evaluation/user-engine/consumer-workplan-brief` | | | | | | | | | | | | | | | | | | | | `part_of` | | | | | | | | | | | | | | | | | | | `uses` | | | | | | | | | | | | | | | | | | | | | | | | | | | |
| `evaluation/user-engine/interface-card-expectations` | | | | | | | | | | | | | | | | | | | | `part_of` | | | | | | | | | | | | | | | | | | | `uses` | | | | | | | | | | | | | | | | | | | | | | | | | `uses` | | |
| `evaluation/user-engine/questions` | | | | | | | | | | | | | | | | | | | | `part_of` | | | | | | | | | `uses` | | `uses` | | `uses` | | | | | `uses` | `uses` | `uses` | `uses` | | | | | | | | | | | | | | | | | | | | | | | | | |
| `evaluation/user-engine/small-saas-alignment` | | | | | | | | | | | | | | | | | | | | `part_of` | | | | | | | | | `uses` | | | | `uses` | | | | | `uses` | | | | | | `evaluates` | | | | | | | | | | | | | | | | | | | | | | |
| `example/consumer-purpose-portfolio` | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | `illustrates` | | | `illustrates` | | `uses` | | | | | | | | | | | | | | | | | | | | | | |
| `kernel/itc-core` | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
| `kernel/itc-kernel-map` | | | | | | | | | | | | | | | | | | | | | | | | | | `maps` | | | `maps` | | `maps` | `maps` | `maps` | `maps` | `maps` | `maps` | `maps` | `maps` | | `maps` | `maps` | | | | | | | | | | | | | | | | | | | | | | | `maps` | | `maps` |
| `mapping/purpose-demand-governance-candidates` | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | `maps` | | | | | | `maps` | | `uses` | | | | | | | | | | | | | | | | | | | | | | | | | |
| `model/access-control` | | | | | | | | | | | | | | | | | | | | | | | | | | `conforms_to` | | | | | | | `uses` | | | | | `uses` | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
| `model/capability` | `derived_from` | | | | | | `introduces` | `uses` | | | | | | | | | | | | | | | | | | `conforms_to` | | | | | | | `uses` | | `uses` | | `uses` | | `uses` | | | | | | | | | | | | | | | | | | | | | | | | | | | |
| `model/data` | | | | | | | | | | | | | | | | | | | | | | | | | | `conforms_to` | | | | | | | `uses` | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
| `model/devsecops` | | | | | | | | | | | | | | | | | | | | | | | | | | `conforms_to` | | | | | | | | | | | | | | `uses` | | | | | | | | | | | | | | | | | | | | | | | | | | |
| `model/governance` | | | | | | | | `introduces` | | | | | | | | | | | | | | | | | | `conforms_to` | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
| `model/information-space` | | | | | | | | | | | | | | | | | | | | | | | | | | `conforms_to` | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
| `model/landscape` | | | | | | | | | | | | | | | | | | | | | | | | | | `conforms_to` | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
| `model/network` | | | | | | | | | | | | | | | | | | | | | | | | | | `conforms_to` | | | | | | | | | | | | | | `uses` | | | | | | | | | | | | | | | | | | | | | | | | | | |
| `model/observability` | | | | | | | | | | | | | | | | | | | | | | | | | | `conforms_to` | | | | | | | | | | | | | | | `uses` | | | | | | | | | | | | | | | | | | | | | | | | | |
| `model/organization` | | | | | | | | | | | | | | | | | | | | | | | | | | `conforms_to` | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
| `model/purpose-demand-extension` | | | | | | | | | | | | | | `introduces` | | | | | | | | | | | | `conforms_to` | | | | | | | `extends` | `uses` | | | | | | | `uses` | | | | | | | | | | | | | | | | | | | | | | | | | |
| `model/security` | | | | | | | | | | | | | | | | | | | | | | | | | | `conforms_to` | | | `uses` | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
| `model/task` | | | | | | | | | | | | | | | | | | | | | | | | | | `conforms_to` | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
| `pattern/intent-scope-purposes` | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | `uses` | | | | | | `implements` | | `uses` | | | | | | | | | | | | | | | | | | | | | | | | | |
| `practice/intake-and-assimilation` | | | | | | | | | | | | | | | | | | | | | | | | | | `conforms_to` | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
| `profile/small-saas` | | | | | | | | | | | | | | | | | | | | | | | | | | `conforms_to` | | | `requires` | | `requires` | `requires` | `requires` | | `requires` | `requires` | `requires` | `requires` | | `requires` | `requires` | | | | | | | | | | | | | | | | | | | | | | | `requires` | | `requires` |
| `review-kit/alignment` | | `uses` | | | | | | | | | | | | | | | | | | | | | | | | `conforms_to` | | | | | | | `uses` | | | | | | `uses` | | `uses` | | | | | | | | | | | | | | | | | | | | | | | `uses` | | |
| `review-kit/alignment/model-selection-guide` | | `uses` | | | | | | | | | | | | | | | | | | | | | | | | | | | `uses` | | `uses` | `uses` | `uses` | | `uses` | `uses` | `uses` | `uses` | `uses` | `uses` | `uses` | | | `uses` | `part_of` | | | | | | | | | | | | | | | | | | | `uses` | | `uses` |
| `review-kit/alignment/schema` | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | `uses` | | | | | | | | `uses` | | | | `part_of` | | | | | | | | | | | | | | | | | | | | | |
| `review-kit/alignment/scorecard` | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | `uses` | | | | | | | | `uses` | | | | `part_of` | | | | | | | | | | | | | | | | | | | | | |
| `review-kit/alignment/workflow` | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | `uses` | | | | | | `uses` | | `uses` | | | | `part_of` | | | | | | | | | | | | | | | | | | | | | |
| `review-kit/alignment/workplan-template` | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | `uses` | | `uses` | | | | `part_of` | | | | | | | | | | | | | | | | | | | | | |
| `small-saas/control/namespace-per-tenant` | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | `uses` | | | | `instantiates` | | | | | | | | | | `evidenced_by` | | | | | | | | | | `uses` | | |
| `small-saas/dataset/subscription-ledger` | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | `uses` | | | | | | | | | | | | | `instantiates` | | | | | | | | | | | | `governed_by` | `owned_by` | | | | `partitioned_for` | `partitioned_for` | | | | |
| `small-saas/deployment/production` | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | `uses` | | | | `uses` | | | | | | | | `instantiates` | | | | | | | `implements` | | | | | | `deploys` | | | | `separates` | `separates` | | | | |
| `small-saas/evidence/access-review-2026-05` | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | `uses` | | | | | | | `instantiates` | | | | | | | | | | | | | | | | | | | | | | |
| `small-saas/incident/cross-tenant-access-attempt` | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | `uses` | | | | `instantiates` | | | | | | | `constrained_by` | | | `evidenced_by` | | | | | | | | | | | | |
| `small-saas/policy/tenant-isolation` | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | `uses` | | | | | | | | | | | `instantiates` | | | | | | | `requires` | | | `evidenced_by` | | | | | | | | | | | | |
| `small-saas/service/billing-portal` | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | `uses` | | | | | | | | | `instantiates` | | | | | | | | | | | | | | `part_of` | | `owned_by` | | | | | | |
| `small-saas/system/billing-system` | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | `uses` | | | | | | | | | `instantiates` | | | | | | | | | | | | | | | | | `serves` | `serves` | | | | |
| `small-saas/task/onboard-tenant` | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | `uses` | | | `instantiates` | | | | | | | | | | | | `governed_by` | | | | `owned_by` | `changes` | | | | | |
| `small-saas/team/platform` | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | `uses` | | | | | | `instantiates` | | | | | | | | | | | | | | | | | | | | | | |
| `small-saas/tenant/acme` | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | `uses` | | | | | | `instantiates` | | | | | | | `isolated_by` | | | | | | | | | | | | `represented_by` | | | |
| `small-saas/tenant/globex` | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | `uses` | | | | | | `instantiates` | | | | | | | `isolated_by` | | | | | | | | | | | | | | | |
| `small-saas/user/ada-admin` | | | | | | | | | | | | | | | | | | | | | | | | | | | | | `uses` | | | | | | | | | `uses` | | | | | | `instantiates` | | | | | | | | | | `access_evidenced_by` | | `has_access_under` | | | | `member_of` | | | | | | |
| `standard/caring` | | | | | | | | | | | | | | | | | | | | | | | | | | `conforms_to` | | | `imports` | | `imports` | `imports` | `imports` | | | `imports` | `imports` | `imports` | | `imports` | `imports` | | | | | | | | | | | | | | | | | | | | | | | | | `imports` |
| `standard/repository-layout` | | | | | | | | | | | | | | | | | | | | | | | | | | `conforms_to` | | | | | | | `imports` | `imports` | | | | | | | `imports` | | | | | | | | | | | | | | | | | | | | | | | | | |
| `standard/tagging` | | | | | | | | | | | | | | | | | | | | | | | | | | `conforms_to` | | | | | | | | | | | | | | | `imports` | | | | | | | | | | | | | | | | | | | | | | | | | |
| Artifact | `assimilation/it-capability-canon` | `benchmark/caring/kubernetes-rbac` | `benchmark/caring/kubernetes-rbac/access-descriptors` | `benchmark/caring/kubernetes-rbac/caring-mapping` | `benchmark/caring/kubernetes-rbac/findings` | `benchmark/caring/kubernetes-rbac/native-concepts` | `capability-catalog/itc-cap` | `catalog/attribute-value-types` | `catalog/evidence-basis` | `comparison/repo-scoping/canon-benefit-analysis` | `comparison/repo-scoping/consumer-workplan-brief` | `comparison/repo-scoping/extension-candidates` | `comparison/repo-scoping/frame` | `comparison/repo-scoping/report` | `concept-catalog/purpose-demand` | `conformance/railiance-fabric` | `conformance/railiance-fabric/consumer-workplan-brief` | `conformance/railiance-fabric/entity-edge-capture-criteria` | `conformance/railiance-fabric/mapping-expectations` | `conformance/railiance-fabric/visualization-examples` | `evaluation/user-engine` | `evaluation/user-engine/consumer-workplan-brief` | `evaluation/user-engine/interface-card-expectations` | `evaluation/user-engine/questions` | `evaluation/user-engine/small-saas-alignment` | `example/consumer-purpose-portfolio` | `kernel/itc-core` | `kernel/itc-kernel-map` | `mapping/capability-anchors` | `mapping/purpose-demand-governance-candidates` | `model/access-control` | `model/capability` | `model/data` | `model/devsecops` | `model/governance` | `model/information-space` | `model/landscape` | `model/network` | `model/observability` | `model/organization` | `model/purpose-demand-extension` | `model/security` | `model/task` | `pattern/intent-scope-purposes` | `practice/intake-and-assimilation` | `profile/small-saas` | `review-kit/alignment` | `review-kit/alignment/model-selection-guide` | `review-kit/alignment/schema` | `review-kit/alignment/scorecard` | `review-kit/alignment/workflow` | `review-kit/alignment/workplan-template` | `small-saas/control/namespace-per-tenant` | `small-saas/dataset/subscription-ledger` | `small-saas/deployment/production` | `small-saas/evidence/access-review-2026-05` | `small-saas/incident/cross-tenant-access-attempt` | `small-saas/policy/tenant-isolation` | `small-saas/service/billing-portal` | `small-saas/system/billing-system` | `small-saas/task/onboard-tenant` | `small-saas/team/platform` | `small-saas/tenant/acme` | `small-saas/tenant/globex` | `small-saas/user/ada-admin` | `standard/caring` | `standard/repository-layout` | `standard/tagging` |
| --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- |
| `assimilation/it-capability-canon` | | | | | | | | | | | | | | | | | | | | | | | | | | | `conforms_to` | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
| `benchmark/caring/kubernetes-rbac` | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | `stress_tests` | | | `stress_tests` | `stress_tests` | | | `stress_tests` | `stress_tests` | | | `stress_tests` | | | | | | | | | | | | | | | | | | | | | | | | `conforms_to` | | `uses` |
| `benchmark/caring/kubernetes-rbac/access-descriptors` | | `part_of` | | | | | | | | | | | | | | | | | | | | | | | | | | | | | `uses` | | | `uses` | | | | | | | | `uses` | | | | | | | | | | | | | | | | | | | | | | | | `uses` | | |
| `benchmark/caring/kubernetes-rbac/caring-mapping` | | `part_of` | | | | | | | | | | | | | | | | | | | | | | | | | | | | | `maps` | | | | `maps` | | | | | | | `maps` | | | | | | | | | | | | | | | | | | | | | | | | `maps` | | |
| `benchmark/caring/kubernetes-rbac/findings` | | `part_of` | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | `proposes` | | | | | | | `proposes` | | | | | | | | | | | | | | | | | | | | | | | | `proposes` | | |
| `benchmark/caring/kubernetes-rbac/native-concepts` | | `part_of` | | | | | | | | | | | | | | | | | | | | | | | | | | | | | `maps` | | | | | | `maps` | | | | | | | | | | | | | | | | | | | | | | | | | | | | | `maps` | | |
| `capability-catalog/itc-cap` | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
| `catalog/attribute-value-types` | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
| `catalog/evidence-basis` | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
| `comparison/repo-scoping/canon-benefit-analysis` | | | | | | | | | | | | | | `part_of` | | | | | | | | | | | | | | | | | | | | | `maps` | `maps` | | | | | `maps` | | `maps` | | | | | | | | | | | | | | | | | | | | | | | | | `maps` |
| `comparison/repo-scoping/consumer-workplan-brief` | | | | | | | | | | | | | | `part_of` | | | | | | | | | | | | | | | | | | | | | | | | | | | `uses` | | | | | | | | | | | | | | | | | | | | | | | | | | | |
| `comparison/repo-scoping/extension-candidates` | | | | | | | | | | | | | | `part_of` | | | | | | | | | | | | | | | | | | | | | `proposes` | `proposes` | | | | | `proposes` | | `proposes` | | | | | | | | | | | | | | | | | | | | | | | | | |
| `comparison/repo-scoping/frame` | | | | | | | | | | | | | | `part_of` | | | | | | | | | | | | | | | | | | | | | `uses` | | | | | | `uses` | | `uses` | | | | | | | | | | | | | | | | | | | | | | | | | |
| `comparison/repo-scoping/report` | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | `uses` | `uses` | | | | | `compares` | | `uses` | `uses` | | | | | | | | | | | | | | | | | | | | | | | | |
| `concept-catalog/purpose-demand` | | | | | | | | | | | | | | | | | | | | | | | | | | | `conforms_to` | | | | | | | | `uses` | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
| `conformance/railiance-fabric` | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | `uses` | `uses` | `uses` | | `uses` | `uses` | `uses` | | `uses` | `uses` | `uses` | | | | | | | | | | | | | | | | | | | | | | | | | `uses` |
| `conformance/railiance-fabric/consumer-workplan-brief` | | | | | | | | | | | | | | | | `part_of` | | | | | | | | | | | | | | | | | | | | | | | | | `uses` | | | | | | | | | | | | | | | | | | | | | | | | | | | |
| `conformance/railiance-fabric/entity-edge-capture-criteria` | | | | | | | | | | | | | | | | `part_of` | | | | | | | | | | | | | | | | | `uses` | `uses` | `uses` | | `uses` | `uses` | `uses` | | `uses` | `uses` | `uses` | | | | | | | | | | | | | | | | | | | | | | | | | |
| `conformance/railiance-fabric/mapping-expectations` | | | | | | | | | | | | | | | | `part_of` | | | | | | | | | | | | | | | | | `maps` | `maps` | `maps` | | `maps` | `maps` | `maps` | | `maps` | `maps` | | | | | | | | | | | | | | | | | | | | | | | | | | |
| `conformance/railiance-fabric/visualization-examples` | | | | | | | | | | | | | | | | `part_of` | | `illustrates` | `illustrates` | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
| `evaluation/user-engine` | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | `uses` | | `uses` | | `uses` | | | | | `uses` | `uses` | `uses` | `uses` | | | `evaluates` | | | | | | | | | | | | | | | | | | | | `uses` | | |
| `evaluation/user-engine/consumer-workplan-brief` | | | | | | | | | | | | | | | | | | | | | `part_of` | | | | | | | | | | | | | | | | | | | | `uses` | | | | | | | | | | | | | | | | | | | | | | | | | | | |
| `evaluation/user-engine/interface-card-expectations` | | | | | | | | | | | | | | | | | | | | | `part_of` | | | | | | | | | | | | | | | | | | | | `uses` | | | | | | | | | | | | | | | | | | | | | | | | | `uses` | | |
| `evaluation/user-engine/questions` | | | | | | | | | | | | | | | | | | | | | `part_of` | | | | | | | | | | `uses` | | `uses` | | `uses` | | | | | `uses` | `uses` | `uses` | `uses` | | | | | | | | | | | | | | | | | | | | | | | | | |
| `evaluation/user-engine/small-saas-alignment` | | | | | | | | | | | | | | | | | | | | | `part_of` | | | | | | | | | | `uses` | | | | `uses` | | | | | `uses` | | | | | | `evaluates` | | | | | | | | | | | | | | | | | | | | | | |
| `example/consumer-purpose-portfolio` | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | `illustrates` | | | `illustrates` | | `uses` | | | | | | | | | | | | | | | | | | | | | | |
| `kernel/itc-core` | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
| `kernel/itc-kernel-map` | | | | | | | | | | | | | | | | | | | | | | | | | | | `maps` | | | | `maps` | `maps` | `maps` | `maps` | `maps` | `maps` | `maps` | `maps` | `maps` | `maps` | | `maps` | `maps` | | | | | | | | | | | | | | | | | | | | | | | `maps` | | `maps` |
| `mapping/capability-anchors` | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
| `mapping/purpose-demand-governance-candidates` | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | `maps` | | | | | | `maps` | | `uses` | | | | | | | | | | | | | | | | | | | | | | | | | |
| `model/access-control` | | | | | | | | | | | | | | | | | | | | | | | | | | | `conforms_to` | | | | | | | | `uses` | | | | | `uses` | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
| `model/capability` | `derived_from` | | | | | | `introduces` | | `uses` | | | | | | | | | | | | | | | | | | `conforms_to` | | `introduces` | | | | | | `uses` | | `uses` | | `uses` | | `uses` | | | | | | | | | | | | | | | | | | | | | | | | | | | |
| `model/data` | | | | | | | | `introduces` | | | | | | | | | | | | | | | | | | | `conforms_to` | | | | | | | | `uses` | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
| `model/devsecops` | | | | | | | | | | | | | | | | | | | | | | | | | | | `conforms_to` | | | | | | | | | | | | | | | `uses` | | | | | | | | | | | | | | | | | | | | | | | | | | |
| `model/governance` | | | | | | | | | `introduces` | | | | | | | | | | | | | | | | | | `conforms_to` | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
| `model/information-space` | | | | | | | | | | | | | | | | | | | | | | | | | | | `conforms_to` | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
| `model/landscape` | | | | | | | | | | | | | | | | | | | | | | | | | | | `conforms_to` | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
| `model/network` | | | | | | | | | | | | | | | | | | | | | | | | | | | `conforms_to` | | | | | | | | | | | | | | | `uses` | | | | | | | | | | | | | | | | | | | | | | | | | | |
| `model/observability` | | | | | | | | | | | | | | | | | | | | | | | | | | | `conforms_to` | | | | | | | | | | | | | | | | `uses` | | | | | | | | | | | | | | | | | | | | | | | | | |
| `model/organization` | | | | | | | | | | | | | | | | | | | | | | | | | | | `conforms_to` | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
| `model/purpose-demand-extension` | | | | | | | | | | | | | | | `introduces` | | | | | | | | | | | | `conforms_to` | | | | | | | | `extends` | `uses` | | | | | | | `uses` | | | | | | | | | | | | | | | | | | | | | | | | | |
| `model/security` | | | | | | | | | | | | | | | | | | | | | | | | | | | `conforms_to` | | | | `uses` | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
| `model/task` | | | | | | | | | | | | | | | | | | | | | | | | | | | `conforms_to` | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
| `pattern/intent-scope-purposes` | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | `uses` | | | | | | `implements` | | `uses` | | | | | | | | | | | | | | | | | | | | | | | | | |
| `practice/intake-and-assimilation` | | | | | | | | | | | | | | | | | | | | | | | | | | | `conforms_to` | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
| `profile/small-saas` | | | | | | | | | | | | | | | | | | | | | | | | | | | `conforms_to` | | | | `requires` | | `requires` | `requires` | `requires` | | `requires` | `requires` | `requires` | `requires` | | `requires` | `requires` | | | | | | | | | | | | | | | | | | | | | | | `requires` | | `requires` |
| `review-kit/alignment` | | `uses` | | | | | | | | | | | | | | | | | | | | | | | | | `conforms_to` | | | | | | | | `uses` | | | | | | `uses` | | `uses` | | | | | | | | | | | | | | | | | | | | | | | `uses` | | |
| `review-kit/alignment/model-selection-guide` | | `uses` | | | | | | | | | | | | | | | | | | | | | | | | | | | | | `uses` | | `uses` | `uses` | `uses` | | `uses` | `uses` | `uses` | `uses` | `uses` | `uses` | `uses` | | | `uses` | `part_of` | | | | | | | | | | | | | | | | | | | `uses` | | `uses` |
| `review-kit/alignment/schema` | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | `uses` | | | | | | | | `uses` | | | | `part_of` | | | | | | | | | | | | | | | | | | | | | |
| `review-kit/alignment/scorecard` | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | `uses` | | | | | | | | `uses` | | | | `part_of` | | | | | | | | | | | | | | | | | | | | | |
| `review-kit/alignment/workflow` | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | `uses` | | | | | | `uses` | | `uses` | | | | `part_of` | | | | | | | | | | | | | | | | | | | | | |
| `review-kit/alignment/workplan-template` | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | `uses` | | `uses` | | | | `part_of` | | | | | | | | | | | | | | | | | | | | | |
| `small-saas/control/namespace-per-tenant` | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | `uses` | | | | `instantiates` | | | | | | | | | | `evidenced_by` | | | | | | | | | | `uses` | | |
| `small-saas/dataset/subscription-ledger` | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | `uses` | | | | | | | | | | | | | `instantiates` | | | | | | | | | | | | `governed_by` | `owned_by` | | | | `partitioned_for` | `partitioned_for` | | | | |
| `small-saas/deployment/production` | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | `uses` | | | | `uses` | | | | | | | | `instantiates` | | | | | | | `implements` | | | | | | `deploys` | | | | `separates` | `separates` | | | | |
| `small-saas/evidence/access-review-2026-05` | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | `uses` | | | | | | | `instantiates` | | | | | | | | | | | | | | | | | | | | | | |
| `small-saas/incident/cross-tenant-access-attempt` | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | `uses` | | | | `instantiates` | | | | | | | `constrained_by` | | | `evidenced_by` | | | | | | | | | | | | |
| `small-saas/policy/tenant-isolation` | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | `uses` | | | | | | | | | | | `instantiates` | | | | | | | `requires` | | | `evidenced_by` | | | | | | | | | | | | |
| `small-saas/service/billing-portal` | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | `uses` | | | | | | | | | `instantiates` | | | | | | | | | | | | | | `part_of` | | `owned_by` | | | | | | |
| `small-saas/system/billing-system` | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | `uses` | | | | | | | | | `instantiates` | | | | | | | | | | | | | | | | | `serves` | `serves` | | | | |
| `small-saas/task/onboard-tenant` | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | `uses` | | | `instantiates` | | | | | | | | | | | | `governed_by` | | | | `owned_by` | `changes` | | | | | |
| `small-saas/team/platform` | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | `uses` | | | | | | `instantiates` | | | | | | | | | | | | | | | | | | | | | | |
| `small-saas/tenant/acme` | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | `uses` | | | | | | `instantiates` | | | | | | | `isolated_by` | | | | | | | | | | | | `represented_by` | | | |
| `small-saas/tenant/globex` | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | `uses` | | | | | | `instantiates` | | | | | | | `isolated_by` | | | | | | | | | | | | | | | |
| `small-saas/user/ada-admin` | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | `uses` | | | | | | | | | `uses` | | | | | | `instantiates` | | | | | | | | | | `access_evidenced_by` | | `has_access_under` | | | | `member_of` | | | | | | |
| `standard/caring` | | | | | | | | | | | | | | | | | | | | | | | | | | | `conforms_to` | | | | `imports` | | `imports` | `imports` | `imports` | | | `imports` | `imports` | `imports` | | `imports` | `imports` | | | | | | | | | | | | | | | | | | | | | | | | | `imports` |
| `standard/repository-layout` | | | | | | | | | | | | | | | | | | | | | | | | | | | `conforms_to` | | | | | | | | `imports` | `imports` | | | | | | | `imports` | | | | | | | | | | | | | | | | | | | | | | | | | |
| `standard/tagging` | | | | | | | | | | | | | | | | | | | | | | | | | | | `conforms_to` | | | | | | | | | | | | | | | | `imports` | | | | | | | | | | | | | | | | | | | | | | | | | |

View file

@ -3,7 +3,7 @@
# Kernel Overview
- Infospace: `canon`
- Artifacts: 66
- Artifacts: 68
## Artifact Kinds
@ -21,7 +21,7 @@
- `caring-mapping`: 1
- `comparison-frame`: 1
- `comparison-report`: 1
- `concept-catalog`: 2
- `concept-catalog`: 3
- `conformance-pack`: 1
- `consumer-workplan-brief`: 3
- `consumer-workplan-template`: 1
@ -31,7 +31,7 @@
- `extension-candidate-set`: 1
- `interface-card-expectation`: 1
- `kernel`: 2
- `mapping`: 1
- `mapping`: 2
- `mapping-expectation`: 1
- `model`: 12
- `model-extension`: 1
@ -63,9 +63,9 @@
- `implements`: 2
- `imports`: 14
- `instantiates`: 13
- `introduces`: 3
- `introduces`: 5
- `isolated_by`: 2
- `maps`: 36
- `maps`: 37
- `member_of`: 1
- `owned_by`: 3
- `part_of`: 22