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> |
||
|---|---|---|
| .. | ||
| README.md | ||
incoming/
Drop zone for raw, un-reviewed material proposed for absorption into InfoTechCanon: external standards, vocabularies, product schemas, internal drafts, and their machine-readable companions.
Rules
- Files land here unedited and stay unedited.
- No canon artifact may reference a path under
incoming/— nothing here is part of the canon. - This directory is expected to be empty after a processing session. Anything left here is unprocessed backlog.
Processing
Follow infospace/assimilation/intake-and-assimilation-practice.md. In short:
git mv the input into infospace/assimilation/<slug>/source/ as a frozen
snapshot, produce the assimilation workspace, record a disposition, and — if
adopted — transform it into a canon artifact and cut a new canon version with
notes in CHANGELOG.md.
If an input is a need rather than a body of knowledge, it belongs in demand/
with a workplan, not here.