A third front door next to incoming/ and demand/: longitudinal PurposeFit evidence, not a change request and not a canon artifact. Seeded with the resource-control backup-cycle mapping. |
||
|---|---|---|
| .. | ||
| 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.
If an input is a report on whether existing canon concepts provided utility,
it belongs in feedback/, not here.