Implement infospace scaffold and service baseline
This commit is contained in:
parent
df6238c7e0
commit
9883a99f78
43 changed files with 35986 additions and 28 deletions
27
infospace/reports/scaffold-placement.md
Normal file
27
infospace/reports/scaffold-placement.md
Normal file
|
|
@ -0,0 +1,27 @@
|
|||
# Scaffold Placement Report
|
||||
|
||||
**Workplan:** ITC-WP-0001
|
||||
**Date:** 2026-05-23
|
||||
**Mode:** placement only, no semantic refactor
|
||||
|
||||
## Summary
|
||||
|
||||
The first implementation pass created the concrete `infospace/` root and
|
||||
placed the existing seed corpus into the newer `kernel/`, `models/`, and
|
||||
`standards/` layout. The original files in `seeds/` remain unchanged as
|
||||
provenance.
|
||||
|
||||
## Placement Rules
|
||||
|
||||
- Core and Kernel Map are copied to `infospace/kernel/`.
|
||||
- Broad domain models are copied to `infospace/models/<domain>/`.
|
||||
- Tagging and CARING are copied to `infospace/standards/<standard>/`.
|
||||
- `infospace/artifacts/index.yaml` records canonical path, kind, title,
|
||||
source seed path, and initial graph relationships.
|
||||
- No semantic edits were made to the copied documents.
|
||||
|
||||
## Deferred
|
||||
|
||||
- Domain-level profile extraction remains in ITC-WP-0004 and ITC-WP-0006.
|
||||
- Generated views and stricter validation remain in ITC-WP-0003.
|
||||
- Consumer repository workplans remain owned by the consumer repositories.
|
||||
Loading…
Add table
Add a link
Reference in a new issue