Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Assistant: claude-code Assistant-Model: opus Assistant-Process: 1494246@bnt-lap001 Assistant-Session: caf6de6f-f9e4-47ce-a584-49baa271fa4b
1.5 KiB
1.5 KiB
Canon
Normative conceptual documents for assembly-economics. Each document is
promoted from exploration material in history/ and then evolves on its own.
The history files stay unchanged as the record of origin.
Documents
| Document | Status | Source in history/20261011-InitialExploration.md |
|---|---|---|
| ConceptualCanon.md | v0.1 (extracted verbatim) | lines 857–1739 |
| MembraneModel.md | planned (ASSEMBLY-WP-0002-T03) | lines 1747–2065 (IT integration), 2882–3203 (membrane as filter) |
| SeedKernel.md | planned (ASSEMBLY-WP-0002-T04) | lines 2070–2437 |
| EvolutionModel.md | planned (ASSEMBLY-WP-0002-T05) | lines 2442–2877 |
| MetabolismModel.md | planned (ASSEMBLY-WP-0002-T06) | lines 3208–3775 |
| ResourceOntology.md | planned (ASSEMBLY-WP-0002-T07) | lines 3780–4263 |
| NetworkObjectModel.md | planned (ASSEMBLY-WP-0002-T08) | derived from ConceptualCanon.md § 53 |
Conventions
- Every document opens with a provenance comment that names its source lines and the task that created it.
- Promotion is verbatim first. Consolidation and edits happen in later commits, so the diff shows every change against the original.
- Version is stated in the document header (
v0.1,v0.2, …). Bump it on normative changes, not on wording fixes. - Implementation-specific material (storage, protocols, APIs) stays out of the canon, as ConceptualCanon.md § 52 requires.