coulomb/info-tech-canon
2
0
Fork 0
generated from coulomb/repo-seed
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Register State Hub workplan IDs

Browse Source
This commit is contained in:
Bernd Worsch
2026-05-23 02:51:52 +02:00
parent 0ed55d8b37
commit df6238c7e0
11 changed files with 112 additions and 79 deletions
Download Patch File Download Diff File Expand all files Collapse all files

17
workplans/ITC-WP-0001-infospace-scaffold-and-seed-placement.md
View File

@@ -2,12 +2,14 @@
id: ITC-WP-0001
type: workplan
title: "Infospace Scaffold And Seed Placement"
domain: canon
repo: info-tech-canon
status: planned
status: proposed
priority: high
created: "2026-05-23"
updated: "2026-05-23"
depends_on_workplans: []
state_hub_workstream_id: "609380c7-fcc7-40ef-bb23-cdca80b4ce0a"
---
# ITC-WP-0001 - Infospace Scaffold And Seed Placement
@@ -49,8 +51,9 @@ infospace/
```task
id: ITC-WP-0001-T01
status: planned
status: todo
priority: high
state_hub_task_id: "3a7b29ba-bc15-4ca1-ba61-ec4ffaefa2a1"
```
- Create `infospace/` as the single canon infospace root.
@@ -61,8 +64,9 @@ priority: high
```task
id: ITC-WP-0001-T02
status: planned
status: todo
priority: high
state_hub_task_id: "b5894ec2-e79e-4308-9125-fd10c4b76faf"
```
- Place Core and Kernel Map under `infospace/kernel/`.
@@ -75,8 +79,9 @@ priority: high
```task
id: ITC-WP-0001-T03
status: planned
status: todo
priority: high
state_hub_task_id: "4826fbad-3dc7-4759-b086-8cb3cf50f6ff"
```
- Update `canon.yaml` to point at `infospace/...` paths.
@@ -89,8 +94,9 @@ priority: high
```task
id: ITC-WP-0001-T04
status: planned
status: todo
priority: medium
state_hub_task_id: "ff5bae40-9e89-4ec7-9f96-6670e140f4fa"
```
- Record each artifact's seed source path.
@@ -104,4 +110,3 @@ priority: medium
- The seed documents are available under the newer `kernel/models/standards`
layout.
- Original seed provenance remains traceable.

17
workplans/ITC-WP-0002-service-surface-cli-json-api.md
View File

@@ -2,13 +2,15 @@
id: ITC-WP-0002
type: workplan
title: "Service Surface Baseline CLI JSON API"
domain: canon
repo: info-tech-canon
status: planned
status: proposed
priority: high
created: "2026-05-23"
updated: "2026-05-23"
depends_on_workplans:
- ITC-WP-0001
state_hub_workstream_id: "b467e4da-6ce4-4608-a446-319427954b32"
---
# ITC-WP-0002 - Service Surface Baseline CLI JSON API
@@ -30,8 +32,9 @@ usable by downstream agents and tools.
```task
id: ITC-WP-0002-T01
status: planned
status: todo
priority: high
state_hub_task_id: "0d843b8f-0bba-4bd8-8879-5641d2b50848"
```
- Add a minimal Python package for InfoTechCanon service code.
@@ -43,8 +46,9 @@ priority: high
```task
id: ITC-WP-0002-T02
status: planned
status: todo
priority: high
state_hub_task_id: "030955d2-e6af-48d8-a617-943cf4f10628"
```
- Add commands that return JSON by default:
@@ -61,8 +65,9 @@ priority: high
```task
id: ITC-WP-0002-T03
status: planned
status: todo
priority: high
state_hub_task_id: "a926fa1d-7dc0-4450-84c9-c0d49b3744ea"
```
- Wrap infospace loading, artifact listing, validation, metrics, and graph
@@ -73,8 +78,9 @@ priority: high
```task
id: ITC-WP-0002-T04
status: planned
status: todo
priority: high
state_hub_task_id: "070ef996-cf45-47ed-b9d8-1e313c9b0e22"
```
- Add a minimal local API for read-only canon inspection.
@@ -94,4 +100,3 @@ priority: high
- Commands can inspect the `infospace/` root.
- API and CLI outputs share the same service-layer contracts.
- Tests cover the first happy paths and structured failures.

20
workplans/ITC-WP-0003-validation-indexes-and-generated-views.md
View File

@@ -2,14 +2,16 @@
id: ITC-WP-0003
type: workplan
title: "Validation Indexes And Generated Views"
domain: canon
repo: info-tech-canon
status: planned
status: proposed
priority: high
created: "2026-05-23"
updated: "2026-05-23"
depends_on_workplans:
- ITC-WP-0001
- ITC-WP-0002
state_hub_workstream_id: "510e6d15-ac2a-48ee-9ef1-3d14c21e16aa"
---
# ITC-WP-0003 - Validation Indexes And Generated Views
@@ -31,8 +33,9 @@ inconsistencies should fail visibly.
```task
id: ITC-WP-0003-T01
status: planned
status: todo
priority: high
state_hub_task_id: "246d5671-9585-43e1-880c-cc4ce728459f"
```
- Add `make validate`.
@@ -44,8 +47,9 @@ priority: high
```task
id: ITC-WP-0003-T02
status: planned
status: todo
priority: high
state_hub_task_id: "8db6058f-754f-4d92-a93f-d4119b2cad55"
```
- Check required top-level files.
@@ -58,8 +62,9 @@ priority: high
```task
id: ITC-WP-0003-T03
status: planned
status: todo
priority: high
state_hub_task_id: "ea3c6e98-fb3c-44fd-9f54-9a934ab62455"
```
- Add minimal schemas for:
@@ -76,8 +81,9 @@ priority: high
```task
id: ITC-WP-0003-T04
status: planned
status: todo
priority: high
state_hub_task_id: "b33bbda7-8ec6-48b2-a637-571a87473c5a"
```
- Generate `views/by-standard.md`.
@@ -91,8 +97,9 @@ priority: high
```task
id: ITC-WP-0003-T05
status: planned
status: todo
priority: medium
state_hub_task_id: "01469609-91fb-48e3-b6e5-11e6342b29af"
```
- Create a first concept ownership index.
@@ -106,4 +113,3 @@ priority: medium
- Validation produces machine-readable output.
- Generated views can be refreshed deterministically.
- Concept ownership can be inspected even before all concept pages exist.

17
workplans/ITC-WP-0004-small-saas-profile-proof.md
View File

@@ -2,8 +2,9 @@
id: ITC-WP-0004
type: workplan
title: "Small SaaS Profile Proof"
domain: canon
repo: info-tech-canon
status: planned
status: proposed
priority: high
created: "2026-05-23"
updated: "2026-05-23"
@@ -11,6 +12,7 @@ depends_on_workplans:
- ITC-WP-0001
- ITC-WP-0002
- ITC-WP-0003
state_hub_workstream_id: "b531a077-ccc1-4aff-bbd3-a5ee3daf8661"
---
# ITC-WP-0004 - Small SaaS Profile Proof
@@ -33,8 +35,9 @@ governance, observability, and work tracking.
```task
id: ITC-WP-0004-T01
status: planned
status: todo
priority: high
state_hub_task_id: "21801d10-2ec9-45b9-bb7a-632f251075d5"
```
- Create `infospace/profiles/small-saas/`.
@@ -45,8 +48,9 @@ priority: high
```task
id: ITC-WP-0004-T02
status: planned
status: todo
priority: high
state_hub_task_id: "92c860ca-174d-4d31-b11c-66750a2d3588"
```
- Add example service, system, tenant, user, team, dataset, deployment,
@@ -58,8 +62,9 @@ priority: high
```task
id: ITC-WP-0004-T03
status: planned
status: todo
priority: high
state_hub_task_id: "b342257f-beef-4ec6-b116-b9f8798df10c"
```
- Define required fields and links for small SaaS artifacts.
@@ -72,8 +77,9 @@ priority: high
```task
id: ITC-WP-0004-T04
status: planned
status: todo
priority: medium
state_hub_task_id: "58a85249-be34-497d-a19c-96b6b343b076"
```
- Add a profile report under `infospace/reports/`.
@@ -87,4 +93,3 @@ priority: medium
- The proof produces useful graph and JSON outputs.
- The result is suitable as the baseline for user-engine and railiance-fabric
evaluation.

17
workplans/ITC-WP-0005-retrieval-agent-briefs-and-interface-cards.md
View File

@@ -2,14 +2,16 @@
id: ITC-WP-0005
type: workplan
title: "Retrieval Agent Briefs And Interface Cards"
domain: canon
repo: info-tech-canon
status: planned
status: proposed
priority: medium
created: "2026-05-23"
updated: "2026-05-23"
depends_on_workplans:
- ITC-WP-0003
- ITC-WP-0004
state_hub_workstream_id: "1dc61e3a-7451-42ac-bba7-1c6fa30c826c"
---
# ITC-WP-0005 - Retrieval Agent Briefs And Interface Cards
@@ -31,8 +33,9 @@ AccessRole vs CARING role, Policy vs Control vs Evidence, and similar rules.
```task
id: ITC-WP-0005-T01
status: planned
status: todo
priority: high
state_hub_task_id: "3e509e68-2f6d-43fb-a4da-a0289f38960c"
```
- Place the global agent brief under `infospace/agent/`.
@@ -43,8 +46,9 @@ priority: high
```task
id: ITC-WP-0005-T02
status: planned
status: todo
priority: high
state_hub_task_id: "12f350a2-d6d2-402e-820a-5ef86478a562"
```
- Generate `infospace/agent/retrieval-index.md` and a JSON/YAML equivalent.
@@ -55,8 +59,9 @@ priority: high
```task
id: ITC-WP-0005-T03
status: planned
status: todo
priority: medium
state_hub_task_id: "12c17aeb-1da2-4a6f-b71d-cc8614a53394"
```
- Define a Canon Interface Card template.
@@ -67,8 +72,9 @@ priority: medium
```task
id: ITC-WP-0005-T04
status: planned
status: todo
priority: medium
state_hub_task_id: "c504ffe6-1a4c-4ce6-85b4-4c455edaa461"
```
- Create brief templates for user-engine, railiance-fabric, and repo-scoping.
@@ -79,4 +85,3 @@ priority: medium
- Agents can start from compact briefs and retrieve full standards when needed.
- Interface Card templates are ready for first consumers.
- The retrieval index is generated and validated.

17
workplans/ITC-WP-0006-purpose-and-demand-model.md
View File

@@ -2,13 +2,15 @@
id: ITC-WP-0006
type: workplan
title: "Purpose And Demand Model Extension"
domain: canon
repo: info-tech-canon
status: planned
status: proposed
priority: high
created: "2026-05-23"
updated: "2026-05-23"
depends_on_workplans:
- ITC-WP-0003
state_hub_workstream_id: "71fba9d5-f34f-427b-9da1-01990ab04e4d"
---
# ITC-WP-0006 - Purpose And Demand Model Extension
@@ -45,8 +47,9 @@ PURPOSES
```task
id: ITC-WP-0006-T01
status: planned
status: todo
priority: high
state_hub_task_id: "654ce87f-2967-4998-8528-3ec6db31ff1c"
```
- Define candidate concepts:
@@ -65,8 +68,9 @@ priority: high
```task
id: ITC-WP-0006-T02
status: planned
status: todo
priority: high
state_hub_task_id: "9fb752da-3daa-4f7b-96d4-3887673e68c2"
```
- Create a pattern explaining how producer intent, current scope, and consumer
@@ -78,8 +82,9 @@ priority: high
```task
id: ITC-WP-0006-T03
status: planned
status: todo
priority: high
state_hub_task_id: "f2ec2951-fe90-48c6-acf2-35e0b7183513"
```
- Determine which purpose concepts belong in the Governance Model.
@@ -91,8 +96,9 @@ priority: high
```task
id: ITC-WP-0006-T04
status: planned
status: todo
priority: medium
state_hub_task_id: "5cfd80ee-3b04-4389-862b-d7913e953076"
```
- Add examples for user-engine, railiance-fabric, and repo-scoping as
@@ -104,4 +110,3 @@ priority: medium
- PURPOSES is defined enough to use in the first consumer evaluations.
- The relation between INTENT, SCOPE, and PURPOSES is explicit.
- Governance model extension candidates are documented for review.

17
workplans/ITC-WP-0007-user-engine-evaluation-readiness.md
View File

@@ -2,8 +2,9 @@
id: ITC-WP-0007
type: workplan
title: "User Engine Evaluation Readiness"
domain: canon
repo: info-tech-canon
status: planned
status: proposed
priority: high
created: "2026-05-23"
updated: "2026-05-23"
@@ -11,6 +12,7 @@ depends_on_workplans:
- ITC-WP-0004
- ITC-WP-0005
- ITC-WP-0006
state_hub_workstream_id: "72e168f7-35b2-459a-86e6-93f05206f6c2"
---
# ITC-WP-0007 - User Engine Evaluation Readiness
@@ -33,8 +35,9 @@ governance expectations, and integration boundaries.
```task
id: ITC-WP-0007-T01
status: planned
status: todo
priority: high
state_hub_task_id: "17d5792f-7452-4179-b346-f8c976fbe2eb"
```
- Create a canon-side question set for user-management capability evaluation.
@@ -45,8 +48,9 @@ priority: high
```task
id: ITC-WP-0007-T02
status: planned
status: todo
priority: high
state_hub_task_id: "d44c6608-14d8-44cc-80a8-9959296da286"
```
- Define expected Canon Interface Card fields for user-engine.
@@ -57,8 +61,9 @@ priority: high
```task
id: ITC-WP-0007-T03
status: planned
status: todo
priority: medium
state_hub_task_id: "fa1e3da2-1990-4945-8d53-140ad4bedcbf"
```
- Use the small SaaS profile as the concrete evaluation lens.
@@ -68,8 +73,9 @@ priority: medium
```task
id: ITC-WP-0007-T04
status: planned
status: todo
priority: medium
state_hub_task_id: "ffcd728f-b5eb-4449-945b-1a3f8a9640de"
```
- Produce a brief that can be copied into a user-engine workplan.
@@ -85,4 +91,3 @@ priority: medium
- InfoTechCanon can evaluate user-engine before integration work begins.
- The evaluation pack is machine-readable enough for CLI/API use.
- A consumer workplan brief exists for user-engine.

17
workplans/ITC-WP-0008-railiance-fabric-conformance-support.md
View File

@@ -2,8 +2,9 @@
id: ITC-WP-0008
type: workplan
title: "Railiance Fabric Conformance Support"
domain: canon
repo: info-tech-canon
status: planned
status: proposed
priority: high
created: "2026-05-23"
updated: "2026-05-23"
@@ -11,6 +12,7 @@ depends_on_workplans:
- ITC-WP-0004
- ITC-WP-0005
- ITC-WP-0006
state_hub_workstream_id: "09f95da5-bfe0-42c0-a828-4b85f3cfc90a"
---
# ITC-WP-0008 - Railiance Fabric Conformance Support
@@ -32,8 +34,9 @@ system reasoning.
```task
id: ITC-WP-0008-T01
status: planned
status: todo
priority: high
state_hub_task_id: "fbe6e497-5c1b-4221-b470-d185e55b99a0"
```
- Define expected entity categories for a fabric-style system.
@@ -44,8 +47,9 @@ priority: high
```task
id: ITC-WP-0008-T02
status: planned
status: todo
priority: high
state_hub_task_id: "23bfb8b0-060e-4a66-a6a1-244cebc1e3c7"
```
- Identify which models railiance-fabric should map to first.
@@ -56,8 +60,9 @@ priority: high
```task
id: ITC-WP-0008-T03
status: planned
status: todo
priority: medium
state_hub_task_id: "3f8167a3-029b-4ebf-a517-1713e80ea39f"
```
- Add small graph examples showing clean entity/edge capture.
@@ -67,8 +72,9 @@ priority: medium
```task
id: ITC-WP-0008-T04
status: planned
status: todo
priority: medium
state_hub_task_id: "8454dda9-4fcc-4db9-afc1-3d7634d1a49f"
```
- Produce a brief for a railiance-fabric consumer workplan.
@@ -80,4 +86,3 @@ priority: medium
- Visualization needs inform the standard without forcing display semantics
into canonical concepts.
- A consumer workplan brief exists for railiance-fabric.

17
workplans/ITC-WP-0009-repo-scoping-comparison-and-extension.md
View File

@@ -2,14 +2,16 @@
id: ITC-WP-0009
type: workplan
title: "Repo Scoping Comparison And Extension"
domain: canon
repo: info-tech-canon
status: planned
status: proposed
priority: high
created: "2026-05-23"
updated: "2026-05-23"
depends_on_workplans:
- ITC-WP-0005
- ITC-WP-0006
state_hub_workstream_id: "97efb3e4-3303-41bd-a220-d1fbd7c24f01"
---
# ITC-WP-0009 - Repo Scoping Comparison And Extension
@@ -32,8 +34,9 @@ produce extension candidates rather than silently blending models.
```task
id: ITC-WP-0009-T01
status: planned
status: todo
priority: high
state_hub_task_id: "7f5b0093-29b8-453f-ab73-c44db71cde52"
```
- Define the questions used to compare repo-scoping with the canon.
@@ -44,8 +47,9 @@ priority: high
```task
id: ITC-WP-0009-T02
status: planned
status: todo
priority: high
state_hub_task_id: "d026d36b-e89d-4498-9c07-0f2e7f0c3c4c"
```
- Identify which canon concepts repo-scoping can reuse directly.
@@ -55,8 +59,9 @@ priority: high
```task
id: ITC-WP-0009-T03
status: planned
status: todo
priority: high
state_hub_task_id: "98888f6a-774f-4e6b-93f4-335fb3001e9c"
```
- Identify concepts the canon lacks or under-specifies.
@@ -67,8 +72,9 @@ priority: high
```task
id: ITC-WP-0009-T04
status: planned
status: todo
priority: medium
state_hub_task_id: "5b8ac21c-e0e4-4e45-817c-a91111712c82"
```
- Produce a brief for a repo-scoping consumer workplan.
@@ -79,4 +85,3 @@ priority: medium
- There is a clear comparison report.
- Canon extension candidates are explicit.
- Repo-scoping can plan adoption from its own repository.

17
workplans/ITC-WP-0010-caring-kubernetes-rbac-benchmark.md
View File

@@ -2,14 +2,16 @@
id: ITC-WP-0010
type: workplan
title: "CARING Kubernetes RBAC Benchmark"
domain: canon
repo: info-tech-canon
status: planned
status: proposed
priority: medium
created: "2026-05-23"
updated: "2026-05-23"
depends_on_workplans:
- ITC-WP-0003
- ITC-WP-0005
state_hub_workstream_id: "b64f0fc9-8668-4c02-8247-67a41660bdeb"
---
# ITC-WP-0010 - CARING Kubernetes RBAC Benchmark
@@ -31,8 +33,9 @@ Governance, Security, Network, DevSecOps, Observability, Task, and Tagging.
```task
id: ITC-WP-0010-T01
status: planned
status: todo
priority: high
state_hub_task_id: "9ad31e13-7dc2-469c-b539-d3375a16c5f4"
```
- Create `infospace/standards/caring/benchmarks/kubernetes-rbac/`.
@@ -42,8 +45,9 @@ priority: high
```task
id: ITC-WP-0010-T02
status: planned
status: todo
priority: high
state_hub_task_id: "180d7ccf-7daa-4f4c-a92a-641ef5d7b442"
```
- Map Kubernetes Role, ClusterRole, RoleBinding, ClusterRoleBinding,
@@ -54,8 +58,9 @@ priority: high
```task
id: ITC-WP-0010-T03
status: planned
status: todo
priority: high
state_hub_task_id: "4ffd6643-a7ab-487c-a09a-0fcaf0115c83"
```
- Express benchmark cases as CARING access descriptors.
@@ -66,8 +71,9 @@ priority: high
```task
id: ITC-WP-0010-T04
status: planned
status: todo
priority: medium
state_hub_task_id: "52632a4c-6e03-4212-ad6b-0cbb7b3a6e42"
```
- Produce gaps, conflicts, mappings, and proposed canon changes.
@@ -78,4 +84,3 @@ priority: medium
- Kubernetes RBAC is analyzed as a benchmark, not as a shortcut profile.
- CARING descriptor shape is tested with practical examples.
- Benchmark findings produce explicit canon change proposals.

18
workplans/README.md
View File

@@ -1,18 +0,0 @@
# InfoTechCanon Workplans
This directory registers the repo-local implementation workplans for turning
the current seed corpus into a practical, infospace-backed service.
The workplans here cover the InfoTechCanon side of the work: layout, service
surface, validation, profiles, retrieval artifacts, and canon-side support
packages for first consumers.
Consumer-repo adoption workplans should be created in the consumer repositories
themselves:
- `user-engine`
- `railiance-fabric`
- `repo-scoping`
See `index.yaml` for the registry and dependency order.