info-tech-canon/workplans/ITC-WP-0001-infospace-scaffold-and-seed-placement.md

id, type, title, repo, status, priority, created, updated, depends_on_workplans

id	type	title	repo	status	priority	created	updated	depends_on_workplans
ITC-WP-0001	workplan	Infospace Scaffold And Seed Placement	info-tech-canon	planned	high	2026-05-23	2026-05-23

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:

infospace/
  infospace.yaml
  artifacts/index.yaml
  kernel/
  models/
  standards/
  profiles/
  patterns/
  mappings/
  assimilation/
  schemas/
  views/
  agent/
  examples/
  validation/

Tasks

T01 - Create infospace layout

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

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

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

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.