Implement canon conformance and maintenance optimizations
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
CI Smoke / container-smoke (push) Successful in 3s

Assistant: codex
Assistant-Model: gpt-6-astra
Assistant-Session: 01a06e82-3e08-7042-a79d-438ac6eed8db
This commit is contained in:
tegwick 2026-09-05 00:50:09 +02:00
parent a2e7f22d8d
commit b081d39da1
64 changed files with 4491 additions and 373 deletions

View file

@ -0,0 +1,30 @@
---
id: agent-brief/example-emission-cadence-qonto-assistant
artifact_id: example/emission-cadence/qonto-assistant
source_path: standards/emission-cadence/examples/qonto-assistant.yaml
source_kind: example
generated: true
---
<!-- GENERATED by info_tech_canon; do not edit by hand. -->
# Agent Brief: Qonto Assistant Emission Cadence Worked Example
- Artifact ID: `example/emission-cadence/qonto-assistant`
- Kind: `example`
- Canonical path: `standards/emission-cadence/examples/qonto-assistant.yaml`
- Full source: `standards/emission-cadence/examples/qonto-assistant.yaml`
- Summary: Canon-side example artifact: Qonto Assistant Emission Cadence Worked Example.
## Retrieval Hints
Imports and anchors:
- `standard/emission-cadence`
## Owned Concepts
- `Qonto Assistant Emission Cadence Worked Example`
## Related Distinctions
No common distinction is anchored directly on this artifact.

View file

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

View file

@ -0,0 +1,37 @@
---
id: agent-brief/standard-emission-cadence
artifact_id: standard/emission-cadence
source_path: standards/emission-cadence/InfoTechCanonEmissionCadenceStandard.md
source_kind: standard
generated: true
---
<!-- GENERATED by info_tech_canon; do not edit by hand. -->
# Agent Brief: InfoTechCanon Emission Cadence Standard
- Artifact ID: `standard/emission-cadence`
- Kind: `standard`
- Canonical path: `standards/emission-cadence/InfoTechCanonEmissionCadenceStandard.md`
- Full source: `standards/emission-cadence/InfoTechCanonEmissionCadenceStandard.md`
- Summary: Cross-cutting canon standard: InfoTechCanon Emission Cadence Standard.
## Retrieval Hints
Imports and anchors:
- `kernel/itc-core`
- `model/governance`
- `model/observability`
## Owned Concepts
- `EmissionCadenceDeclaration`
- `EmissionCadenceForm`
- `ExpectedRateCadence`
- `HeartbeatCadence`
- `InfoTechCanon Emission Cadence Standard`
- `ReconciliationCadence`
## 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: 71
- Retrieval index items: 71
- Artifact count: 76
- Retrieval index items: 76
- 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

@ -59,8 +59,29 @@
}
],
"infospace": "canon",
"item_count": 71,
"item_count": 76,
"items": [
{
"canonical_path": "assimilation/emission-cadence/ASSIMILATION.md",
"id": "assimilation/emission-cadence",
"imports": [
"kernel/itc-core"
],
"kind": "assimilation",
"owned_concepts": [
"Assimilation \u2014 EmissionCadenceDeclaration handover"
],
"relationships": [
{
"target": "kernel/itc-core",
"type": "conforms_to"
}
],
"source_path": "infospace/assimilation/emission-cadence/source/EmissionCadenceDeclaration.md",
"summary": "Canon artifact: Assimilation \u2014 EmissionCadenceDeclaration handover.",
"title": "Assimilation \u2014 EmissionCadenceDeclaration handover",
"warnings": []
},
{
"canonical_path": "assimilation/it-capability-canon/ASSIMILATION.md",
"id": "assimilation/it-capability-canon",
@ -983,6 +1004,27 @@
"title": "Canon-Side Consumer Purpose Portfolio",
"warnings": []
},
{
"canonical_path": "standards/emission-cadence/examples/qonto-assistant.yaml",
"id": "example/emission-cadence/qonto-assistant",
"imports": [
"standard/emission-cadence"
],
"kind": "example",
"owned_concepts": [
"Qonto Assistant Emission Cadence Worked Example"
],
"relationships": [
{
"target": "standard/emission-cadence",
"type": "conforms_to"
}
],
"source_path": "infospace/assimilation/emission-cadence/source/EmissionCadenceDeclaration.md",
"summary": "Canon-side example artifact: Qonto Assistant Emission Cadence Worked Example.",
"title": "Qonto Assistant Emission Cadence Worked Example",
"warnings": []
},
{
"canonical_path": "kernel/InfoTechCanonCore.md",
"id": "kernel/itc-core",
@ -1086,6 +1128,33 @@
"title": "ITC-CAP concept mappings to anchoring canon models",
"warnings": []
},
{
"canonical_path": "assimilation/emission-cadence/mappings.yaml",
"id": "mapping/emission-cadence-handover",
"imports": [],
"kind": "mapping",
"owned_concepts": [
"Emission cadence handover mappings"
],
"relationships": [
{
"target": "standard/emission-cadence",
"type": "maps"
},
{
"target": "model/observability",
"type": "maps"
},
{
"target": "model/governance",
"type": "maps"
}
],
"source_path": "infospace/assimilation/emission-cadence/source/EmissionCadenceDeclaration.md",
"summary": "Mapping artifact connecting canon surfaces: Emission cadence handover mappings.",
"title": "Emission cadence handover mappings",
"warnings": []
},
{
"canonical_path": "mappings/purpose-demand-governance-candidates.yaml",
"id": "mapping/purpose-demand-governance-candidates",
@ -2014,6 +2083,35 @@
"title": "PracticePattern Scheme",
"warnings": []
},
{
"canonical_path": "profiles/small-saas/artifacts/capability-requirements.yaml",
"id": "small-saas/capability-requirements/production",
"imports": [
"model/capability"
],
"kind": "profile-artifact",
"owned_concepts": [
"Small SaaS Production Capability Requirements"
],
"relationships": [
{
"target": "profile/small-saas",
"type": "instantiates"
},
{
"target": "model/capability",
"type": "uses"
},
{
"target": "small-saas/service/billing-portal",
"type": "applies_to"
}
],
"source_path": "profiles/small-saas/artifacts/capability-requirements.yaml",
"summary": "Example artifact for the small-saas profile: Small SaaS Production Capability Requirements.",
"title": "Small SaaS Production Capability Requirements",
"warnings": []
},
{
"canonical_path": "profiles/small-saas/artifacts/control.namespace-per-tenant.yaml",
"id": "small-saas/control/namespace-per-tenant",
@ -2545,6 +2643,50 @@
"title": "InfoTechCanon CARING Access Governance Standard",
"warnings": []
},
{
"canonical_path": "standards/emission-cadence/InfoTechCanonEmissionCadenceStandard.md",
"id": "standard/emission-cadence",
"imports": [
"kernel/itc-core",
"model/governance",
"model/observability"
],
"kind": "standard",
"owned_concepts": [
"EmissionCadenceDeclaration",
"EmissionCadenceForm",
"ExpectedRateCadence",
"HeartbeatCadence",
"InfoTechCanon Emission Cadence Standard",
"ReconciliationCadence"
],
"relationships": [
{
"target": "kernel/itc-core",
"type": "conforms_to"
},
{
"target": "model/observability",
"type": "imports"
},
{
"target": "model/governance",
"type": "imports"
},
{
"target": "model/security",
"type": "related_to"
},
{
"target": "assimilation/emission-cadence",
"type": "derived_from"
}
],
"source_path": "infospace/assimilation/emission-cadence/source/EmissionCadenceDeclaration.md",
"summary": "Cross-cutting canon standard: InfoTechCanon Emission Cadence Standard.",
"title": "InfoTechCanon Emission Cadence Standard",
"warnings": []
},
{
"canonical_path": "standards/repository-layout/InfoTechCanonRepositoryLayoutStandard.md",
"id": "standard/repository-layout",

View file

@ -4,7 +4,7 @@
Schema: `info-tech-canon.retrieval-index.v1`
Infospace: `canon`
Items: **71**
Items: **76**
## Common Distinctions
@ -17,6 +17,16 @@ Items: **71**
## Items
### Assimilation — EmissionCadenceDeclaration handover
- ID: `assimilation/emission-cadence`
- Kind: `assimilation`
- Canonical path: `assimilation/emission-cadence/ASSIMILATION.md`
- Source path: `infospace/assimilation/emission-cadence/source/EmissionCadenceDeclaration.md`
- Summary: Canon artifact: Assimilation — EmissionCadenceDeclaration handover.
- Imports and anchors: `kernel/itc-core`
- Owned concepts: `Assimilation — EmissionCadenceDeclaration handover`
### Assimilation — IT Capability Canon (ITCC) v0.1
- ID: `assimilation/it-capability-canon`
@ -277,6 +287,16 @@ Items: **71**
- Imports and anchors: `profile/small-saas`
- Owned concepts: `Canon-Side Consumer Purpose Portfolio`
### Qonto Assistant Emission Cadence Worked Example
- ID: `example/emission-cadence/qonto-assistant`
- Kind: `example`
- Canonical path: `standards/emission-cadence/examples/qonto-assistant.yaml`
- Source path: `infospace/assimilation/emission-cadence/source/EmissionCadenceDeclaration.md`
- Summary: Canon-side example artifact: Qonto Assistant Emission Cadence Worked Example.
- Imports and anchors: `standard/emission-cadence`
- Owned concepts: `Qonto Assistant Emission Cadence Worked Example`
### InfoTechCanon Core
- ID: `kernel/itc-core`
@ -307,6 +327,16 @@ Items: **71**
- Imports and anchors: none
- Owned concepts: `ITC-CAP concept mappings to anchoring canon models`
### Emission cadence handover mappings
- ID: `mapping/emission-cadence-handover`
- Kind: `mapping`
- Canonical path: `assimilation/emission-cadence/mappings.yaml`
- Source path: `infospace/assimilation/emission-cadence/source/EmissionCadenceDeclaration.md`
- Summary: Mapping artifact connecting canon surfaces: Emission cadence handover mappings.
- Imports and anchors: none
- Owned concepts: `Emission cadence handover mappings`
### Purpose Demand Governance Extension Candidates
- ID: `mapping/purpose-demand-governance-candidates`
@ -567,6 +597,16 @@ Items: **71**
- Imports and anchors: `kernel/itc-core`
- Owned concepts: `PatternLanguage`, `PracticePattern`, `PracticePattern Scheme`
### Small SaaS Production Capability Requirements
- ID: `small-saas/capability-requirements/production`
- Kind: `profile-artifact`
- Canonical path: `profiles/small-saas/artifacts/capability-requirements.yaml`
- Source path: `profiles/small-saas/artifacts/capability-requirements.yaml`
- Summary: Example artifact for the small-saas profile: Small SaaS Production Capability Requirements.
- Imports and anchors: `model/capability`
- Owned concepts: `Small SaaS Production Capability Requirements`
### Namespace Per Tenant Control
- ID: `small-saas/control/namespace-per-tenant`
@ -707,6 +747,16 @@ Items: **71**
- Imports and anchors: `kernel/itc-core`, `model/access-control`, `model/data`, `model/devsecops`, `model/governance`, `model/network`, `model/observability`, `model/organization`, `model/security`, `model/task`, `standard/tagging`
- Owned concepts: `CARINGAccessDescriptor`, `CARINGAnalysisFitnessTest`, `CARINGAnalysisProcedure`, `CARINGCanonicalRole`, `CARINGCapabilityProfile`, `CARINGDeclaredAccessMap`, `CARINGDerivedCapability`, `CARINGEffectiveAccessMap`, `CARINGExposureEvent`, `CARINGExposureMode`, `CARINGInducedAccess`, `CARINGOrganizationRelation`, `CARINGPlane`, `CARINGRedesignProcedure`, `CARINGRestrictionPrecedence`, `InfoTechCanon CARING Access Governance Standard`
### InfoTechCanon Emission Cadence Standard
- ID: `standard/emission-cadence`
- Kind: `standard`
- Canonical path: `standards/emission-cadence/InfoTechCanonEmissionCadenceStandard.md`
- Source path: `infospace/assimilation/emission-cadence/source/EmissionCadenceDeclaration.md`
- Summary: Cross-cutting canon standard: InfoTechCanon Emission Cadence Standard.
- Imports and anchors: `kernel/itc-core`, `model/governance`, `model/observability`
- Owned concepts: `EmissionCadenceDeclaration`, `EmissionCadenceForm`, `ExpectedRateCadence`, `HeartbeatCadence`, `InfoTechCanon Emission Cadence Standard`, `ReconciliationCadence`
### InfoTechCanon Repository Layout Standard
- ID: `standard/repository-layout`

View file

@ -1,7 +1,21 @@
schema: info-tech-canon.retrieval-index.v1
infospace: canon
item_count: 71
item_count: 76
items:
- id: assimilation/emission-cadence
kind: assimilation
title: "Assimilation \u2014 EmissionCadenceDeclaration handover"
canonical_path: assimilation/emission-cadence/ASSIMILATION.md
source_path: infospace/assimilation/emission-cadence/source/EmissionCadenceDeclaration.md
summary: "Canon artifact: Assimilation \u2014 EmissionCadenceDeclaration handover."
owned_concepts:
- "Assimilation \u2014 EmissionCadenceDeclaration handover"
imports:
- kernel/itc-core
relationships:
- type: conforms_to
target: kernel/itc-core
warnings: []
- id: assimilation/it-capability-canon
kind: assimilation
title: "Assimilation \u2014 IT Capability Canon (ITCC) v0.1"
@ -595,6 +609,20 @@ items:
- type: uses
target: profile/small-saas
warnings: []
- id: example/emission-cadence/qonto-assistant
kind: example
title: Qonto Assistant Emission Cadence Worked Example
canonical_path: standards/emission-cadence/examples/qonto-assistant.yaml
source_path: infospace/assimilation/emission-cadence/source/EmissionCadenceDeclaration.md
summary: 'Canon-side example artifact: Qonto Assistant Emission Cadence Worked Example.'
owned_concepts:
- Qonto Assistant Emission Cadence Worked Example
imports:
- standard/emission-cadence
relationships:
- type: conforms_to
target: standard/emission-cadence
warnings: []
- id: kernel/itc-core
kind: kernel
title: InfoTechCanon Core
@ -661,6 +689,24 @@ items:
imports: []
relationships: []
warnings: []
- id: mapping/emission-cadence-handover
kind: mapping
title: Emission cadence handover mappings
canonical_path: assimilation/emission-cadence/mappings.yaml
source_path: infospace/assimilation/emission-cadence/source/EmissionCadenceDeclaration.md
summary: 'Mapping artifact connecting canon surfaces: Emission cadence handover
mappings.'
owned_concepts:
- Emission cadence handover mappings
imports: []
relationships:
- type: maps
target: standard/emission-cadence
- type: maps
target: model/observability
- type: maps
target: model/governance
warnings: []
- id: mapping/purpose-demand-governance-candidates
kind: mapping
title: Purpose Demand Governance Extension Candidates
@ -1280,6 +1326,25 @@ items:
- type: conforms_to
target: kernel/itc-core
warnings: []
- id: small-saas/capability-requirements/production
kind: profile-artifact
title: Small SaaS Production Capability Requirements
canonical_path: profiles/small-saas/artifacts/capability-requirements.yaml
source_path: profiles/small-saas/artifacts/capability-requirements.yaml
summary: 'Example artifact for the small-saas profile: Small SaaS Production Capability
Requirements.'
owned_concepts:
- Small SaaS Production Capability Requirements
imports:
- model/capability
relationships:
- type: instantiates
target: profile/small-saas
- type: uses
target: model/capability
- type: applies_to
target: small-saas/service/billing-portal
warnings: []
- id: small-saas/control/namespace-per-tenant
kind: profile-artifact
title: Namespace Per Tenant Control
@ -1609,6 +1674,35 @@ items:
- type: imports
target: standard/tagging
warnings: []
- id: standard/emission-cadence
kind: standard
title: InfoTechCanon Emission Cadence Standard
canonical_path: standards/emission-cadence/InfoTechCanonEmissionCadenceStandard.md
source_path: infospace/assimilation/emission-cadence/source/EmissionCadenceDeclaration.md
summary: 'Cross-cutting canon standard: InfoTechCanon Emission Cadence Standard.'
owned_concepts:
- EmissionCadenceDeclaration
- EmissionCadenceForm
- ExpectedRateCadence
- HeartbeatCadence
- InfoTechCanon Emission Cadence Standard
- ReconciliationCadence
imports:
- kernel/itc-core
- model/governance
- model/observability
relationships:
- type: conforms_to
target: kernel/itc-core
- type: imports
target: model/observability
- type: imports
target: model/governance
- type: related_to
target: model/security
- type: derived_from
target: assimilation/emission-cadence
warnings: []
- id: standard/repository-layout
kind: standard
title: InfoTechCanon Repository Layout Standard

View file

@ -1193,3 +1193,73 @@ artifacts:
target: small-saas/control/namespace-per-tenant
- type: evidenced_by
target: small-saas/evidence/access-review-2026-05
- id: standard/emission-cadence
path: standards/emission-cadence/InfoTechCanonEmissionCadenceStandard.md
kind: standard
title: InfoTechCanon Emission Cadence Standard
provenance:
source_path: infospace/assimilation/emission-cadence/source/EmissionCadenceDeclaration.md
placement: adapted
placement_workplan: ITC-WP-0018
assimilation: assimilation/emission-cadence
relationships:
- type: conforms_to
target: kernel/itc-core
- type: imports
target: model/observability
- type: imports
target: model/governance
- type: related_to
target: model/security
- type: derived_from
target: assimilation/emission-cadence
- id: assimilation/emission-cadence
path: assimilation/emission-cadence/ASSIMILATION.md
kind: assimilation
title: Assimilation — EmissionCadenceDeclaration handover
provenance:
source_path: infospace/assimilation/emission-cadence/source/EmissionCadenceDeclaration.md
disposition: adapt
placement_workplan: ITC-WP-0018
relationships:
- type: conforms_to
target: kernel/itc-core
- id: mapping/emission-cadence-handover
path: assimilation/emission-cadence/mappings.yaml
kind: mapping
title: Emission cadence handover mappings
provenance:
source_path: infospace/assimilation/emission-cadence/source/EmissionCadenceDeclaration.md
placement_workplan: ITC-WP-0018
relationships:
- type: maps
target: standard/emission-cadence
- type: maps
target: model/observability
- type: maps
target: model/governance
- id: example/emission-cadence/qonto-assistant
path: standards/emission-cadence/examples/qonto-assistant.yaml
kind: example
title: Qonto Assistant Emission Cadence Worked Example
provenance:
source_path: infospace/assimilation/emission-cadence/source/EmissionCadenceDeclaration.md
placement: adapted-example
placement_workplan: ITC-WP-0018
relationships:
- type: conforms_to
target: standard/emission-cadence
- id: small-saas/capability-requirements/production
path: profiles/small-saas/artifacts/capability-requirements.yaml
kind: profile-artifact
title: Small SaaS Production Capability Requirements
provenance:
profile: small-saas
placement_workplan: ITC-WP-0014
relationships:
- type: instantiates
target: profile/small-saas
- type: uses
target: model/capability
- type: applies_to
target: small-saas/service/billing-portal

View file

@ -0,0 +1,79 @@
# Assimilation — EmissionCadenceDeclaration
**Status:** Closed
**Disposition:** Adapt
**Source:** King's Guard Taxonomy draft 0.1.0
**Authority:** `GH-DEC-2026-004` / State Hub decision
`89c73f45-d07b-40ea-b428-5a7375ce4b09`
## Scope
This assimilation covers the generic, ecosystem-wide shape by which a source
declares an expected emission cadence for an event class. It does not absorb
the NetKingdom security profile: evidence-class policy, MUST/SHOULD obligations,
and the rule requiring heartbeat plus reconciliation for rare load-bearing
classes remain owned by NetKingdom.
## Findings
- The Observability Model already owns `Signal`, `SignalSource`, `Event`,
`EventSource`, and the missing-signal pattern. It does not own a portable
source declaration for the expected arrival of an event class.
- The Governance Model already owns `Finding`. A cadence declaration names
detection conditions but does not redefine the finding record or lifecycle.
- The handover contains two useful generic forms: an expected count over a
window, and a positive heartbeat and/or count reconciliation for streams
whose meaningful events are intermittent.
- `evidence_class`, security modality, and required combinations are importing
profile concerns rather than generic cadence semantics.
## DecisionRecord
### Context
King's Guard needs a stable contract to evaluate silence but is a Staff-layer
consumer, not the Taxonomy owner. Gate House assigned the generic contract to
InfoTechCanon and the NetKingdom security profile to `net-kingdom`.
### Decision
Adapt the draft into `standard/emission-cadence` and schema version `0.1`.
Preserve its two form names and field meanings. Make profile classifications
optional extension data, and let the heartbeat-or-reconciliation form contain
either mechanism or both. Publish strict validation for the generic core and a
namespaced `extensions` object for profile-owned additions.
### Options Considered
- Keep the schema in King's Guard — rejected because a consumer would own the
semantics it evaluates.
- Put the whole contract in NetKingdom — rejected because generic cadence is
reusable outside that security estate.
- Joint ownership — rejected because version authority would be ambiguous.
- Adapt the generic core here and import it from a NetKingdom profile — chosen.
### Rationale
The split follows the repository's Taxonomy role and Core's single-owner rule.
Allowing heartbeat, reconciliation, or both keeps the generic form useful while
leaving NetKingdom free to require the stronger combination.
### Consequences
- Sources own their declaration instances and emission behavior.
- Observers own evaluation and findings, not the declaration schema.
- Importing profiles may require fields or combinations but may not change the
generic fields' meanings.
- King's Guard's draft becomes provenance rather than a competing contract.
### Review Trigger
Review the draft after two independent source implementations, or when an
importing profile needs a third cadence form that cannot be expressed through
extensions without changing generic semantics.
## Result
The source was adapted, not copied into the canon. The resulting standard,
schema, and worked example are registered in canon 0.7.0 and validated by the
service surface.

View file

@ -0,0 +1,18 @@
id: assimilation/emission-cadence
title: Assimilation — EmissionCadenceDeclaration handover
source: King's Guard Emission-cadence declaration Taxonomy draft
source_version: "0.1.0"
source_type: internal-draft
source_files:
- source/EmissionCadenceDeclaration.md
requested_by: gate-house
status: closed
disposition: adapt
impacts:
- model/observability
- model/governance
- standard/emission-cadence
decision:
authority: GH-DEC-2026-004
decided_by: Bernd Worsch
decided_at: "2026-09-04T00:55:29Z"

View file

@ -0,0 +1,12 @@
# Comparison matrix — EmissionCadenceDeclaration
| Source concept | Canon comparison | Disposition |
| --- | --- | --- |
| EmissionCadenceDeclaration | Missing portable declaration contract | Add standard-owned concept |
| expected-rate | Missing bounded-count declaration | Add generic form |
| heartbeat | ITC-OBS has missing-signal semantics, but no source declaration | Add form component; import observability terms |
| reconciliation | Missing source/observer count comparison declaration | Add form component |
| finding | ITC-GOV already owns the assessment outcome | Import; do not redefine |
| evidence_class | NetKingdom security viewpoint | Leave to importing profile via extensions |
| load-bearing MUST/SHOULD rules | NetKingdom doctrine | Exclude from generic standard |
| King's Guard evaluation behavior | Consumer implementation | Exclude from canon contract |

View file

@ -0,0 +1,33 @@
source: KG-DRAFT-EMISSION-CADENCE
concepts:
- id: emission-cadence-declaration
source_term: EmissionCadenceDeclaration
definition: A source-authored statement of expected event-class emission.
classification: missing_concept
proposed_owner: standard/emission-cadence
- id: expected-rate-cadence
source_term: expected-rate
definition: A minimum event count expected within a bounded window.
classification: missing_concept
proposed_owner: standard/emission-cadence
- id: heartbeat-cadence
source_term: heartbeat
definition: A positive liveness claim expected within an interval.
classification: broader_than_existing
existing_anchor: model/observability
proposed_owner: standard/emission-cadence
- id: reconciliation-cadence
source_term: reconciliation
definition: A comparison between source-side and observer-side event counts.
classification: missing_concept
proposed_owner: standard/emission-cadence
- id: evidence-class
source_term: evidence_class
definition: Security importance assigned to an emitted event class.
classification: viewpoint_difference
disposition: importing-profile-extension
- id: finding
source_term: finding
definition: The observer outcome produced by a cadence breach.
classification: already_covered
existing_anchor: model/governance

View file

@ -0,0 +1,25 @@
id: mapping/emission-cadence-handover
title: Emission cadence handover mappings
source: KG-DRAFT-EMISSION-CADENCE
target: standard/emission-cadence
mappings:
- source_concept: EmissionCadenceDeclaration
target_concept: EmissionCadenceDeclaration
mapping_type: adapted
- source_concept: expected-rate
target_concept: ExpectedRateCadence
mapping_type: equivalent
- source_concept: heartbeat
target_concept: HeartbeatCadence
mapping_type: adapted
- source_concept: reconciliation
target_concept: ReconciliationCadence
mapping_type: adapted
- source_concept: finding
target: model/governance
target_concept: Finding
mapping_type: imports
- source_concept: event_class
target: model/observability
target_concept: EventType
mapping_type: imports

View file

@ -0,0 +1,14 @@
# Open questions — EmissionCadenceDeclaration
No question blocks adoption.
The following promotion questions remain for the draft's future review:
1. Do two independent source implementations need interval tolerance or grace
fields in the generic core, or can profiles carry them in `extensions`?
2. Should schema 1.0 retain the handed-over name `sources` for cadence entries,
or migrate to the clearer `cadences` with explicit compatibility tooling?
3. Does reconciliation eventually need a generic typed counter-selector
language, or are owner-defined field references sufficient?
These are review triggers, not deferred implementation tasks.

View file

@ -0,0 +1,12 @@
# Proposed changes — resolved
1. Publish a draft Emission Cadence Standard under `infospace/standards/`.
2. Publish and register `emission-cadence.schema.yaml`.
3. Include one schema-valid worked example derived from the handed-over
`qonto-assistant` fixture without claiming it is the source-owned instance.
4. Add structural validation for the schema and example.
5. Register the standard and assimilation in all retrieval surfaces.
6. Bump the canon minor version and record compatibility rules.
All proposals were accepted under `GH-DEC-2026-004` and implemented by
`ITC-WP-0018`.

View file

@ -0,0 +1,17 @@
# Source summary — EmissionCadenceDeclaration draft
The King's Guard draft proposes a source-authored declaration that makes stream
silence observable. It distinguishes two forms:
- `expected-rate`: an event-class minimum over a time window;
- `heartbeat-or-reconciliation`: a positive liveness assertion, a comparison of
source and observed counts, or both.
The draft was written against `qonto-assistant` and the Gate House approval
emission contract. It assigns evaluation to King's Guard and explicitly asks a
Taxonomy repository to own the schema.
Security-specific content associates event classes with `attributive` or
`load-bearing` evidence and requires the stronger form for rare, load-bearing
events. That policy is part of the source context, not the generic core adopted
by InfoTechCanon.

View file

@ -0,0 +1,134 @@
---
title: Emission-cadence declaration (Taxonomy draft)
document_id: KG-DRAFT-EMISSION-CADENCE
version: 0.1.0
status: Draft-for-handover
date: 2026-09-01
drafter: kings-guard
owner: Taxonomy
worked_example: qonto-assistant
reference_instance: GH-WP-0002-T04
reference_source_declaration: approval-engine/cadence.yaml
statute: net-kingdom/canon/standards/security-layer-model_v0.7.md
sections: ["9.6", "17"]
classification: Public
---
# Emission-cadence declaration — Taxonomy draft
kings-guard drafts this artifact because it is the only consumer of
silence-as-signal and cannot implement §9.6 without a declared cadence.
**Ownership stays with Taxonomy.** This file is a handover, not an internal
schema. Inventing a local shape and keeping it here would be the drift
§17 exists to prevent.
Proposed Taxonomy homes, neither of which has assented (§17):
- `info-tech-canon` — ecosystem-wide semantic contracts
- `net-kingdom` — NetKingdom standards of record
gate-house already named the heartbeat form as doctrine in
`docs/contracts/approval-emission-detection.md` (`GH-WP-0002-T04`). The
reference source declaration is `approval-engine/cadence.yaml`. This draft
covers **both** forms, because one does not substitute for the other.
## 1. Why this belongs alongside the security genome
A source already declares intended healthy operation as a `security_genome`:
purpose, permitted capabilities, egress, tolerances. Expected emission cadence
is a claim of the same kind — a statement of intent about the evidence the
source will publish, not a measurement kings-guard takes of it.
Putting the declaration next to the genome keeps three properties:
1. **The class is the source's declaration.** Load-bearing versus attributive
is not inferred by the observer from event contents.
2. **The form follows the class.** Volume classes declare an expected rate.
Low-volume load-bearing classes declare a heartbeat or reconciliation.
Rate monitoring is forbidden for the latter: a suppressed month of
revocations is indistinguishable from a quiet one.
3. **Silence becomes observable without Tooling contact.** The source
publishes the stream, including the positive claim that can itself go
missing. kings-guard compares what arrived against what was declared.
## 2. Both forms
### 2.1 Expected rate — volume classes
Use when the class has a rate that can drop.
```yaml
form: expected-rate
event_class: <name>
evidence_class: attributive | load-bearing
window: 24h
expected_min: <integer>
drop_below: finding
```
A drop below `expected_min` in `window` is a finding about the **stream**,
not about any record's contents.
Load-bearing volume classes MUST declare this form (or the heartbeat form
if they are in fact low-volume). Attributive sources SHOULD.
### 2.2 Heartbeat or reconciliation — low-volume load-bearing classes
Use when the valuable event is rare: revocations, denials, containment
actions. Rate monitoring cannot work. The required property is a **positive
claim that can itself go missing**.
Reference instance: `GH-WP-0002-T04` / `approval-engine/cadence.yaml`.
Form is heartbeat **plus** reconciliation, not rate monitoring.
```yaml
form: heartbeat-or-reconciliation
event_class: <name>
evidence_class: load-bearing
rate_monitoring: forbidden
heartbeat:
event_class: <name>.heartbeat # or a dedicated heartbeat class
interval: 24h
assertion: nothing-to-report
missing: finding
reconciliation:
compare_local: source transition counts per class
compare_observed: evidence-engine counts per class
divergence: finding
undrained_local: lag-not-divergence
```
A missing heartbeat, or a reconciliation divergence, is a finding about the
stream. None of these are informational logs.
## 3. Worked example — `qonto-assistant`
The one real source this draft is written against.
| Event class | Evidence class | Form | Why |
| --- | --- | --- | --- |
| `audit.allow` | attributive | expected-rate (SHOULD) | Forensic reconstruction; no control branches on presence. Completeness is not claimed. The rate row is here so the volume form is specified, not because qonto traffic is currently a meaningful volume class. |
| `audit.deny` | load-bearing | heartbeat-or-reconciliation (MUST) | Deny-escalation and posture branch on deny presence/absence. Statute §9.6 names denials as load-bearing. Denials are infrequent, so rate monitoring is the wrong form. |
| `audit.heartbeat` | load-bearing | the positive claim | `nothing-to-report` plus per-class counts since the previous heartbeat. |
Machine-readable worked example consumed by the local evaluator (draft-shaped,
not a competing schema): `src/kings_guard/fixtures/qonto_assistant_cadence.json`.
Until `qonto-assistant` publishes the declaration and emits heartbeats, no
argument may assume this surface is live on that source. kings-guard can
still observe the audit events it does emit; stream completeness for the
deny class stays `unknown` or `degraded` until the positive claim exists.
## 4. Consumer obligations (kings-guard)
- Copy the declared evidence class onto each observation; do not infer it.
- Evaluate the stream against the declaration, not only each record.
- Carry completeness separately from record richness in posture output.
- Treat stream findings as distinct from content findings.
- Open no Tooling client to obtain the stream. The source publishes it.
## 5. Handover
Sent to `gate-house`, `net-kingdom`, and `info-tech-canon` for ownership.
kings-guard will consume whatever Taxonomy publishes; it will not fork this
draft into a private schema.

View file

@ -1,5 +1,5 @@
root: infospace
file_count: 191
file_count: 208
files:
- path: README.md
directory: .
@ -79,6 +79,9 @@ files:
- path: agent/briefs/example-consumer-purpose-portfolio.md
directory: agent/briefs
name: example-consumer-purpose-portfolio.md
- path: agent/briefs/example-emission-cadence-qonto-assistant.md
directory: agent/briefs
name: example-emission-cadence-qonto-assistant.md
- path: agent/briefs/kernel-itc-core.md
directory: agent/briefs
name: kernel-itc-core.md
@ -88,6 +91,9 @@ files:
- path: agent/briefs/mapping-capability-anchors.md
directory: agent/briefs
name: mapping-capability-anchors.md
- path: agent/briefs/mapping-emission-cadence-handover.md
directory: agent/briefs
name: mapping-emission-cadence-handover.md
- path: agent/briefs/mapping-purpose-demand-governance-candidates.md
directory: agent/briefs
name: mapping-purpose-demand-governance-candidates.md
@ -133,6 +139,9 @@ files:
- path: agent/briefs/pattern-intent-scope-purposes.md
directory: agent/briefs
name: pattern-intent-scope-purposes.md
- path: agent/briefs/practice-pattern-agentic-drives-functional.md
directory: agent/briefs
name: practice-pattern-agentic-drives-functional.md
- path: agent/briefs/practice-pattern-interface-deprecation-strangler.md
directory: agent/briefs
name: practice-pattern-interface-deprecation-strangler.md
@ -163,6 +172,9 @@ files:
- path: agent/briefs/standard-caring.md
directory: agent/briefs
name: standard-caring.md
- path: agent/briefs/standard-emission-cadence.md
directory: agent/briefs
name: standard-emission-cadence.md
- path: agent/briefs/standard-repository-layout.md
directory: agent/briefs
name: standard-repository-layout.md
@ -217,6 +229,33 @@ files:
- path: assimilation/README.md
directory: assimilation
name: README.md
- path: assimilation/emission-cadence/ASSIMILATION.md
directory: assimilation/emission-cadence
name: ASSIMILATION.md
- path: assimilation/emission-cadence/assimilation.yaml
directory: assimilation/emission-cadence
name: assimilation.yaml
- path: assimilation/emission-cadence/comparison-matrix.md
directory: assimilation/emission-cadence
name: comparison-matrix.md
- path: assimilation/emission-cadence/extracted-concepts.yaml
directory: assimilation/emission-cadence
name: extracted-concepts.yaml
- path: assimilation/emission-cadence/mappings.yaml
directory: assimilation/emission-cadence
name: mappings.yaml
- path: assimilation/emission-cadence/open-questions.md
directory: assimilation/emission-cadence
name: open-questions.md
- path: assimilation/emission-cadence/proposed-changes.md
directory: assimilation/emission-cadence
name: proposed-changes.md
- path: assimilation/emission-cadence/source/EmissionCadenceDeclaration.md
directory: assimilation/emission-cadence/source
name: EmissionCadenceDeclaration.md
- path: assimilation/emission-cadence/source-summary.md
directory: assimilation/emission-cadence
name: source-summary.md
- path: assimilation/intake-and-assimilation-practice.md
directory: assimilation
name: intake-and-assimilation-practice.md
@ -424,6 +463,9 @@ files:
- path: profiles/README.md
directory: profiles
name: README.md
- path: profiles/small-saas/artifacts/capability-requirements.yaml
directory: profiles/small-saas/artifacts
name: capability-requirements.yaml
- path: profiles/small-saas/artifacts/control.namespace-per-tenant.yaml
directory: profiles/small-saas/artifacts
name: control.namespace-per-tenant.yaml
@ -496,6 +538,9 @@ files:
- path: schemas/concept.schema.yaml
directory: schemas
name: concept.schema.yaml
- path: schemas/emission-cadence.schema.yaml
directory: schemas
name: emission-cadence.schema.yaml
- path: schemas/index.yaml
directory: schemas
name: index.yaml
@ -538,6 +583,12 @@ files:
- path: standards/caring/benchmarks/kubernetes-rbac/native-concepts.yaml
directory: standards/caring/benchmarks/kubernetes-rbac
name: native-concepts.yaml
- path: standards/emission-cadence/InfoTechCanonEmissionCadenceStandard.md
directory: standards/emission-cadence
name: InfoTechCanonEmissionCadenceStandard.md
- path: standards/emission-cadence/examples/qonto-assistant.yaml
directory: standards/emission-cadence/examples
name: qonto-assistant.yaml
- path: standards/repository-layout/InfoTechCanonRepositoryLayoutStandard.md
directory: standards/repository-layout
name: InfoTechCanonRepositoryLayoutStandard.md

View file

@ -1,5 +1,9 @@
concept_count: 119
concept_count: 129
concepts:
- concept: "Assimilation \u2014 EmissionCadenceDeclaration handover"
owner: assimilation/emission-cadence
path: assimilation/emission-cadence/ASSIMILATION.md
source: artifact_title
- concept: "Assimilation \u2014 IT Capability Canon (ITCC) v0.1"
owner: assimilation/it-capability-canon
path: assimilation/it-capability-canon/ASSIMILATION.md
@ -104,6 +108,10 @@ concepts:
owner: example/consumer-purpose-portfolio
path: examples/consumer-purpose-portfolio.yaml
source: artifact_title
- concept: Qonto Assistant Emission Cadence Worked Example
owner: example/emission-cadence/qonto-assistant
path: standards/emission-cadence/examples/qonto-assistant.yaml
source: artifact_title
- concept: InfoTechCanon Core
owner: kernel/itc-core
path: kernel/InfoTechCanonCore.md
@ -116,6 +124,10 @@ concepts:
owner: mapping/capability-anchors
path: mappings/capability-anchors.yaml
source: artifact_title
- concept: Emission cadence handover mappings
owner: mapping/emission-cadence-handover
path: assimilation/emission-cadence/mappings.yaml
source: artifact_title
- concept: Purpose Demand Governance Extension Candidates
owner: mapping/purpose-demand-governance-candidates
path: mappings/purpose-demand-governance-candidates.yaml
@ -338,6 +350,10 @@ concepts:
owner: scheme/practice-pattern
path: patterns/PracticePatternScheme.md
source: frontmatter.owned_concepts
- concept: Small SaaS Production Capability Requirements
owner: small-saas/capability-requirements/production
path: profiles/small-saas/artifacts/capability-requirements.yaml
source: artifact_title
- concept: Namespace Per Tenant Control
owner: small-saas/control/namespace-per-tenant
path: profiles/small-saas/artifacts/control.namespace-per-tenant.yaml
@ -454,6 +470,30 @@ concepts:
owner: standard/caring
path: standards/caring/InfoTechCanonCaringAccessGovernanceStandard.md
source: frontmatter.owned_concepts
- concept: InfoTechCanon Emission Cadence Standard
owner: standard/emission-cadence
path: standards/emission-cadence/InfoTechCanonEmissionCadenceStandard.md
source: artifact_title
- concept: EmissionCadenceDeclaration
owner: standard/emission-cadence
path: standards/emission-cadence/InfoTechCanonEmissionCadenceStandard.md
source: frontmatter.owned_concepts
- concept: EmissionCadenceForm
owner: standard/emission-cadence
path: standards/emission-cadence/InfoTechCanonEmissionCadenceStandard.md
source: frontmatter.owned_concepts
- concept: ExpectedRateCadence
owner: standard/emission-cadence
path: standards/emission-cadence/InfoTechCanonEmissionCadenceStandard.md
source: frontmatter.owned_concepts
- concept: HeartbeatCadence
owner: standard/emission-cadence
path: standards/emission-cadence/InfoTechCanonEmissionCadenceStandard.md
source: frontmatter.owned_concepts
- concept: ReconciliationCadence
owner: standard/emission-cadence
path: standards/emission-cadence/InfoTechCanonEmissionCadenceStandard.md
source: frontmatter.owned_concepts
- concept: InfoTechCanon Repository Layout Standard
owner: standard/repository-layout
path: standards/repository-layout/InfoTechCanonRepositoryLayoutStandard.md

View file

@ -1,4 +1,5 @@
artifacts:
- assimilation/emission-cadence
- assimilation/it-capability-canon
- benchmark/caring/kubernetes-rbac
- benchmark/caring/kubernetes-rbac/access-descriptors
@ -25,9 +26,11 @@ artifacts:
- evaluation/user-engine/questions
- evaluation/user-engine/small-saas-alignment
- example/consumer-purpose-portfolio
- example/emission-cadence/qonto-assistant
- kernel/itc-core
- kernel/itc-kernel-map
- mapping/capability-anchors
- mapping/emission-cadence-handover
- mapping/purpose-demand-governance-candidates
- model/access-control
- model/capability
@ -54,6 +57,7 @@ artifacts:
- review-kit/alignment/workflow
- review-kit/alignment/workplan-template
- scheme/practice-pattern
- small-saas/capability-requirements/production
- small-saas/control/namespace-per-tenant
- small-saas/dataset/subscription-ledger
- small-saas/deployment/production
@ -68,9 +72,14 @@ artifacts:
- small-saas/tenant/globex
- small-saas/user/ada-admin
- standard/caring
- standard/emission-cadence
- standard/repository-layout
- standard/tagging
rows:
- artifact: assimilation/emission-cadence
targets:
kernel/itc-core:
- conforms_to
- artifact: assimilation/it-capability-canon
targets:
kernel/itc-core:
@ -353,6 +362,10 @@ rows:
- illustrates
profile/small-saas:
- uses
- artifact: example/emission-cadence/qonto-assistant
targets:
standard/emission-cadence:
- conforms_to
- artifact: kernel/itc-core
targets: {}
- artifact: kernel/itc-kernel-map
@ -389,6 +402,14 @@ rows:
- maps
- artifact: mapping/capability-anchors
targets: {}
- artifact: mapping/emission-cadence-handover
targets:
model/governance:
- maps
model/observability:
- maps
standard/emission-cadence:
- maps
- artifact: mapping/purpose-demand-governance-candidates
targets:
model/governance:
@ -641,6 +662,14 @@ rows:
targets:
kernel/itc-core:
- conforms_to
- artifact: small-saas/capability-requirements/production
targets:
model/capability:
- uses
profile/small-saas:
- instantiates
small-saas/service/billing-portal:
- applies_to
- artifact: small-saas/control/namespace-per-tenant
targets:
model/security:
@ -801,6 +830,18 @@ rows:
- imports
standard/tagging:
- imports
- artifact: standard/emission-cadence
targets:
assimilation/emission-cadence:
- derived_from
kernel/itc-core:
- conforms_to
model/governance:
- imports
model/observability:
- imports
model/security:
- related_to
- artifact: standard/repository-layout
targets:
kernel/itc-core:

View file

@ -39,6 +39,8 @@ disciplines:
path: standards/caring/InfoTechCanonCaringAccessGovernanceStandard.md
- name: Repository Layout Standard
path: standards/repository-layout/InfoTechCanonRepositoryLayoutStandard.md
- name: Emission Cadence Standard
path: standards/emission-cadence/InfoTechCanonEmissionCadenceStandard.md
schemas:
standard: schemas/standard.schema.yaml
practice-pattern: schemas/practice-pattern.schema.yaml
@ -52,6 +54,7 @@ schemas:
capability: schemas/capability.schema.yaml
capability-record: schemas/capability-record.schema.yaml
attribute-value-type: schemas/attribute-value-type.schema.yaml
emission-cadence: schemas/emission-cadence.schema.yaml
workflows: []
viability:
redundancy_ratio:

View file

@ -0,0 +1,68 @@
id: small-saas/capability-requirements/production
kind: capability-requirement-set
title: Small SaaS Production Capability Requirements
profile: small-saas
record_id: small-saas-production-capabilities
requires:
- capability: identity.authorization
profile: rbac
minimum_maturity: D4
targets:
policy_coverage:
value: all-tenant-routes
- capability: data.transactional
profile: relational
minimum_maturity: D4
targets:
durability:
value: production-approved
- capability: integration.api
profile: request-response
minimum_maturity: D4
targets:
compatibility:
value: versioned-contract
- capability: operations.observability
profile: events
minimum_maturity: D3
targets:
coverage:
value: tenant-access-and-service-health
provisions:
- provider: small-saas/control/namespace-per-tenant
capability: identity.authorization
profile: rbac
maturity: D4
evidence:
- hook: policy_tests
basis: measured
source: small-saas/evidence/access-review-2026-05
- provider: small-saas/dataset/subscription-ledger
capability: data.transactional
profile: relational
maturity: D4
evidence:
- hook: durability_tests
basis: measured
source: small-saas/evidence/access-review-2026-05
- provider: small-saas/service/billing-portal
capability: integration.api
profile: request-response
maturity: D4
evidence:
- hook: contract_tests
basis: measured
source: small-saas/evidence/access-review-2026-05
- provider: small-saas/deployment/production
capability: operations.observability
profile: events
maturity: D3
evidence:
- hook: telemetry_coverage
basis: measured
source: small-saas/evidence/access-review-2026-05
relationships:
- type: instantiates
target: profile/small-saas
- type: applies_to
target: small-saas/service/billing-portal

View file

@ -22,6 +22,7 @@ required_standards:
- model/devsecops
- model/network
- model/observability
- model/capability
- standard/tagging
- standard/caring
required_concepts:
@ -87,6 +88,7 @@ artifact_ids:
- small-saas/control/namespace-per-tenant
- small-saas/evidence/access-review-2026-05
- small-saas/incident/cross-tenant-access-attempt
- small-saas/capability-requirements/production
validation_rules:
required_artifact_kinds:
- service

View file

@ -0,0 +1,159 @@
$schema: https://json-schema.org/draft/2020-12/schema
$id: https://info-tech-canon.local/schemas/emission-cadence.schema.yaml
title: InfoTechCanon EmissionCadenceDeclaration 0.1
description: Generic source-authored event emission cadence declaration.
type: object
required:
- schema_version
- declaration_id
- source
- sources
properties:
schema_version:
const: "0.1"
declaration_id:
$ref: "#/$defs/non_empty_string"
source:
$ref: "#/$defs/non_empty_string"
stream_id:
$ref: "#/$defs/non_empty_string"
sources:
type: array
minItems: 1
items:
$ref: "#/$defs/cadence_entry"
extensions:
$ref: "#/$defs/extensions"
additionalProperties: false
$defs:
non_empty_string:
type: string
minLength: 1
duration:
type: string
pattern: "^(?:P(?=\\d|T\\d)(?:\\d+D)?(?:T(?:\\d+H)?(?:\\d+M)?(?:\\d+S)?)?|[1-9][0-9]*(?:s|m|h|d))$"
extensions:
type: object
minProperties: 1
propertyNames:
pattern: "^[a-z][a-z0-9.-]*$"
additionalProperties:
type: object
heartbeat:
type: object
required:
- event_class
- assertion
- missing
properties:
event_class:
$ref: "#/$defs/non_empty_string"
interval:
$ref: "#/$defs/duration"
interval_seconds:
type: integer
minimum: 1
assertion:
$ref: "#/$defs/non_empty_string"
missing:
$ref: "#/$defs/non_empty_string"
extensions:
$ref: "#/$defs/extensions"
oneOf:
- required: [interval]
not:
required: [interval_seconds]
- required: [interval_seconds]
not:
required: [interval]
additionalProperties: false
reconciliation:
type: object
required:
- compare_local
- compare_observed
- divergence
properties:
compare_local:
$ref: "#/$defs/non_empty_string"
compare_observed:
$ref: "#/$defs/non_empty_string"
divergence:
$ref: "#/$defs/non_empty_string"
undrained_local:
$ref: "#/$defs/non_empty_string"
extensions:
$ref: "#/$defs/extensions"
additionalProperties: false
cadence_entry:
type: object
required:
- source_id
- event_class
- form
properties:
source_id:
$ref: "#/$defs/non_empty_string"
source_system:
$ref: "#/$defs/non_empty_string"
event_class:
$ref: "#/$defs/non_empty_string"
form:
enum:
- expected-rate
- heartbeat-or-reconciliation
window:
$ref: "#/$defs/duration"
window_seconds:
type: integer
minimum: 1
expected_min:
type: integer
minimum: 0
drop_below:
$ref: "#/$defs/non_empty_string"
heartbeat:
$ref: "#/$defs/heartbeat"
reconciliation:
$ref: "#/$defs/reconciliation"
extensions:
$ref: "#/$defs/extensions"
allOf:
- if:
properties:
form:
const: expected-rate
required: [form]
then:
required:
- expected_min
- drop_below
oneOf:
- required: [window]
not:
anyOf:
- required: [window_seconds]
- required: [heartbeat]
- required: [reconciliation]
- required: [window_seconds]
not:
anyOf:
- required: [window]
- required: [heartbeat]
- required: [reconciliation]
- if:
properties:
form:
const: heartbeat-or-reconciliation
required: [form]
then:
anyOf:
- required: [heartbeat]
- required: [reconciliation]
not:
anyOf:
- required: [window]
- required: [window_seconds]
- required: [expected_min]
- required: [drop_below]
additionalProperties: false

View file

@ -25,3 +25,5 @@ schemas:
path: capability-record.schema.yaml
- id: attribute-value-type
path: attribute-value-type.schema.yaml
- id: emission-cadence
path: emission-cadence.schema.yaml

View file

@ -0,0 +1,214 @@
---
id: itc-emission-cadence:EmissionCadenceDeclaration
title: InfoTechCanon Emission Cadence Standard
short_name: ITC-EMISSION-CADENCE
type: standard
standard_family: InfoTechCanon
repository_context: info-tech-canon
recommended_path: standards/emission-cadence/InfoTechCanonEmissionCadenceStandard.md
status: draft
version: 0.1.0
schema_version: "0.1"
canonical_owner: InfoTechCanonEmissionCadenceStandard
namespace: itc-emission-cadence
classification: standard
primary_cluster: observability-contract
imports:
- InfoTechCanonCore
- InfoTechCanonObservabilityModel
- InfoTechCanonGovernanceModel
related:
- InfoTechCanonSecurityModel
owned_concepts:
- EmissionCadenceDeclaration
- EmissionCadenceForm
- ExpectedRateCadence
- HeartbeatCadence
- ReconciliationCadence
provenance:
source_version: 0.1.0
source_file: infospace/assimilation/emission-cadence/source/EmissionCadenceDeclaration.md
assimilation: assimilation/emission-cadence
decision: GH-DEC-2026-004
created_at: "2026-09-04"
updated_at: "2026-09-04"
---
# InfoTechCanon Emission Cadence Standard
**Short Name:** `ITC-EMISSION-CADENCE`
**Document Status:** Draft
**Version:** 0.1.0
**Schema Version:** `0.1`
## 1. Purpose
This standard defines `EmissionCadenceDeclaration`: a machine-readable,
source-authored claim about when records of an event class are expected to be
emitted. It lets an observer evaluate a stream's silence separately from the
contents and richness of records that did arrive.
The declaration describes intended emission. It is not a measurement, a health
result, or proof that every event was emitted.
## 2. Ownership boundary
InfoTechCanon owns the generic forms, fields, validation semantics,
compatibility rules, and evolution of this contract.
Other owners retain their own responsibilities:
- a source owns each declaration instance and the behavior it declares;
- an observer owns measurement, evaluation, and resulting findings;
- an importing profile owns domain policy: which classes must declare cadence,
which form is required, and any stronger combination or threshold rules;
- ITC-OBS owns `Event`, `EventType`, `EventSource`, and missing-signal semantics;
- ITC-GOV owns `Finding` and its lifecycle.
In particular, this standard does not define `attributive` or `load-bearing`
evidence, does not require cadence for any security class, and does not require
heartbeat and reconciliation together. Those are NetKingdom security-profile
rules, not ecosystem-wide semantics.
## 3. Declaration envelope
A declaration contains:
| Field | Requirement | Meaning |
| --- | --- | --- |
| `schema_version` | required | Contract version understood by the producer. This draft uses `0.1`. |
| `declaration_id` | required | Stable identifier for the declaration instance. |
| `source` | required | Source system that owns the emission claim. |
| `stream_id` | optional | Stable stream identifier when the source publishes more than one stream. |
| `sources` | required | One or more event-class cadence entries. The name is retained from the handed-over 0.1 draft. |
| `extensions` | optional | Namespaced, profile-owned data that does not change generic field meanings. |
Every entry in `sources` has a stable `source_id`, an `event_class`, and exactly
one generic `form`. A declaration must not contain duplicate `source_id` values.
## 4. Forms
### 4.1 `expected-rate`
`ExpectedRateCadence` says that at least `expected_min` records of an event class
are expected in each `window`.
```yaml
source_id: example.audit
event_class: audit.recorded
form: expected-rate
window: PT24H
expected_min: 1
drop_below: finding
```
The window may be an ISO 8601 duration (`PT24H`) or a positive compact duration
using `s`, `m`, `h`, or `d` (`24h`). A producer that cannot use duration strings
may provide `window_seconds` instead, but must not provide both.
Evaluation is performed per complete window unless an importing profile defines
a grace rule. A count below `expected_min` satisfies the condition named by
`drop_below`. The string names an observer-owned outcome; it does not create or
change the ITC-GOV Finding concept.
### 4.2 `heartbeat-or-reconciliation`
This form describes one or both of the following mechanisms:
- `heartbeat`: a positive assertion expected within an interval, so the
assertion can itself be missing;
- `reconciliation`: references to source-side and observer-side counts whose
divergence is evaluated.
At least one mechanism is required by the generic contract. An importing
profile may require both.
```yaml
source_id: example.denials
event_class: audit.denied
form: heartbeat-or-reconciliation
heartbeat:
event_class: audit.heartbeat
interval: PT24H
assertion: nothing-to-report
missing: finding
reconciliation:
compare_local: source_transition_counts.audit.denied
compare_observed: evidence_counts.audit.denied
divergence: finding
undrained_local: lag-not-divergence
```
`heartbeat.interval` follows the same duration rules as the expected-rate
window; `interval_seconds` is the alternative integer representation.
`compare_local` and `compare_observed` are owner-defined references. This draft
does not define a query language for them.
## 5. Extensions and profiles
Generic objects are closed: unknown fields fail schema validation. Additional
profile data belongs in an `extensions` mapping keyed by an owner-controlled
namespace. For example:
```yaml
extensions:
netkingdom:
evidence_class: load-bearing
rate_monitoring: forbidden
```
An extension may narrow use of the generic contract. It must not redefine a
generic field, change the meaning of a form, or make an instance that fails the
generic schema valid.
## 6. Validation semantics
The normative machine contract is
`infospace/schemas/emission-cadence.schema.yaml`.
A conforming generic declaration:
1. validates against that schema;
2. has at least one cadence entry;
3. has unique `source_id` values;
4. uses one duration representation for each window or interval;
5. supplies only expected-rate fields for `expected-rate` entries;
6. supplies heartbeat, reconciliation, or both for
`heartbeat-or-reconciliation` entries; and
7. carries profile-owned data only under a namespaced `extensions` key.
Schema validation establishes declaration shape, not operational truth.
Observers must not infer that a stream is complete merely because its
declaration is valid.
## 7. Compatibility and evolution
The document version and `schema_version` use semantic versioning with the
schema's major and minor represented on the wire.
- Patch releases clarify prose or validation without changing accepted data.
- Minor releases add optional fields or forms. Producers may opt in; consumers
must not silently interpret an unknown form as a known one.
- Major releases may rename, remove, or change field semantics and require an
explicit migration note.
During the `0.x` draft period, incompatible changes remain possible but must be
recorded in the repo changelog and accompanied by migration guidance. A
consumer must reject an unsupported `schema_version`; it must not guess.
## 8. Worked example
`examples/qonto-assistant.yaml` is a schema-valid transformation of the King's
Guard handover example. It demonstrates both forms and the profile-extension
boundary. It is not the source-owned `qonto-assistant` declaration and makes no
claim about live emission or observation.
## 9. Conformance
A producer conforms to this standard when its published declaration validates
against the named schema and accurately identifies the source and event class
it owns. A consumer conforms when it preserves the generic semantics, rejects
unsupported versions and forms, and keeps observation results separate from
the source's declaration.
Profile conformance is additional and is assessed by the profile owner.

View file

@ -0,0 +1,36 @@
# Worked example only. qonto-assistant owns its live declaration; this file
# makes no claim that this cadence is currently emitted or observed.
schema_version: "0.1"
declaration_id: qonto-assistant.audit.example
source: qonto-assistant
stream_id: qonto-assistant.audit
sources:
- source_id: qonto-assistant.audit.allow
event_class: audit.allow
form: expected-rate
window: PT24H
expected_min: 1
drop_below: finding
extensions:
netkingdom:
evidence_class: attributive
completeness_claimed: false
example_only: true
- source_id: qonto-assistant.audit.deny
event_class: audit.deny
form: heartbeat-or-reconciliation
heartbeat:
event_class: audit.heartbeat
interval: PT24H
assertion: nothing-to-report
missing: finding
reconciliation:
compare_local: source_transition_counts.audit.deny
compare_observed: evidence_counts.audit.deny
divergence: finding
undrained_local: lag-not-divergence
extensions:
netkingdom:
evidence_class: load-bearing
rate_monitoring: forbidden
completeness_claimed: true

View file

@ -1,14 +1,496 @@
{
"coverage": {
"artifacts": [
{
"checks": "structural-or-specialized",
"id": "assimilation/emission-cadence",
"kind": "assimilation",
"schema": null
},
{
"checks": "structural-or-specialized",
"id": "assimilation/it-capability-canon",
"kind": "assimilation",
"schema": null
},
{
"checks": "structural-or-specialized",
"id": "benchmark/caring/kubernetes-rbac",
"kind": "benchmark-workspace",
"schema": null
},
{
"checks": "structural-or-specialized",
"id": "benchmark/caring/kubernetes-rbac/access-descriptors",
"kind": "access-descriptor-set",
"schema": null
},
{
"checks": "structural-or-specialized",
"id": "benchmark/caring/kubernetes-rbac/caring-mapping",
"kind": "caring-mapping",
"schema": null
},
{
"checks": "structural-or-specialized",
"id": "benchmark/caring/kubernetes-rbac/findings",
"kind": "benchmark-findings",
"schema": null
},
{
"checks": "structural-or-specialized",
"id": "benchmark/caring/kubernetes-rbac/native-concepts",
"kind": "native-concept-map",
"schema": null
},
{
"checks": "structural-or-specialized",
"id": "capability-catalog/itc-cap",
"kind": "capability-catalog",
"schema": null
},
{
"checks": "structural-or-specialized",
"id": "catalog/attribute-value-types",
"kind": "concept-catalog",
"schema": null
},
{
"checks": "structural-or-specialized",
"id": "catalog/evidence-basis",
"kind": "concept-catalog",
"schema": null
},
{
"checks": "structural-or-specialized",
"id": "comparison/repo-scoping/canon-benefit-analysis",
"kind": "benefit-analysis",
"schema": null
},
{
"checks": "structural-or-specialized",
"id": "comparison/repo-scoping/consumer-workplan-brief",
"kind": "consumer-workplan-brief",
"schema": null
},
{
"checks": "structural-or-specialized",
"id": "comparison/repo-scoping/extension-candidates",
"kind": "extension-candidate-set",
"schema": null
},
{
"checks": "structural-or-specialized",
"id": "comparison/repo-scoping/frame",
"kind": "comparison-frame",
"schema": null
},
{
"checks": "structural-or-specialized",
"id": "comparison/repo-scoping/report",
"kind": "comparison-report",
"schema": null
},
{
"checks": "structural-or-specialized",
"id": "concept-catalog/purpose-demand",
"kind": "concept-catalog",
"schema": null
},
{
"checks": "structural-or-specialized",
"id": "conformance/railiance-fabric",
"kind": "conformance-pack",
"schema": null
},
{
"checks": "structural-or-specialized",
"id": "conformance/railiance-fabric/consumer-workplan-brief",
"kind": "consumer-workplan-brief",
"schema": null
},
{
"checks": "structural-or-specialized",
"id": "conformance/railiance-fabric/entity-edge-capture-criteria",
"kind": "capture-criteria",
"schema": null
},
{
"checks": "structural-or-specialized",
"id": "conformance/railiance-fabric/mapping-expectations",
"kind": "mapping-expectation",
"schema": null
},
{
"checks": "structural-or-specialized",
"id": "conformance/railiance-fabric/visualization-examples",
"kind": "visualization-example-set",
"schema": null
},
{
"checks": "structural-or-specialized",
"id": "evaluation/user-engine",
"kind": "evaluation-pack",
"schema": null
},
{
"checks": "structural-or-specialized",
"id": "evaluation/user-engine/consumer-workplan-brief",
"kind": "consumer-workplan-brief",
"schema": null
},
{
"checks": "structural-or-specialized",
"id": "evaluation/user-engine/interface-card-expectations",
"kind": "interface-card-expectation",
"schema": null
},
{
"checks": "structural-or-specialized",
"id": "evaluation/user-engine/questions",
"kind": "evaluation-question-set",
"schema": null
},
{
"checks": "structural-or-specialized",
"id": "evaluation/user-engine/small-saas-alignment",
"kind": "profile-alignment",
"schema": null
},
{
"checks": "structural-or-specialized",
"id": "example/consumer-purpose-portfolio",
"kind": "example",
"schema": null
},
{
"checks": "structural-or-specialized",
"id": "example/emission-cadence/qonto-assistant",
"kind": "example",
"schema": null
},
{
"checks": "structural-or-specialized",
"id": "kernel/itc-core",
"kind": "kernel",
"schema": null
},
{
"checks": "structural-or-specialized",
"id": "kernel/itc-kernel-map",
"kind": "kernel",
"schema": null
},
{
"checks": "schema-and-references",
"id": "mapping/capability-anchors",
"kind": "mapping",
"schema": "mapping.schema.yaml"
},
{
"checks": "schema-and-references",
"id": "mapping/emission-cadence-handover",
"kind": "mapping",
"schema": "mapping.schema.yaml"
},
{
"checks": "schema-and-references",
"id": "mapping/purpose-demand-governance-candidates",
"kind": "mapping",
"schema": "mapping.schema.yaml"
},
{
"checks": "structural-or-specialized",
"id": "model/access-control",
"kind": "model",
"schema": null
},
{
"checks": "structural-or-specialized",
"id": "model/capability",
"kind": "model",
"schema": null
},
{
"checks": "structural-or-specialized",
"id": "model/data",
"kind": "model",
"schema": null
},
{
"checks": "structural-or-specialized",
"id": "model/devsecops",
"kind": "model",
"schema": null
},
{
"checks": "structural-or-specialized",
"id": "model/governance",
"kind": "model",
"schema": null
},
{
"checks": "structural-or-specialized",
"id": "model/information-space",
"kind": "model",
"schema": null
},
{
"checks": "structural-or-specialized",
"id": "model/landscape",
"kind": "model",
"schema": null
},
{
"checks": "structural-or-specialized",
"id": "model/network",
"kind": "model",
"schema": null
},
{
"checks": "structural-or-specialized",
"id": "model/observability",
"kind": "model",
"schema": null
},
{
"checks": "structural-or-specialized",
"id": "model/organization",
"kind": "model",
"schema": null
},
{
"checks": "structural-or-specialized",
"id": "model/purpose-demand-extension",
"kind": "model-extension",
"schema": null
},
{
"checks": "structural-or-specialized",
"id": "model/security",
"kind": "model",
"schema": null
},
{
"checks": "structural-or-specialized",
"id": "model/task",
"kind": "model",
"schema": null
},
{
"checks": "structural-or-specialized",
"id": "pattern/intent-scope-purposes",
"kind": "pattern",
"schema": null
},
{
"checks": "structural-or-specialized",
"id": "practice-pattern/agentic-drives-functional",
"kind": "practice-pattern",
"schema": null
},
{
"checks": "structural-or-specialized",
"id": "practice-pattern/interface-deprecation-strangler",
"kind": "practice-pattern",
"schema": null
},
{
"checks": "structural-or-specialized",
"id": "practice/intake-and-assimilation",
"kind": "practice",
"schema": null
},
{
"checks": "structural-or-specialized",
"id": "profile/small-saas",
"kind": "profile",
"schema": null
},
{
"checks": "structural-or-specialized",
"id": "review-kit/alignment",
"kind": "alignment-review-kit",
"schema": null
},
{
"checks": "structural-or-specialized",
"id": "review-kit/alignment/model-selection-guide",
"kind": "model-selection-guide",
"schema": null
},
{
"checks": "structural-or-specialized",
"id": "review-kit/alignment/schema",
"kind": "alignment-review-schema",
"schema": null
},
{
"checks": "structural-or-specialized",
"id": "review-kit/alignment/scorecard",
"kind": "alignment-scorecard",
"schema": null
},
{
"checks": "structural-or-specialized",
"id": "review-kit/alignment/workflow",
"kind": "alignment-review-workflow",
"schema": null
},
{
"checks": "structural-or-specialized",
"id": "review-kit/alignment/workplan-template",
"kind": "consumer-workplan-template",
"schema": null
},
{
"checks": "structural-or-specialized",
"id": "scheme/practice-pattern",
"kind": "practice-pattern-scheme",
"schema": null
},
{
"checks": "structural-or-specialized",
"id": "small-saas/capability-requirements/production",
"kind": "profile-artifact",
"schema": null
},
{
"checks": "structural-or-specialized",
"id": "small-saas/control/namespace-per-tenant",
"kind": "profile-artifact",
"schema": null
},
{
"checks": "structural-or-specialized",
"id": "small-saas/dataset/subscription-ledger",
"kind": "profile-artifact",
"schema": null
},
{
"checks": "structural-or-specialized",
"id": "small-saas/deployment/production",
"kind": "profile-artifact",
"schema": null
},
{
"checks": "structural-or-specialized",
"id": "small-saas/evidence/access-review-2026-05",
"kind": "profile-artifact",
"schema": null
},
{
"checks": "structural-or-specialized",
"id": "small-saas/incident/cross-tenant-access-attempt",
"kind": "profile-artifact",
"schema": null
},
{
"checks": "structural-or-specialized",
"id": "small-saas/policy/tenant-isolation",
"kind": "profile-artifact",
"schema": null
},
{
"checks": "structural-or-specialized",
"id": "small-saas/service/billing-portal",
"kind": "profile-artifact",
"schema": null
},
{
"checks": "structural-or-specialized",
"id": "small-saas/system/billing-system",
"kind": "profile-artifact",
"schema": null
},
{
"checks": "structural-or-specialized",
"id": "small-saas/task/onboard-tenant",
"kind": "profile-artifact",
"schema": null
},
{
"checks": "structural-or-specialized",
"id": "small-saas/team/platform",
"kind": "profile-artifact",
"schema": null
},
{
"checks": "structural-or-specialized",
"id": "small-saas/tenant/acme",
"kind": "profile-artifact",
"schema": null
},
{
"checks": "structural-or-specialized",
"id": "small-saas/tenant/globex",
"kind": "profile-artifact",
"schema": null
},
{
"checks": "structural-or-specialized",
"id": "small-saas/user/ada-admin",
"kind": "profile-artifact",
"schema": null
},
{
"checks": "structural-or-specialized",
"id": "standard/caring",
"kind": "standard",
"schema": null
},
{
"checks": "structural-or-specialized",
"id": "standard/emission-cadence",
"kind": "standard",
"schema": null
},
{
"checks": "structural-or-specialized",
"id": "standard/repository-layout",
"kind": "standard",
"schema": null
},
{
"checks": "structural-or-specialized",
"id": "standard/tagging",
"kind": "standard",
"schema": null
}
],
"not_proven": [
"ownership of concepts only in prose",
"all Markdown links",
"consumer adoption",
"cross-version interoperability",
"CARING effective access",
"mapping rationale completeness"
],
"ok": true,
"specialized": [
"capability catalog/record",
"practice pattern",
"emission cadence example",
"consumer packs"
]
},
"details": {
"artifact_count": 71,
"relationship_count": 302
"artifact_count": 76,
"relationship_count": 315
},
"errors": [],
"evidence": {
"corpus_sha256": "466d11ec8825482b370c3afc4cf22b44fe5f48aa14e4babef838a6aa91009148",
"digest_scope": "all infospace files except validation reports",
"dirty": true,
"generated_at": "2026-09-04T22:43:03.604707+00:00",
"revision": "a2e7f22d8deda813b6265f1e06fc75d0a2ccc5ce"
},
"metrics": {
"coherence_components": 1.0,
"consistency_cycles": 0.0,
"coverage_ratio": 1.0,
"granularity_entropy": 4.580874882166957,
"granularity_entropy": 4.582306705233707,
"redundancy_ratio": 0.0
},
"ok": true,

View file

@ -2,10 +2,11 @@
# By Concept
Concept count: **119**
Concept count: **129**
| Concept | Owner | Source |
| --- | --- | --- |
| Assimilation — EmissionCadenceDeclaration handover | `assimilation/emission-cadence` | `artifact_title` |
| Assimilation — IT Capability Canon (ITCC) v0.1 | `assimilation/it-capability-canon` | `artifact_title` |
| CARING Kubernetes RBAC Benchmark | `benchmark/caring/kubernetes-rbac` | `artifact_title` |
| Kubernetes RBAC CARING Access Descriptors | `benchmark/caring/kubernetes-rbac/access-descriptors` | `artifact_title` |
@ -32,9 +33,11 @@ Concept count: **119**
| User Engine Canon Evaluation Questions | `evaluation/user-engine/questions` | `artifact_title` |
| User Engine Small SaaS Alignment Lens | `evaluation/user-engine/small-saas-alignment` | `artifact_title` |
| Canon-Side Consumer Purpose Portfolio | `example/consumer-purpose-portfolio` | `artifact_title` |
| Qonto Assistant Emission Cadence Worked Example | `example/emission-cadence/qonto-assistant` | `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` |
| Emission cadence handover mappings | `mapping/emission-cadence-handover` | `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` |
@ -90,6 +93,7 @@ Concept count: **119**
| PracticePattern Scheme | `scheme/practice-pattern` | `artifact_title` |
| PracticePattern | `scheme/practice-pattern` | `frontmatter.owned_concepts` |
| PatternLanguage | `scheme/practice-pattern` | `frontmatter.owned_concepts` |
| Small SaaS Production Capability Requirements | `small-saas/capability-requirements/production` | `artifact_title` |
| Namespace Per Tenant Control | `small-saas/control/namespace-per-tenant` | `artifact_title` |
| Subscription Ledger Dataset | `small-saas/dataset/subscription-ledger` | `artifact_title` |
| Production Deployment | `small-saas/deployment/production` | `artifact_title` |
@ -119,6 +123,12 @@ Concept count: **119**
| CARINGAnalysisFitnessTest | `standard/caring` | `frontmatter.owned_concepts` |
| CARINGAnalysisProcedure | `standard/caring` | `frontmatter.owned_concepts` |
| CARINGRedesignProcedure | `standard/caring` | `frontmatter.owned_concepts` |
| InfoTechCanon Emission Cadence Standard | `standard/emission-cadence` | `artifact_title` |
| EmissionCadenceDeclaration | `standard/emission-cadence` | `frontmatter.owned_concepts` |
| EmissionCadenceForm | `standard/emission-cadence` | `frontmatter.owned_concepts` |
| ExpectedRateCadence | `standard/emission-cadence` | `frontmatter.owned_concepts` |
| HeartbeatCadence | `standard/emission-cadence` | `frontmatter.owned_concepts` |
| ReconciliationCadence | `standard/emission-cadence` | `frontmatter.owned_concepts` |
| InfoTechCanon Repository Layout Standard | `standard/repository-layout` | `artifact_title` |
| CanonicalRepositoryLayout | `standard/repository-layout` | `frontmatter.owned_concepts` |
| RepositoryDocumentationDirectory | `standard/repository-layout` | `frontmatter.owned_concepts` |

View file

@ -2,6 +2,10 @@
# By Mapping Target
## `assimilation/emission-cadence`
- `standard/emission-cadence` via `derived_from`
## `assimilation/it-capability-canon`
- `model/capability` via `derived_from`
@ -63,6 +67,7 @@
## `kernel/itc-core`
- `assimilation/emission-cadence` via `conforms_to`
- `assimilation/it-capability-canon` via `conforms_to`
- `concept-catalog/purpose-demand` via `conforms_to`
- `kernel/itc-kernel-map` via `maps`
@ -84,6 +89,7 @@
- `review-kit/alignment` via `conforms_to`
- `scheme/practice-pattern` via `conforms_to`
- `standard/caring` via `conforms_to`
- `standard/emission-cadence` via `conforms_to`
- `standard/repository-layout` via `conforms_to`
- `standard/tagging` via `conforms_to`
@ -111,6 +117,7 @@
- `kernel/itc-kernel-map` via `maps`
- `practice-pattern/agentic-drives-functional` via `uses`
- `small-saas/capability-requirements/production` via `uses`
## `model/data`
@ -156,6 +163,7 @@
- `evaluation/user-engine/questions` via `uses`
- `evaluation/user-engine/small-saas-alignment` via `uses`
- `kernel/itc-kernel-map` via `maps`
- `mapping/emission-cadence-handover` via `maps`
- `mapping/purpose-demand-governance-candidates` via `maps`
- `model/access-control` via `uses`
- `model/capability` via `uses`
@ -172,6 +180,7 @@
- `review-kit/alignment/workflow` via `uses`
- `small-saas/policy/tenant-isolation` via `uses`
- `standard/caring` via `imports`
- `standard/emission-cadence` via `imports`
- `standard/repository-layout` via `imports`
## `model/information-space`
@ -215,6 +224,7 @@
- `conformance/railiance-fabric/entity-edge-capture-criteria` via `uses`
- `conformance/railiance-fabric/mapping-expectations` via `maps`
- `kernel/itc-kernel-map` via `maps`
- `mapping/emission-cadence-handover` via `maps`
- `model/capability` via `uses`
- `practice-pattern/agentic-drives-functional` via `uses`
- `practice-pattern/interface-deprecation-strangler` via `uses`
@ -222,6 +232,7 @@
- `review-kit/alignment/model-selection-guide` via `uses`
- `small-saas/evidence/access-review-2026-05` via `uses`
- `standard/caring` via `imports`
- `standard/emission-cadence` via `imports`
## `model/organization`
@ -281,6 +292,7 @@
- `small-saas/control/namespace-per-tenant` via `uses`
- `small-saas/incident/cross-tenant-access-attempt` via `uses`
- `standard/caring` via `imports`
- `standard/emission-cadence` via `related_to`
## `model/task`
@ -325,6 +337,7 @@
- `evaluation/user-engine/small-saas-alignment` via `evaluates`
- `example/consumer-purpose-portfolio` via `uses`
- `review-kit/alignment/model-selection-guide` via `uses`
- `small-saas/capability-requirements/production` via `instantiates`
- `small-saas/control/namespace-per-tenant` via `instantiates`
- `small-saas/dataset/subscription-ledger` via `instantiates`
- `small-saas/deployment/production` via `instantiates`
@ -375,6 +388,7 @@
## `small-saas/service/billing-portal`
- `small-saas/capability-requirements/production` via `applies_to`
- `small-saas/dataset/subscription-ledger` via `owned_by`
- `small-saas/deployment/production` via `deploys`
@ -420,6 +434,11 @@
- `review-kit/alignment/model-selection-guide` via `uses`
- `small-saas/control/namespace-per-tenant` via `uses`
## `standard/emission-cadence`
- `example/emission-cadence/qonto-assistant` via `conforms_to`
- `mapping/emission-cadence-handover` via `maps`
## `standard/tagging`
- `benchmark/caring/kubernetes-rbac` via `uses`

View file

@ -23,6 +23,13 @@
- Path: `standards/caring/InfoTechCanonCaringAccessGovernanceStandard.md`
- Relationships: 11
## InfoTechCanon Emission Cadence Standard
- ID: `standard/emission-cadence`
- Kind: `standard`
- Path: `standards/emission-cadence/InfoTechCanonEmissionCadenceStandard.md`
- Relationships: 5
## InfoTechCanon Repository Layout Standard
- ID: `standard/repository-layout`

View file

@ -2,76 +2,81 @@
# 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/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-pattern/agentic-drives-functional` | `practice-pattern/interface-deprecation-strangler` | `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` | `scheme/practice-pattern` | `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-pattern/agentic-drives-functional` | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | `uses` | | | `uses` | | | | `uses` | | | | `uses` | | | `related_to` | | | | | | | | | `conforms_to` | | | | | | | | | | | | | | | | |
| `practice-pattern/interface-deprecation-strangler` | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | `uses` | `uses` | | | | `uses` | | | | | | | | | | | | | | | | `conforms_to` | | | | | | | | | | | | | | | | |
| `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` | | | | | | | | | | | | | | | | | | | | | | |
| `scheme/practice-pattern` | | | | | | | | | | | | | | | | | | | | | | | | | | | `conforms_to` | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
| `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/emission-cadence` | `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` | `example/emission-cadence/qonto-assistant` | `kernel/itc-core` | `kernel/itc-kernel-map` | `mapping/capability-anchors` | `mapping/emission-cadence-handover` | `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-pattern/agentic-drives-functional` | `practice-pattern/interface-deprecation-strangler` | `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` | `scheme/practice-pattern` | `small-saas/capability-requirements/production` | `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/emission-cadence` | `standard/repository-layout` | `standard/tagging` |
| --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- |
| `assimilation/emission-cadence` | | | | | | | | | | | | | | | | | | | | | | | | | | | | | `conforms_to` | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
| `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` | | | | | | | | | | | | | | | | | | | | | | | | | |
| `example/emission-cadence/qonto-assistant` | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | `conforms_to` | | |
| `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/emission-cadence-handover` | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | `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` | | `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-pattern/agentic-drives-functional` | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | `uses` | | | `uses` | | | | `uses` | | | | `uses` | | | `related_to` | | | | | | | | | `conforms_to` | | | | | | | | | | | | | | | | | | |
| `practice-pattern/interface-deprecation-strangler` | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | `uses` | `uses` | | | | `uses` | | | | | | | | | | | | | | | | `conforms_to` | | | | | | | | | | | | | | | | | | |
| `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` | | | | | | | | | | | | | | | | | | | | | | | | |
| `scheme/practice-pattern` | | | | | | | | | | | | | | | | | | | | | | | | | | | | | `conforms_to` | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
| `small-saas/capability-requirements/production` | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | `uses` | | | | | | | | | | | | | | | | `instantiates` | | | | | | | | | | | | | | | `applies_to` | | | | | | | | | | |
| `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/emission-cadence` | `derived_from` | | | | | | | | | | | | | | | | | | | | | | | | | | | | `conforms_to` | | | | | | | | | `imports` | | | | `imports` | | | `related_to` | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
| `standard/repository-layout` | | | | | | | | | | | | | | | | | | | | | | | | | | | | | `conforms_to` | | | | | | | | | `imports` | `imports` | | | | | | | `imports` | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
| `standard/tagging` | | | | | | | | | | | | | | | | | | | | | | | | | | | | | `conforms_to` | | | | | | | | | | | | | | | | | `imports` | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |

View file

@ -3,7 +3,7 @@
# Kernel Overview
- Infospace: `canon`
- Artifacts: 71
- Artifacts: 76
## Artifact Kinds
@ -12,7 +12,7 @@
- `alignment-review-schema`: 1
- `alignment-review-workflow`: 1
- `alignment-scorecard`: 1
- `assimilation`: 1
- `assimilation`: 2
- `benchmark-findings`: 1
- `benchmark-workspace`: 1
- `benefit-analysis`: 1
@ -27,11 +27,11 @@
- `consumer-workplan-template`: 1
- `evaluation-pack`: 1
- `evaluation-question-set`: 1
- `example`: 1
- `example`: 2
- `extension-candidate-set`: 1
- `interface-card-expectation`: 1
- `kernel`: 2
- `mapping`: 2
- `mapping`: 3
- `mapping-expectation`: 1
- `model`: 12
- `model-extension`: 1
@ -43,19 +43,20 @@
- `practice-pattern-scheme`: 1
- `profile`: 1
- `profile-alignment`: 1
- `profile-artifact`: 13
- `standard`: 3
- `profile-artifact`: 14
- `standard`: 4
- `visualization-example-set`: 1
## Relationship Types
- `access_evidenced_by`: 1
- `applies_to`: 1
- `changes`: 1
- `compares`: 1
- `conforms_to`: 25
- `conforms_to`: 28
- `constrained_by`: 1
- `deploys`: 1
- `derived_from`: 1
- `derived_from`: 2
- `evaluates`: 2
- `evidenced_by`: 3
- `extends`: 1
@ -63,20 +64,20 @@
- `has_access_under`: 1
- `illustrates`: 4
- `implements`: 2
- `imports`: 14
- `instantiates`: 13
- `imports`: 16
- `instantiates`: 14
- `introduces`: 5
- `isolated_by`: 2
- `maps`: 37
- `maps`: 40
- `member_of`: 1
- `owned_by`: 3
- `part_of`: 22
- `partitioned_for`: 2
- `proposes`: 7
- `related_to`: 1
- `related_to`: 2
- `represented_by`: 1
- `requires`: 13
- `separates`: 2
- `serves`: 2
- `stress_tests`: 6
- `uses`: 125
- `uses`: 126

View file

@ -2,7 +2,7 @@
# Repository Tree
File count: **191**
File count: **208**
- `README.md`
- `agent/README.md`
@ -30,9 +30,11 @@ File count: **191**
- `agent/briefs/evaluation-user-engine-small-saas-alignment.md`
- `agent/briefs/evaluation-user-engine.md`
- `agent/briefs/example-consumer-purpose-portfolio.md`
- `agent/briefs/example-emission-cadence-qonto-assistant.md`
- `agent/briefs/kernel-itc-core.md`
- `agent/briefs/kernel-itc-kernel-map.md`
- `agent/briefs/mapping-capability-anchors.md`
- `agent/briefs/mapping-emission-cadence-handover.md`
- `agent/briefs/mapping-purpose-demand-governance-candidates.md`
- `agent/briefs/model-access-control.md`
- `agent/briefs/model-capability.md`
@ -48,6 +50,7 @@ File count: **191**
- `agent/briefs/model-security.md`
- `agent/briefs/model-task.md`
- `agent/briefs/pattern-intent-scope-purposes.md`
- `agent/briefs/practice-pattern-agentic-drives-functional.md`
- `agent/briefs/practice-pattern-interface-deprecation-strangler.md`
- `agent/briefs/profile-small-saas.md`
- `agent/briefs/review-kit-alignment-model-selection-guide.md`
@ -58,6 +61,7 @@ File count: **191**
- `agent/briefs/review-kit-alignment.md`
- `agent/briefs/scheme-practice-pattern.md`
- `agent/briefs/standard-caring.md`
- `agent/briefs/standard-emission-cadence.md`
- `agent/briefs/standard-repository-layout.md`
- `agent/briefs/standard-tagging.md`
- `agent/consumer-briefs/railiance-fabric.md`
@ -76,6 +80,15 @@ File count: **191**
- `agent/templates/consumer-brief.template.md`
- `artifacts/index.yaml`
- `assimilation/README.md`
- `assimilation/emission-cadence/ASSIMILATION.md`
- `assimilation/emission-cadence/assimilation.yaml`
- `assimilation/emission-cadence/comparison-matrix.md`
- `assimilation/emission-cadence/extracted-concepts.yaml`
- `assimilation/emission-cadence/mappings.yaml`
- `assimilation/emission-cadence/open-questions.md`
- `assimilation/emission-cadence/proposed-changes.md`
- `assimilation/emission-cadence/source/EmissionCadenceDeclaration.md`
- `assimilation/emission-cadence/source-summary.md`
- `assimilation/intake-and-assimilation-practice.md`
- `assimilation/it-capability-canon/ASSIMILATION.md`
- `assimilation/it-capability-canon/assimilation.yaml`
@ -145,6 +158,7 @@ File count: **191**
- `patterns/README.md`
- `patterns/intent-scope-purposes.md`
- `profiles/README.md`
- `profiles/small-saas/artifacts/capability-requirements.yaml`
- `profiles/small-saas/artifacts/control.namespace-per-tenant.yaml`
- `profiles/small-saas/artifacts/dataset.subscription-ledger.yaml`
- `profiles/small-saas/artifacts/deployment.production.yaml`
@ -169,6 +183,7 @@ File count: **191**
- `schemas/capability-record.schema.yaml`
- `schemas/capability.schema.yaml`
- `schemas/concept.schema.yaml`
- `schemas/emission-cadence.schema.yaml`
- `schemas/index.yaml`
- `schemas/interface-card.schema.yaml`
- `schemas/mapping.schema.yaml`
@ -183,6 +198,8 @@ File count: **191**
- `standards/caring/benchmarks/kubernetes-rbac/caring-mapping.yaml`
- `standards/caring/benchmarks/kubernetes-rbac/findings-and-canon-pressure.yaml`
- `standards/caring/benchmarks/kubernetes-rbac/native-concepts.yaml`
- `standards/emission-cadence/InfoTechCanonEmissionCadenceStandard.md`
- `standards/emission-cadence/examples/qonto-assistant.yaml`
- `standards/repository-layout/InfoTechCanonRepositoryLayoutStandard.md`
- `standards/tagging/InfoTechCanonTaggingStandard.md`
- `validation/README.md`