info-tech-canon/canon.yaml
tegwick 5a1ea90f64 Dispose OrwellLoggingDiagnostics as adapt (INFO-DEC-2026-003)
The canon owner disposed coordination-engine's candidate practice pattern as
adapt, which unblocks COORDINATION-WP-0004-T01. Preserve the source, record
the DecisionRecord, and register the assimilation. The TAMQ known use is
implemented and tested, so the pattern enters at candidate. Canon placement
is planned as proposed workplan INFO-WP-0030.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 121421@bnt-lap001
Assistant-Session: 36f8657c-ebfa-4a2e-9ba0-bff06738f233
2026-09-22 16:21:37 +02:00

236 lines
7 KiB
YAML

repository: info-tech-canon
title: InfoTechCanon
status: service-baseline
version: 0.12.0
description: >
An evolving, markdown-first canon for building interoperable, adaptable,
and extensible information-processing systems.
layout:
current_seed_root: seeds/
target_infospace_root: infospace/
layout_family: kernel-models-standards
notes:
- The repository implements one infospace under infospace/.
- The repository root remains the service and workplan shell.
- Seed files remain provenance until scaffold migration is reviewed.
service_surface:
implemented:
- cli
- json
- api
implementation_basis:
- infospace-bench
package: info_tech_canon
cli_module: info_tech_canon.cli
api_module: info_tech_canon.api
classification:
kernel:
description: Defines how the canon is organized and evolved.
models:
description: Define broad domain structures.
standards:
description: Define cross-cutting conventions or named analytical/design frameworks.
kernel:
- id: itc-core
title: InfoTechCanonCore
path: infospace/kernel/InfoTechCanonCore.md
status: RC1-seed
- id: itc-kernel-map
title: InfoTechCanonKernelMap
path: infospace/kernel/InfoTechCanonKernelMap.md
status: RC1-kernel-map
models:
- id: itc-infospace
title: InfoTechCanonInformationSpaceModel
path: infospace/models/information-space/InfoTechCanonInformationSpaceModel.md
status: RC1-seed
- id: itc-land
title: InfoTechCanonLandscapeModel
path: infospace/models/landscape/InfoTechCanonLandscapeModel.md
status: RC1-seed
- id: itc-org
title: InfoTechCanonOrganizationModel
path: infospace/models/organization/InfoTechCanonOrganizationModel.md
status: RC1-seed
- id: itc-gov
title: InfoTechCanonGovernanceModel
path: infospace/models/governance/InfoTechCanonGovernanceModel.md
status: RC1-seed
- id: itc-ident
title: InfoTechCanonIdentityModel
path: infospace/models/identity/InfoTechCanonIdentityModel.md
status: draft
version: 0.1.0
- id: itc-evid
title: InfoTechCanonEvidenceModel
path: infospace/models/evidence/InfoTechCanonEvidenceModel.md
status: draft
version: 0.1.0
- id: itc-task
title: InfoTechCanonTaskModel
path: infospace/models/task/InfoTechCanonTaskModel.md
status: RC1-seed
- id: itc-access
title: InfoTechCanonAccessControlModel
path: infospace/models/access-control/InfoTechCanonAccessControlModel.md
status: RC1-seed
- id: itc-sec
title: InfoTechCanonSecurityModel
path: infospace/models/security/InfoTechCanonSecurityModel.md
status: RC1-seed
- id: itc-data
title: InfoTechCanonDataModel
path: infospace/models/data/InfoTechCanonDataModel.md
status: RC1-seed
- id: itc-devsecops
title: InfoTechCanonDevSecOpsModel
path: infospace/models/devsecops/InfoTechCanonDevSecOpsModel.md
status: RC1-seed
- id: itc-net
title: InfoTechCanonNetworkModel
path: infospace/models/network/InfoTechCanonNetworkModel.md
status: RC1-seed
- id: itc-obs
title: InfoTechCanonObservabilityModel
path: infospace/models/observability/InfoTechCanonObservabilityModel.md
status: RC1-seed
- id: itc-cap
title: InfoTechCanonCapabilityModel
path: infospace/models/capability/InfoTechCanonCapabilityModel.md
status: draft
version: 0.4.0
catalog: infospace/models/capability/capabilities.yaml
provenance:
assimilation: assimilation/it-capability-canon
source_body: Information Technology Capability Canon (ITCC)
source_version: "0.1"
disposition: adapt
concept_areas:
- id: family-area
title: Family concept-area seed
path: infospace/concepts/family/FamilySeed.md
status: seed
content_status: seeded-not-authored
standards:
- id: itc-tag
title: InfoTechCanonTaggingStandard
path: infospace/standards/tagging/InfoTechCanonTaggingStandard.md
status: RC1-seed
- id: itc-caring
title: InfoTechCanonCaringAccessGovernanceStandard
path: infospace/standards/caring/InfoTechCanonCaringAccessGovernanceStandard.md
status: 0.4.0-RC2-aligned
- id: itc-repo-layout
title: InfoTechCanonRepositoryLayoutStandard
path: infospace/standards/repository-layout/InfoTechCanonRepositoryLayoutStandard.md
status: RC1-seed
- id: itc-emission-cadence
title: InfoTechCanonEmissionCadenceStandard
path: infospace/standards/emission-cadence/InfoTechCanonEmissionCadenceStandard.md
status: draft
version: 0.1.0
schema: infospace/schemas/emission-cadence.schema.yaml
provenance:
assimilation: assimilation/emission-cadence
source_body: King's Guard EmissionCadenceDeclaration handover
source_version: 0.1.0
disposition: adapt
planned_directories:
- infospace/
- infospace/profiles/
- infospace/patterns/
- infospace/mappings/
- infospace/assimilation/
- infospace/schemas/
- infospace/views/
- infospace/indexes/
- infospace/agent/
- infospace/examples/
- infospace/validation/
- workplans/
- demand/
- incoming/
- feedback/
workplans:
registry: workplans/index.yaml
planned:
- ITC-WP-0001
- ITC-WP-0002
- ITC-WP-0003
- ITC-WP-0004
- ITC-WP-0005
- ITC-WP-0006
- ITC-WP-0007
- ITC-WP-0008
- ITC-WP-0009
- ITC-WP-0010
- ITC-WP-0011
- ITC-WP-0012
- ITC-WP-0013
- ITC-WP-0014
- ITC-WP-0015
- ITC-WP-0016
- ITC-WP-0017
- ITC-WP-0018
feedback:
path: feedback/
index: feedback/index.yaml
practice: feedback/README.md
template: feedback/TEMPLATE.md
assimilation:
practice: infospace/assimilation/intake-and-assimilation-practice.md
intake_dir: incoming/
records:
- id: assimilation/canon-federation
source: Completed identity-canon research corpus
disposition: observe
status: closed
path: infospace/assimilation/canon-federation/
- id: assimilation/it-capability-canon
source: Information Technology Capability Canon (ITCC) v0.1
disposition: adapt
status: closed
produced: itc-cap
- id: assimilation/emission-cadence
source: King's Guard EmissionCadenceDeclaration draft 0.1.0
disposition: adapt
status: closed
produced: itc-emission-cadence
- id: assimilation/orwell-logging-diagnostics
source: coordination-engine OrwellLoggingDiagnostics candidate
disposition: adapt
status: decided
path: infospace/assimilation/orwell-logging-diagnostics/
workplan: INFO-WP-0030
first_proofs:
near_term:
- small-saas
downstream_consumers:
- user-engine
- railiance-fabric
- repo-scoping
distinct_later_benchmarks:
- caring-kubernetes-rbac
next_actions:
- keep ITC-CAP 0.4.0 frozen; do not change its shape without a new minor
- collect two independent EmissionCadenceDeclaration source implementations
before promoting ITC-EMISSION-CADENCE beyond draft
interface_cards:
- id: info-tech-canon/federation-interface
path: infospace/interfaces/federation.yaml
status: published
version: 0.1.0