The seed INTENT and the history-derived draft are merged into INTENT.md; seed/INTENT.md is removed as superseded. "Canon" is reserved for an established body of knowledge, so the exploratory material moves to concepts/ and ASSEMBLY-WP-0002 is retitled accordingly. 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
31 lines
1.8 KiB
Markdown
31 lines
1.8 KiB
Markdown
# Concepts
|
||
|
||
Exploratory concept documents for `assembly-economics`. Each document is
|
||
promoted from exploration material in `history/` or `seed/` and then evolves on
|
||
its own. These are working concepts, not an established body of knowledge. The
|
||
history files stay unchanged as the record of origin.
|
||
|
||
## Documents
|
||
|
||
| Document | Status | Source in `history/20261011-InitialExploration.md` |
|
||
|----------|--------|-----------------------------------------------------|
|
||
| [AdaptiveInformationProcessingNetworkConcept.md](AdaptiveInformationProcessingNetworkConcept.md) | v0.1 (extracted; terminology edited) | 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 AdaptiveInformationProcessingNetworkConcept.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
|
||
substantive changes, not on wording fixes.
|
||
- Implementation-specific material (storage, protocols, APIs) stays out of
|
||
concept documents, as AdaptiveInformationProcessingNetworkConcept.md § 52 requires.
|
||
- Do not call these documents "canon". That term is reserved for an
|
||
established body of knowledge.
|