tegwick
28d5824362
Define the intake and assimilation practice (incoming/ drop zone -> frozen source snapshot -> Minimal Assimilation Profile -> disposition gate -> canon transformation -> versioned change notes) and run it on the first inputs. - infospace/assimilation/intake-and-assimilation-practice.md, incoming/README.md - assimilation/it-capability-canon: frozen source, comparison matrix, 26 mappings, 8 proposed changes, 7 open questions, decision record (adapt) - new model ITC-CAP with 41-capability machine-readable catalog, anchored to owning canon models; CILM rejected, Profile renamed, Provision made explicit - registered in canon.yaml / artifacts index / infospace.yaml; regenerated briefs, indexes, views; canon version 0.1.0-scaffold -> 0.2.0 + CHANGELOG - ITC-WP-0014 for promotion work; ITC-WP-0013 added to the workplan registry make validate: ok (65 artifacts, 0 errors/warnings). make test: 22 passed. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
173 lines
5 KiB
YAML
173 lines
5 KiB
YAML
repository: info-tech-canon
|
|
title: InfoTechCanon
|
|
status: service-baseline
|
|
version: 0.2.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-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: proposed
|
|
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
|
|
|
|
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
|
|
|
|
planned_directories:
|
|
- infospace/
|
|
- infospace/profiles/
|
|
- infospace/patterns/
|
|
- infospace/mappings/
|
|
- infospace/assimilation/
|
|
- infospace/schemas/
|
|
- infospace/views/
|
|
- infospace/indexes/
|
|
- infospace/agent/
|
|
- infospace/examples/
|
|
- infospace/validation/
|
|
- workplans/
|
|
|
|
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
|
|
|
|
assimilation:
|
|
practice: infospace/assimilation/intake-and-assimilation-practice.md
|
|
intake_dir: incoming/
|
|
records:
|
|
- id: assimilation/it-capability-canon
|
|
source: Information Technology Capability Canon (ITCC) v0.1
|
|
disposition: adapt
|
|
status: closed
|
|
produced: itc-cap
|
|
|
|
first_proofs:
|
|
near_term:
|
|
- small-saas
|
|
downstream_consumers:
|
|
- user-engine
|
|
- railiance-fabric
|
|
- repo-scoping
|
|
distinct_later_benchmarks:
|
|
- caring-kubernetes-rbac
|
|
|
|
next_actions:
|
|
- implement ITC-WP-0003 validation and generated views
|
|
- implement ITC-WP-0004 small-saas profile proof
|
|
- explore ITC-WP-0006 PURPOSES model extension
|
|
- resolve ITC-WP-0014 T01 capability identifier prefix (blocks ITC-CAP promotion)
|