generated from coulomb/repo-seed
Register infospace service workplans
This commit is contained in:
102
canon.yaml
102
canon.yaml
@@ -6,6 +6,23 @@ 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:
|
||||
planned:
|
||||
- cli
|
||||
- json
|
||||
- api
|
||||
implementation_basis:
|
||||
- infospace-bench
|
||||
|
||||
classification:
|
||||
kernel:
|
||||
description: Defines how the canon is organized and evolved.
|
||||
@@ -17,84 +34,109 @@ classification:
|
||||
kernel:
|
||||
- id: itc-core
|
||||
title: InfoTechCanonCore
|
||||
path: kernel/InfoTechCanonCore.md
|
||||
path: infospace/kernel/InfoTechCanonCore.md
|
||||
status: RC1-seed
|
||||
- id: itc-kernel-map
|
||||
title: InfoTechCanonKernelMap
|
||||
path: kernel/InfoTechCanonKernelMap.md
|
||||
path: infospace/kernel/InfoTechCanonKernelMap.md
|
||||
status: RC1-kernel-map
|
||||
|
||||
models:
|
||||
- id: itc-infospace
|
||||
title: InfoTechCanonInformationSpaceModel
|
||||
path: models/information-space/InfoTechCanonInformationSpaceModel.md
|
||||
path: infospace/models/information-space/InfoTechCanonInformationSpaceModel.md
|
||||
status: RC1-seed
|
||||
- id: itc-land
|
||||
title: InfoTechCanonLandscapeModel
|
||||
path: models/landscape/InfoTechCanonLandscapeModel.md
|
||||
path: infospace/models/landscape/InfoTechCanonLandscapeModel.md
|
||||
status: RC1-seed
|
||||
- id: itc-org
|
||||
title: InfoTechCanonOrganizationModel
|
||||
path: models/organization/InfoTechCanonOrganizationModel.md
|
||||
path: infospace/models/organization/InfoTechCanonOrganizationModel.md
|
||||
status: RC1-seed
|
||||
- id: itc-gov
|
||||
title: InfoTechCanonGovernanceModel
|
||||
path: models/governance/InfoTechCanonGovernanceModel.md
|
||||
path: infospace/models/governance/InfoTechCanonGovernanceModel.md
|
||||
status: RC1-seed
|
||||
- id: itc-task
|
||||
title: InfoTechCanonTaskModel
|
||||
path: models/task/InfoTechCanonTaskModel.md
|
||||
path: infospace/models/task/InfoTechCanonTaskModel.md
|
||||
status: RC1-seed
|
||||
- id: itc-access
|
||||
title: InfoTechCanonAccessControlModel
|
||||
path: models/access-control/InfoTechCanonAccessControlModel.md
|
||||
path: infospace/models/access-control/InfoTechCanonAccessControlModel.md
|
||||
status: RC1-seed
|
||||
- id: itc-sec
|
||||
title: InfoTechCanonSecurityModel
|
||||
path: models/security/InfoTechCanonSecurityModel.md
|
||||
path: infospace/models/security/InfoTechCanonSecurityModel.md
|
||||
status: RC1-seed
|
||||
- id: itc-data
|
||||
title: InfoTechCanonDataModel
|
||||
path: models/data/InfoTechCanonDataModel.md
|
||||
path: infospace/models/data/InfoTechCanonDataModel.md
|
||||
status: RC1-seed
|
||||
- id: itc-devsecops
|
||||
title: InfoTechCanonDevSecOpsModel
|
||||
path: models/devsecops/InfoTechCanonDevSecOpsModel.md
|
||||
path: infospace/models/devsecops/InfoTechCanonDevSecOpsModel.md
|
||||
status: RC1-seed
|
||||
- id: itc-net
|
||||
title: InfoTechCanonNetworkModel
|
||||
path: models/network/InfoTechCanonNetworkModel.md
|
||||
path: infospace/models/network/InfoTechCanonNetworkModel.md
|
||||
status: RC1-seed
|
||||
- id: itc-obs
|
||||
title: InfoTechCanonObservabilityModel
|
||||
path: models/observability/InfoTechCanonObservabilityModel.md
|
||||
path: infospace/models/observability/InfoTechCanonObservabilityModel.md
|
||||
status: RC1-seed
|
||||
|
||||
standards:
|
||||
- id: itc-tag
|
||||
title: InfoTechCanonTaggingStandard
|
||||
path: standards/tagging/InfoTechCanonTaggingStandard.md
|
||||
path: infospace/standards/tagging/InfoTechCanonTaggingStandard.md
|
||||
status: RC1-seed
|
||||
- id: itc-caring
|
||||
title: InfoTechCanonCaringAccessGovernanceStandard
|
||||
path: standards/caring/InfoTechCanonCaringAccessGovernanceStandard.md
|
||||
path: infospace/standards/caring/InfoTechCanonCaringAccessGovernanceStandard.md
|
||||
status: 0.4.0-RC2-aligned
|
||||
|
||||
planned_directories:
|
||||
- profiles/
|
||||
- patterns/
|
||||
- mappings/
|
||||
- assimilation/
|
||||
- schemas/
|
||||
- views/
|
||||
- agent/
|
||||
- examples/
|
||||
- validation/
|
||||
- infospace/
|
||||
- infospace/profiles/
|
||||
- infospace/patterns/
|
||||
- infospace/mappings/
|
||||
- infospace/assimilation/
|
||||
- infospace/schemas/
|
||||
- infospace/views/
|
||||
- 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
|
||||
|
||||
first_proofs:
|
||||
near_term:
|
||||
- small-saas
|
||||
downstream_consumers:
|
||||
- user-engine
|
||||
- railiance-fabric
|
||||
- repo-scoping
|
||||
distinct_later_benchmarks:
|
||||
- caring-kubernetes-rbac
|
||||
|
||||
next_actions:
|
||||
- centralize generic mechanisms in Core
|
||||
- create schemas for core artifact types
|
||||
- create concept ownership index
|
||||
- create agent briefs
|
||||
- run CARING assimilation benchmark
|
||||
- create small-saas kernel profile
|
||||
- implement ITC-WP-0001 infospace scaffold
|
||||
- implement ITC-WP-0002 service surface
|
||||
- implement ITC-WP-0003 validation and generated views
|
||||
- implement ITC-WP-0004 small-saas profile proof
|
||||
- explore ITC-WP-0006 PURPOSES model extension
|
||||
|
||||
107
workplans/ITC-WP-0001-infospace-scaffold-and-seed-placement.md
Normal file
107
workplans/ITC-WP-0001-infospace-scaffold-and-seed-placement.md
Normal file
@@ -0,0 +1,107 @@
|
||||
---
|
||||
id: ITC-WP-0001
|
||||
type: workplan
|
||||
title: "Infospace Scaffold And Seed Placement"
|
||||
repo: info-tech-canon
|
||||
status: planned
|
||||
priority: high
|
||||
created: "2026-05-23"
|
||||
updated: "2026-05-23"
|
||||
depends_on_workplans: []
|
||||
---
|
||||
|
||||
# ITC-WP-0001 - Infospace Scaffold And Seed Placement
|
||||
|
||||
## Goal
|
||||
|
||||
Create the concrete `infospace/` root and place the existing seed corpus into
|
||||
the newer `kernel/`, `models/`, and `standards/` layout.
|
||||
|
||||
## Intent
|
||||
|
||||
This repository implements one infospace, but the infospace should not be the
|
||||
repo root. The root remains the service/repo shell. The canon content lives in
|
||||
`infospace/`.
|
||||
|
||||
The canonical layout is:
|
||||
|
||||
```text
|
||||
infospace/
|
||||
infospace.yaml
|
||||
artifacts/index.yaml
|
||||
kernel/
|
||||
models/
|
||||
standards/
|
||||
profiles/
|
||||
patterns/
|
||||
mappings/
|
||||
assimilation/
|
||||
schemas/
|
||||
views/
|
||||
agent/
|
||||
examples/
|
||||
validation/
|
||||
```
|
||||
|
||||
## Tasks
|
||||
|
||||
### T01 - Create infospace layout
|
||||
|
||||
```task
|
||||
id: ITC-WP-0001-T01
|
||||
status: planned
|
||||
priority: high
|
||||
```
|
||||
|
||||
- Create `infospace/` as the single canon infospace root.
|
||||
- Add the infospace-bench required files and directories.
|
||||
- Add README placeholders only where needed for Git tracking.
|
||||
|
||||
### T02 - Move seed artifacts into canonical paths
|
||||
|
||||
```task
|
||||
id: ITC-WP-0001-T02
|
||||
status: planned
|
||||
priority: high
|
||||
```
|
||||
|
||||
- Place Core and Kernel Map under `infospace/kernel/`.
|
||||
- Place broad domain models under `infospace/models/<domain>/`.
|
||||
- Place Tagging and CARING under `infospace/standards/<standard>/`.
|
||||
- Keep the original `seeds/` files as provenance until the first scaffold
|
||||
release is reviewed.
|
||||
|
||||
### T03 - Adapt manifests and path references
|
||||
|
||||
```task
|
||||
id: ITC-WP-0001-T03
|
||||
status: planned
|
||||
priority: high
|
||||
```
|
||||
|
||||
- Update `canon.yaml` to point at `infospace/...` paths.
|
||||
- Add `infospace/artifacts/index.yaml` entries for the placed artifacts.
|
||||
- Make generated and curated paths explicit.
|
||||
- Replace older `core/` references with `kernel/` where they describe the
|
||||
current target layout.
|
||||
|
||||
### T04 - Preserve provenance
|
||||
|
||||
```task
|
||||
id: ITC-WP-0001-T04
|
||||
status: planned
|
||||
priority: medium
|
||||
```
|
||||
|
||||
- Record each artifact's seed source path.
|
||||
- Add a scaffold report describing moved, copied, and deferred files.
|
||||
- Avoid semantic refactoring during the placement pass.
|
||||
|
||||
## Acceptance
|
||||
|
||||
- The repo has a concrete `infospace/` root.
|
||||
- `canon.yaml` and `infospace/artifacts/index.yaml` agree on canonical paths.
|
||||
- The seed documents are available under the newer `kernel/models/standards`
|
||||
layout.
|
||||
- Original seed provenance remains traceable.
|
||||
|
||||
97
workplans/ITC-WP-0002-service-surface-cli-json-api.md
Normal file
97
workplans/ITC-WP-0002-service-surface-cli-json-api.md
Normal file
@@ -0,0 +1,97 @@
|
||||
---
|
||||
id: ITC-WP-0002
|
||||
type: workplan
|
||||
title: "Service Surface Baseline CLI JSON API"
|
||||
repo: info-tech-canon
|
||||
status: planned
|
||||
priority: high
|
||||
created: "2026-05-23"
|
||||
updated: "2026-05-23"
|
||||
depends_on_workplans:
|
||||
- ITC-WP-0001
|
||||
---
|
||||
|
||||
# ITC-WP-0002 - Service Surface Baseline CLI JSON API
|
||||
|
||||
## Goal
|
||||
|
||||
Create the first practical service surface for InfoTechCanon: a JSON-oriented
|
||||
CLI, importable Python service layer, and minimal local API from the start.
|
||||
|
||||
## Intent
|
||||
|
||||
The service should use `infospace-bench` facilities instead of inventing a
|
||||
parallel infospace runtime. The initial surface should be small, explicit, and
|
||||
usable by downstream agents and tools.
|
||||
|
||||
## Tasks
|
||||
|
||||
### T01 - Package skeleton
|
||||
|
||||
```task
|
||||
id: ITC-WP-0002-T01
|
||||
status: planned
|
||||
priority: high
|
||||
```
|
||||
|
||||
- Add a minimal Python package for InfoTechCanon service code.
|
||||
- Add `pyproject.toml` with local dependency expectations for
|
||||
`infospace-bench`.
|
||||
- Keep runtime dependencies narrow.
|
||||
|
||||
### T02 - CLI commands
|
||||
|
||||
```task
|
||||
id: ITC-WP-0002-T02
|
||||
status: planned
|
||||
priority: high
|
||||
```
|
||||
|
||||
- Add commands that return JSON by default:
|
||||
- inspect canon
|
||||
- list artifacts
|
||||
- list standards
|
||||
- list models
|
||||
- validate
|
||||
- graph
|
||||
- profile inspect
|
||||
- Use structured errors.
|
||||
|
||||
### T03 - Python service layer
|
||||
|
||||
```task
|
||||
id: ITC-WP-0002-T03
|
||||
status: planned
|
||||
priority: high
|
||||
```
|
||||
|
||||
- Wrap infospace loading, artifact listing, validation, metrics, and graph
|
||||
export behind stable service functions.
|
||||
- Keep domain-specific canon logic separate from generic infospace-bench logic.
|
||||
|
||||
### T04 - API baseline
|
||||
|
||||
```task
|
||||
id: ITC-WP-0002-T04
|
||||
status: planned
|
||||
priority: high
|
||||
```
|
||||
|
||||
- Add a minimal local API for read-only canon inspection.
|
||||
- Endpoints should mirror CLI contracts where practical.
|
||||
- Prefer JSON responses suitable for agents and tools.
|
||||
- Defer authentication, remote deployment, and multi-tenant concerns.
|
||||
|
||||
## Non-Goals
|
||||
|
||||
- Do not build a large web application.
|
||||
- Do not duplicate infospace-bench lifecycle implementation.
|
||||
- Do not introduce semantic changes to canon documents in this workplan.
|
||||
|
||||
## Acceptance
|
||||
|
||||
- The repo exposes CLI, JSON, and API entry points.
|
||||
- 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.
|
||||
|
||||
109
workplans/ITC-WP-0003-validation-indexes-and-generated-views.md
Normal file
109
workplans/ITC-WP-0003-validation-indexes-and-generated-views.md
Normal file
@@ -0,0 +1,109 @@
|
||||
---
|
||||
id: ITC-WP-0003
|
||||
type: workplan
|
||||
title: "Validation Indexes And Generated Views"
|
||||
repo: info-tech-canon
|
||||
status: planned
|
||||
priority: high
|
||||
created: "2026-05-23"
|
||||
updated: "2026-05-23"
|
||||
depends_on_workplans:
|
||||
- ITC-WP-0001
|
||||
- ITC-WP-0002
|
||||
---
|
||||
|
||||
# ITC-WP-0003 - Validation Indexes And Generated Views
|
||||
|
||||
## Goal
|
||||
|
||||
Add repeatable validation, schema stubs, indexes, and generated views so the
|
||||
canon can be maintained by humans and consumed by tools.
|
||||
|
||||
## Intent
|
||||
|
||||
The first validation pass should be useful before it is complete. Missing
|
||||
optional artifacts should be warnings. Broken required paths and manifest
|
||||
inconsistencies should fail visibly.
|
||||
|
||||
## Tasks
|
||||
|
||||
### T01 - Make targets
|
||||
|
||||
```task
|
||||
id: ITC-WP-0003-T01
|
||||
status: planned
|
||||
priority: high
|
||||
```
|
||||
|
||||
- Add `make validate`.
|
||||
- Add `make index`.
|
||||
- Add `make tree`.
|
||||
- Add `make agent-briefs`.
|
||||
|
||||
### T02 - Structural validation
|
||||
|
||||
```task
|
||||
id: ITC-WP-0003-T02
|
||||
status: planned
|
||||
priority: high
|
||||
```
|
||||
|
||||
- Check required top-level files.
|
||||
- Check required `infospace/` directories.
|
||||
- Check `canon.yaml` paths.
|
||||
- Check `infospace/artifacts/index.yaml`.
|
||||
- Warn about missing optional agent briefs, concepts, mappings, and examples.
|
||||
|
||||
### T03 - Schemas
|
||||
|
||||
```task
|
||||
id: ITC-WP-0003-T03
|
||||
status: planned
|
||||
priority: high
|
||||
```
|
||||
|
||||
- Add minimal schemas for:
|
||||
- standard
|
||||
- concept
|
||||
- mapping
|
||||
- profile
|
||||
- assimilation
|
||||
- interface card
|
||||
- agent brief
|
||||
- workplan
|
||||
|
||||
### T04 - Generated views
|
||||
|
||||
```task
|
||||
id: ITC-WP-0003-T04
|
||||
status: planned
|
||||
priority: high
|
||||
```
|
||||
|
||||
- Generate `views/by-standard.md`.
|
||||
- Generate `views/by-concept.md`.
|
||||
- Generate `views/by-profile.md`.
|
||||
- Generate `views/by-mapping-target.md`.
|
||||
- Generate `views/kernel-overview.md`.
|
||||
- Mark generated files clearly.
|
||||
|
||||
### T05 - Ownership and duplication checks
|
||||
|
||||
```task
|
||||
id: ITC-WP-0003-T05
|
||||
status: planned
|
||||
priority: medium
|
||||
```
|
||||
|
||||
- Create a first concept ownership index.
|
||||
- Detect duplicate concept candidates.
|
||||
- Produce a cross-standard import matrix.
|
||||
- Report unresolved ownership conflicts.
|
||||
|
||||
## Acceptance
|
||||
|
||||
- `make validate` is the primary confidence command.
|
||||
- Validation produces machine-readable output.
|
||||
- Generated views can be refreshed deterministically.
|
||||
- Concept ownership can be inspected even before all concept pages exist.
|
||||
|
||||
90
workplans/ITC-WP-0004-small-saas-profile-proof.md
Normal file
90
workplans/ITC-WP-0004-small-saas-profile-proof.md
Normal file
@@ -0,0 +1,90 @@
|
||||
---
|
||||
id: ITC-WP-0004
|
||||
type: workplan
|
||||
title: "Small SaaS Profile Proof"
|
||||
repo: info-tech-canon
|
||||
status: planned
|
||||
priority: high
|
||||
created: "2026-05-23"
|
||||
updated: "2026-05-23"
|
||||
depends_on_workplans:
|
||||
- ITC-WP-0001
|
||||
- ITC-WP-0002
|
||||
- ITC-WP-0003
|
||||
---
|
||||
|
||||
# ITC-WP-0004 - Small SaaS Profile Proof
|
||||
|
||||
## Goal
|
||||
|
||||
Create the first practical profile proof: a small SaaS system profile that
|
||||
uses the kernel, models, and standards without waiting for the larger CARING
|
||||
benchmark.
|
||||
|
||||
## Intent
|
||||
|
||||
The first proof should show that InfoTechCanon can guide a real implementation
|
||||
shape: service ownership, users, tenants, access, data, runtime, deployment,
|
||||
governance, observability, and work tracking.
|
||||
|
||||
## Tasks
|
||||
|
||||
### T01 - Profile definition
|
||||
|
||||
```task
|
||||
id: ITC-WP-0004-T01
|
||||
status: planned
|
||||
priority: high
|
||||
```
|
||||
|
||||
- Create `infospace/profiles/small-saas/`.
|
||||
- Define scope, assumptions, required standards, and conformance level.
|
||||
- Declare which model concepts are required, optional, or out of scope.
|
||||
|
||||
### T02 - Example artifacts
|
||||
|
||||
```task
|
||||
id: ITC-WP-0004-T02
|
||||
status: planned
|
||||
priority: high
|
||||
```
|
||||
|
||||
- Add example service, system, tenant, user, team, dataset, deployment,
|
||||
task, policy, control, evidence, and incident artifacts.
|
||||
- Keep examples small but connected.
|
||||
- Add relationships suitable for graph export.
|
||||
|
||||
### T03 - Validation rules
|
||||
|
||||
```task
|
||||
id: ITC-WP-0004-T03
|
||||
status: planned
|
||||
priority: high
|
||||
```
|
||||
|
||||
- Define required fields and links for small SaaS artifacts.
|
||||
- Validate service ownership.
|
||||
- Validate tenant and namespace separation claims.
|
||||
- Validate user-management and access-control traces.
|
||||
- Validate evidence links for governance claims.
|
||||
|
||||
### T04 - Report and demo commands
|
||||
|
||||
```task
|
||||
id: ITC-WP-0004-T04
|
||||
status: planned
|
||||
priority: medium
|
||||
```
|
||||
|
||||
- Add a profile report under `infospace/reports/`.
|
||||
- Add CLI/API inspection examples.
|
||||
- Produce a graph view of the small SaaS proof.
|
||||
|
||||
## Acceptance
|
||||
|
||||
- The small SaaS profile is the first executable proof of the canon.
|
||||
- Profile artifacts validate through the service surface.
|
||||
- The proof produces useful graph and JSON outputs.
|
||||
- The result is suitable as the baseline for user-engine and railiance-fabric
|
||||
evaluation.
|
||||
|
||||
@@ -0,0 +1,82 @@
|
||||
---
|
||||
id: ITC-WP-0005
|
||||
type: workplan
|
||||
title: "Retrieval Agent Briefs And Interface Cards"
|
||||
repo: info-tech-canon
|
||||
status: planned
|
||||
priority: medium
|
||||
created: "2026-05-23"
|
||||
updated: "2026-05-23"
|
||||
depends_on_workplans:
|
||||
- ITC-WP-0003
|
||||
- ITC-WP-0004
|
||||
---
|
||||
|
||||
# ITC-WP-0005 - Retrieval Agent Briefs And Interface Cards
|
||||
|
||||
## Goal
|
||||
|
||||
Make InfoTechCanon retrievable and usable by agents, tools, and consumer
|
||||
repositories without requiring them to read every full standard.
|
||||
|
||||
## Intent
|
||||
|
||||
The canon needs compact, source-linked retrieval artifacts that preserve the
|
||||
important distinctions: Actor vs Subject vs Principal, Organization Role vs
|
||||
AccessRole vs CARING role, Policy vs Control vs Evidence, and similar rules.
|
||||
|
||||
## Tasks
|
||||
|
||||
### T01 - Agent briefs
|
||||
|
||||
```task
|
||||
id: ITC-WP-0005-T01
|
||||
status: planned
|
||||
priority: high
|
||||
```
|
||||
|
||||
- Place the global agent brief under `infospace/agent/`.
|
||||
- Add per-standard and per-model agent briefs.
|
||||
- Validate that agent briefs point back to full source artifacts.
|
||||
|
||||
### T02 - Retrieval index
|
||||
|
||||
```task
|
||||
id: ITC-WP-0005-T02
|
||||
status: planned
|
||||
priority: high
|
||||
```
|
||||
|
||||
- Generate `infospace/agent/retrieval-index.md` and a JSON/YAML equivalent.
|
||||
- Include stable IDs, canonical paths, summary, owned concepts, imports,
|
||||
warnings, and common distinctions.
|
||||
|
||||
### T03 - Canon Interface Card template
|
||||
|
||||
```task
|
||||
id: ITC-WP-0005-T03
|
||||
status: planned
|
||||
priority: medium
|
||||
```
|
||||
|
||||
- Define a Canon Interface Card template.
|
||||
- Include fields for owned concepts, produced concepts, consumed concepts,
|
||||
implemented profiles, mappings, validation expectations, and consumer needs.
|
||||
|
||||
### T04 - Consumer brief templates
|
||||
|
||||
```task
|
||||
id: ITC-WP-0005-T04
|
||||
status: planned
|
||||
priority: medium
|
||||
```
|
||||
|
||||
- Create brief templates for user-engine, railiance-fabric, and repo-scoping.
|
||||
- Keep actual adoption workplans in those repos.
|
||||
|
||||
## Acceptance
|
||||
|
||||
- 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.
|
||||
|
||||
107
workplans/ITC-WP-0006-purpose-and-demand-model.md
Normal file
107
workplans/ITC-WP-0006-purpose-and-demand-model.md
Normal file
@@ -0,0 +1,107 @@
|
||||
---
|
||||
id: ITC-WP-0006
|
||||
type: workplan
|
||||
title: "Purpose And Demand Model Extension"
|
||||
repo: info-tech-canon
|
||||
status: planned
|
||||
priority: high
|
||||
created: "2026-05-23"
|
||||
updated: "2026-05-23"
|
||||
depends_on_workplans:
|
||||
- ITC-WP-0003
|
||||
---
|
||||
|
||||
# ITC-WP-0006 - Purpose And Demand Model Extension
|
||||
|
||||
## Goal
|
||||
|
||||
Explore and formalize the missing PURPOSES concept family and how it relates
|
||||
to INTENT, SCOPE, governance, repository evolution, and consumer demand.
|
||||
|
||||
## Intent
|
||||
|
||||
A repository should be able to learn what it is used for. Consumers express
|
||||
their demand as purposes or use cases anchored in their intent. The producing
|
||||
repo can then adapt its scope, interfaces, profiles, and evolution priorities
|
||||
based on those declared purposes.
|
||||
|
||||
Working distinction:
|
||||
|
||||
```text
|
||||
INTENT
|
||||
Why the producer exists and what it is trying to become.
|
||||
|
||||
SCOPE
|
||||
What the producer currently includes, excludes, owns, and promises.
|
||||
|
||||
PURPOSES
|
||||
What consumers use, need, want, or value from the producer, anchored in
|
||||
the consumers' own intent.
|
||||
```
|
||||
|
||||
## Tasks
|
||||
|
||||
### T01 - Concept proposal
|
||||
|
||||
```task
|
||||
id: ITC-WP-0006-T01
|
||||
status: planned
|
||||
priority: high
|
||||
```
|
||||
|
||||
- Define candidate concepts:
|
||||
- Purpose
|
||||
- ConsumerPurpose
|
||||
- UseCase
|
||||
- DemandSignal
|
||||
- ConsumerNeed
|
||||
- ProducerCapability
|
||||
- PurposeFit
|
||||
- ScopePressure
|
||||
- EvolutionRequest
|
||||
- Identify likely owners across Core, Governance, Task, and Information Space.
|
||||
|
||||
### T02 - INTENT/SCOPE/PURPOSES pattern
|
||||
|
||||
```task
|
||||
id: ITC-WP-0006-T02
|
||||
status: planned
|
||||
priority: high
|
||||
```
|
||||
|
||||
- Create a pattern explaining how producer intent, current scope, and consumer
|
||||
purposes interact.
|
||||
- Show how purposes can generate tasks, governance decisions, profile changes,
|
||||
and interface changes.
|
||||
|
||||
### T03 - Governance extension candidates
|
||||
|
||||
```task
|
||||
id: ITC-WP-0006-T03
|
||||
status: planned
|
||||
priority: high
|
||||
```
|
||||
|
||||
- Determine which purpose concepts belong in the Governance Model.
|
||||
- Add decision and evidence expectations for accepting, rejecting, or deferring
|
||||
consumer purposes.
|
||||
- Connect purpose pressure to roadmap and change control concepts.
|
||||
|
||||
### T04 - Examples
|
||||
|
||||
```task
|
||||
id: ITC-WP-0006-T04
|
||||
status: planned
|
||||
priority: medium
|
||||
```
|
||||
|
||||
- Add examples for user-engine, railiance-fabric, and repo-scoping as
|
||||
consumers of InfoTechCanon.
|
||||
- Express each as canon-side examples, not as consumer repo adoption tasks.
|
||||
|
||||
## Acceptance
|
||||
|
||||
- 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.
|
||||
|
||||
88
workplans/ITC-WP-0007-user-engine-evaluation-readiness.md
Normal file
88
workplans/ITC-WP-0007-user-engine-evaluation-readiness.md
Normal file
@@ -0,0 +1,88 @@
|
||||
---
|
||||
id: ITC-WP-0007
|
||||
type: workplan
|
||||
title: "User Engine Evaluation Readiness"
|
||||
repo: info-tech-canon
|
||||
status: planned
|
||||
priority: high
|
||||
created: "2026-05-23"
|
||||
updated: "2026-05-23"
|
||||
depends_on_workplans:
|
||||
- ITC-WP-0004
|
||||
- ITC-WP-0005
|
||||
- ITC-WP-0006
|
||||
---
|
||||
|
||||
# ITC-WP-0007 - User Engine Evaluation Readiness
|
||||
|
||||
## Goal
|
||||
|
||||
Prepare canon-side evaluation material for assessing `user-engine` against
|
||||
InfoTechCanon before integrating it as the user-management capability.
|
||||
|
||||
## Intent
|
||||
|
||||
The first use of the service will be evaluation, not direct enforcement. The
|
||||
canon should help determine whether user-engine cleanly represents users,
|
||||
actors, subjects, principals, organization roles, access roles, purposes,
|
||||
governance expectations, and integration boundaries.
|
||||
|
||||
## Tasks
|
||||
|
||||
### T01 - Evaluation question set
|
||||
|
||||
```task
|
||||
id: ITC-WP-0007-T01
|
||||
status: planned
|
||||
priority: high
|
||||
```
|
||||
|
||||
- Create a canon-side question set for user-management capability evaluation.
|
||||
- Cover Organization, Access Control, Governance, Data, Security, Task, and
|
||||
PURPOSES concepts.
|
||||
|
||||
### T02 - Expected artifact profile
|
||||
|
||||
```task
|
||||
id: ITC-WP-0007-T02
|
||||
status: planned
|
||||
priority: high
|
||||
```
|
||||
|
||||
- Define expected Canon Interface Card fields for user-engine.
|
||||
- Define expected entity and edge types user-engine should expose or map.
|
||||
- Define evidence needed before integration.
|
||||
|
||||
### T03 - Small SaaS alignment
|
||||
|
||||
```task
|
||||
id: ITC-WP-0007-T03
|
||||
status: planned
|
||||
priority: medium
|
||||
```
|
||||
|
||||
- Use the small SaaS profile as the concrete evaluation lens.
|
||||
- Identify where user-engine should satisfy profile requirements.
|
||||
|
||||
### T04 - Consumer workplan brief
|
||||
|
||||
```task
|
||||
id: ITC-WP-0007-T04
|
||||
status: planned
|
||||
priority: medium
|
||||
```
|
||||
|
||||
- Produce a brief that can be copied into a user-engine workplan.
|
||||
- Do not create or maintain the user-engine adoption workplan here.
|
||||
|
||||
## Non-Goals
|
||||
|
||||
- Do not refactor user-engine in this repo.
|
||||
- Do not decide user-engine implementation details here.
|
||||
|
||||
## Acceptance
|
||||
|
||||
- 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.
|
||||
|
||||
@@ -0,0 +1,83 @@
|
||||
---
|
||||
id: ITC-WP-0008
|
||||
type: workplan
|
||||
title: "Railiance Fabric Conformance Support"
|
||||
repo: info-tech-canon
|
||||
status: planned
|
||||
priority: high
|
||||
created: "2026-05-23"
|
||||
updated: "2026-05-23"
|
||||
depends_on_workplans:
|
||||
- ITC-WP-0004
|
||||
- ITC-WP-0005
|
||||
- ITC-WP-0006
|
||||
---
|
||||
|
||||
# ITC-WP-0008 - Railiance Fabric Conformance Support
|
||||
|
||||
## Goal
|
||||
|
||||
Prepare canon-side support for refactoring `railiance-fabric` to conform to
|
||||
and inform InfoTechCanon, especially entity and edge capture for visualization.
|
||||
|
||||
## Intent
|
||||
|
||||
Railiance-fabric should become a practical pressure test for whether the canon
|
||||
captures useful entities and edges cleanly enough for graph visualization and
|
||||
system reasoning.
|
||||
|
||||
## Tasks
|
||||
|
||||
### T01 - Entity and edge capture criteria
|
||||
|
||||
```task
|
||||
id: ITC-WP-0008-T01
|
||||
status: planned
|
||||
priority: high
|
||||
```
|
||||
|
||||
- Define expected entity categories for a fabric-style system.
|
||||
- Define relationship and edge categories that support visualization.
|
||||
- Separate canonical relationships from display-only graph edges.
|
||||
|
||||
### T02 - Mapping expectations
|
||||
|
||||
```task
|
||||
id: ITC-WP-0008-T02
|
||||
status: planned
|
||||
priority: high
|
||||
```
|
||||
|
||||
- Identify which models railiance-fabric should map to first.
|
||||
- Include Landscape, Network, Data, DevSecOps, Observability, Governance,
|
||||
Security, and PURPOSES where relevant.
|
||||
|
||||
### T03 - Visualization examples
|
||||
|
||||
```task
|
||||
id: ITC-WP-0008-T03
|
||||
status: planned
|
||||
priority: medium
|
||||
```
|
||||
|
||||
- Add small graph examples showing clean entity/edge capture.
|
||||
- Include examples that expose bad graph shapes and their correction.
|
||||
|
||||
### T04 - Consumer workplan brief
|
||||
|
||||
```task
|
||||
id: ITC-WP-0008-T04
|
||||
status: planned
|
||||
priority: medium
|
||||
```
|
||||
|
||||
- Produce a brief for a railiance-fabric consumer workplan.
|
||||
- Keep the actual railiance-fabric refactor workplan in that repo.
|
||||
|
||||
## Acceptance
|
||||
|
||||
- The canon defines practical graph capture expectations for railiance-fabric.
|
||||
- Visualization needs inform the standard without forcing display semantics
|
||||
into canonical concepts.
|
||||
- A consumer workplan brief exists for railiance-fabric.
|
||||
|
||||
@@ -0,0 +1,82 @@
|
||||
---
|
||||
id: ITC-WP-0009
|
||||
type: workplan
|
||||
title: "Repo Scoping Comparison And Extension"
|
||||
repo: info-tech-canon
|
||||
status: planned
|
||||
priority: high
|
||||
created: "2026-05-23"
|
||||
updated: "2026-05-23"
|
||||
depends_on_workplans:
|
||||
- ITC-WP-0005
|
||||
- ITC-WP-0006
|
||||
---
|
||||
|
||||
# ITC-WP-0009 - Repo Scoping Comparison And Extension
|
||||
|
||||
## Goal
|
||||
|
||||
Compare InfoTechCanon with `repo-scoping` to identify how repo-scoping can
|
||||
benefit from the canon and where the canon should be extended to maximize
|
||||
repo-scoping utility.
|
||||
|
||||
## Intent
|
||||
|
||||
Repo-scoping is likely to stress the Governance Model and the emerging
|
||||
INTENT/SCOPE/PURPOSES pattern. The comparison should be explicit and should
|
||||
produce extension candidates rather than silently blending models.
|
||||
|
||||
## Tasks
|
||||
|
||||
### T01 - Comparison frame
|
||||
|
||||
```task
|
||||
id: ITC-WP-0009-T01
|
||||
status: planned
|
||||
priority: high
|
||||
```
|
||||
|
||||
- Define the questions used to compare repo-scoping with the canon.
|
||||
- Cover repository intent, current scope, future scope, consumers, purposes,
|
||||
decisions, evidence, risks, and evolution requests.
|
||||
|
||||
### T02 - Canon benefit analysis
|
||||
|
||||
```task
|
||||
id: ITC-WP-0009-T02
|
||||
status: planned
|
||||
priority: high
|
||||
```
|
||||
|
||||
- Identify which canon concepts repo-scoping can reuse directly.
|
||||
- Identify which mappings or profiles would make repo-scoping more useful.
|
||||
|
||||
### T03 - Extension candidates
|
||||
|
||||
```task
|
||||
id: ITC-WP-0009-T03
|
||||
status: planned
|
||||
priority: high
|
||||
```
|
||||
|
||||
- Identify concepts the canon lacks or under-specifies.
|
||||
- Pay special attention to PURPOSES and governance concepts.
|
||||
- Produce candidate changes for review before altering standards.
|
||||
|
||||
### T04 - Consumer workplan brief
|
||||
|
||||
```task
|
||||
id: ITC-WP-0009-T04
|
||||
status: planned
|
||||
priority: medium
|
||||
```
|
||||
|
||||
- Produce a brief for a repo-scoping consumer workplan.
|
||||
- Keep the actual repo-scoping adoption workplan in that repo.
|
||||
|
||||
## Acceptance
|
||||
|
||||
- There is a clear comparison report.
|
||||
- Canon extension candidates are explicit.
|
||||
- Repo-scoping can plan adoption from its own repository.
|
||||
|
||||
81
workplans/ITC-WP-0010-caring-kubernetes-rbac-benchmark.md
Normal file
81
workplans/ITC-WP-0010-caring-kubernetes-rbac-benchmark.md
Normal file
@@ -0,0 +1,81 @@
|
||||
---
|
||||
id: ITC-WP-0010
|
||||
type: workplan
|
||||
title: "CARING Kubernetes RBAC Benchmark"
|
||||
repo: info-tech-canon
|
||||
status: planned
|
||||
priority: medium
|
||||
created: "2026-05-23"
|
||||
updated: "2026-05-23"
|
||||
depends_on_workplans:
|
||||
- ITC-WP-0003
|
||||
- ITC-WP-0005
|
||||
---
|
||||
|
||||
# ITC-WP-0010 - CARING Kubernetes RBAC Benchmark
|
||||
|
||||
## Goal
|
||||
|
||||
Create a distinct benchmark workplan for analyzing Kubernetes RBAC through
|
||||
CARING and the wider InfoTechCanon kernel.
|
||||
|
||||
## Intent
|
||||
|
||||
This is deliberately separate from the small SaaS proof. The benchmark is more
|
||||
ambitious and should stress orthogonality across Access Control, Organization,
|
||||
Governance, Security, Network, DevSecOps, Observability, Task, and Tagging.
|
||||
|
||||
## Tasks
|
||||
|
||||
### T01 - Benchmark workspace
|
||||
|
||||
```task
|
||||
id: ITC-WP-0010-T01
|
||||
status: planned
|
||||
priority: high
|
||||
```
|
||||
|
||||
- Create `infospace/standards/caring/benchmarks/kubernetes-rbac/`.
|
||||
- Define source corpus, cases, expected outputs, and review criteria.
|
||||
|
||||
### T02 - RBAC assimilation
|
||||
|
||||
```task
|
||||
id: ITC-WP-0010-T02
|
||||
status: planned
|
||||
priority: high
|
||||
```
|
||||
|
||||
- Map Kubernetes Role, ClusterRole, RoleBinding, ClusterRoleBinding,
|
||||
ServiceAccount, Namespace, verbs, resources, and scopes.
|
||||
- Preserve the warning that Namespace is not automatically a tenant boundary.
|
||||
|
||||
### T03 - CARING access descriptors
|
||||
|
||||
```task
|
||||
id: ITC-WP-0010-T03
|
||||
status: planned
|
||||
priority: high
|
||||
```
|
||||
|
||||
- Express benchmark cases as CARING access descriptors.
|
||||
- Distinguish declared access, effective access, derived capability, and
|
||||
induced access.
|
||||
|
||||
### T04 - Findings and canon pressure
|
||||
|
||||
```task
|
||||
id: ITC-WP-0010-T04
|
||||
status: planned
|
||||
priority: medium
|
||||
```
|
||||
|
||||
- Produce gaps, conflicts, mappings, and proposed canon changes.
|
||||
- Feed stable findings back into models and standards through explicit tasks.
|
||||
|
||||
## Acceptance
|
||||
|
||||
- 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
Normal file
18
workplans/README.md
Normal file
@@ -0,0 +1,18 @@
|
||||
# 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.
|
||||
|
||||
149
workplans/index.yaml
Normal file
149
workplans/index.yaml
Normal file
@@ -0,0 +1,149 @@
|
||||
repository: info-tech-canon
|
||||
type: workplan-registry
|
||||
status: planned
|
||||
created: "2026-05-23"
|
||||
updated: "2026-05-23"
|
||||
|
||||
implementation_decisions:
|
||||
infospace_root: infospace/
|
||||
layout_family: kernel-models-standards
|
||||
service_surface:
|
||||
- cli
|
||||
- json
|
||||
- api
|
||||
first_proof: small-saas
|
||||
later_benchmark: caring-kubernetes-rbac
|
||||
consumer_workplans_live_in_consumer_repos: true
|
||||
|
||||
workplans:
|
||||
- id: ITC-WP-0001
|
||||
title: Infospace Scaffold And Seed Placement
|
||||
status: planned
|
||||
priority: high
|
||||
path: workplans/ITC-WP-0001-infospace-scaffold-and-seed-placement.md
|
||||
depends_on: []
|
||||
produces:
|
||||
- infospace/
|
||||
- infospace/infospace.yaml
|
||||
- canonical kernel/models/standards layout
|
||||
|
||||
- id: ITC-WP-0002
|
||||
title: Service Surface Baseline CLI JSON API
|
||||
status: planned
|
||||
priority: high
|
||||
path: workplans/ITC-WP-0002-service-surface-cli-json-api.md
|
||||
depends_on:
|
||||
- ITC-WP-0001
|
||||
produces:
|
||||
- Python package skeleton
|
||||
- JSON-oriented CLI
|
||||
- local API surface
|
||||
- infospace-bench integration boundary
|
||||
|
||||
- id: ITC-WP-0003
|
||||
title: Validation Indexes And Generated Views
|
||||
status: planned
|
||||
priority: high
|
||||
path: workplans/ITC-WP-0003-validation-indexes-and-generated-views.md
|
||||
depends_on:
|
||||
- ITC-WP-0001
|
||||
- ITC-WP-0002
|
||||
produces:
|
||||
- make validate
|
||||
- generated indexes
|
||||
- generated views
|
||||
- initial schemas
|
||||
|
||||
- id: ITC-WP-0004
|
||||
title: Small SaaS Profile Proof
|
||||
status: planned
|
||||
priority: high
|
||||
path: workplans/ITC-WP-0004-small-saas-profile-proof.md
|
||||
depends_on:
|
||||
- ITC-WP-0001
|
||||
- ITC-WP-0002
|
||||
- ITC-WP-0003
|
||||
produces:
|
||||
- small-saas profile
|
||||
- example artifacts
|
||||
- profile validation rules
|
||||
|
||||
- id: ITC-WP-0005
|
||||
title: Retrieval Agent Briefs And Interface Cards
|
||||
status: planned
|
||||
priority: medium
|
||||
path: workplans/ITC-WP-0005-retrieval-agent-briefs-and-interface-cards.md
|
||||
depends_on:
|
||||
- ITC-WP-0003
|
||||
- ITC-WP-0004
|
||||
produces:
|
||||
- global and per-standard agent briefs
|
||||
- retrieval index
|
||||
- Canon Interface Card templates
|
||||
|
||||
- id: ITC-WP-0006
|
||||
title: Purpose And Demand Model Extension
|
||||
status: planned
|
||||
priority: high
|
||||
path: workplans/ITC-WP-0006-purpose-and-demand-model.md
|
||||
depends_on:
|
||||
- ITC-WP-0003
|
||||
produces:
|
||||
- PURPOSES concept proposal
|
||||
- INTENT/SCOPE/PURPOSES fit
|
||||
- governance model extension candidates
|
||||
|
||||
- id: ITC-WP-0007
|
||||
title: User Engine Evaluation Readiness
|
||||
status: planned
|
||||
priority: high
|
||||
path: workplans/ITC-WP-0007-user-engine-evaluation-readiness.md
|
||||
depends_on:
|
||||
- ITC-WP-0004
|
||||
- ITC-WP-0005
|
||||
- ITC-WP-0006
|
||||
produces:
|
||||
- canon-side user-management evaluation pack
|
||||
- user-engine conformance questions
|
||||
- consumer workplan brief
|
||||
|
||||
- id: ITC-WP-0008
|
||||
title: Railiance Fabric Conformance Support
|
||||
status: planned
|
||||
priority: high
|
||||
path: workplans/ITC-WP-0008-railiance-fabric-conformance-support.md
|
||||
depends_on:
|
||||
- ITC-WP-0004
|
||||
- ITC-WP-0005
|
||||
- ITC-WP-0006
|
||||
produces:
|
||||
- fabric entity and edge capture criteria
|
||||
- visualization-oriented example mappings
|
||||
- consumer workplan brief
|
||||
|
||||
- id: ITC-WP-0009
|
||||
title: Repo Scoping Comparison And Extension
|
||||
status: planned
|
||||
priority: high
|
||||
path: workplans/ITC-WP-0009-repo-scoping-comparison-and-extension.md
|
||||
depends_on:
|
||||
- ITC-WP-0005
|
||||
- ITC-WP-0006
|
||||
produces:
|
||||
- repo-scoping comparison report
|
||||
- canon extension candidates
|
||||
- consumer workplan brief
|
||||
|
||||
- id: ITC-WP-0010
|
||||
title: CARING Kubernetes RBAC Benchmark
|
||||
status: planned
|
||||
priority: medium
|
||||
path: workplans/ITC-WP-0010-caring-kubernetes-rbac-benchmark.md
|
||||
depends_on:
|
||||
- ITC-WP-0003
|
||||
- ITC-WP-0005
|
||||
produces:
|
||||
- distinct benchmark workspace
|
||||
- Kubernetes RBAC assimilation
|
||||
- CARING validation stress test
|
||||
|
||||
Reference in New Issue
Block a user