# 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.
`history/` and `seed/` stay unchanged as the record of origin.

## Documents

| Document | Status | Source (line ranges refer to `history/20261011-InitialExploration.md`) |
|----------|--------|-----------------------------------------------------|
| [GenerativeAssemblySocietyConcept.md](GenerativeAssemblySocietyConcept.md) | v0.1 (promoted verbatim) | `seed/GenerativeAssemblySocietyConcept.md` |
| [AdaptiveInformationProcessingNetworkConcept.md](AdaptiveInformationProcessingNetworkConcept.md) | v0.1 (extracted; terminology edited) | lines 857–1739 |
| [Glossary.md](Glossary.md) | v0.1 | reconciles the two concept documents (ASSEMBLY-WP-0003-T04) |
| [MembraneModel.md](MembraneModel.md) | v0.1 (promoted verbatim, two parts) | lines 1747–2065 (IT integration), 2882–3203 (membrane as filter) |
| [SeedKernel.md](SeedKernel.md) | v0.1 (promoted verbatim) | lines 2070–2437 |
| [EvolutionModel.md](EvolutionModel.md) | v0.1 (promoted verbatim; terminology edited) | lines 2442–2877 |
| [MetabolismModel.md](MetabolismModel.md) | v0.1 (promoted verbatim) | lines 3208–3775 |
| [ResourceOntology.md](ResourceOntology.md) | v0.1 (promoted verbatim) | lines 3780–4263 |
| [NetworkObjectModel.md](NetworkObjectModel.md) | v0.1 (new; 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, including the originating question. Consolidation
  and edits happen in later commits, so the diff shows every change against the
  original.
- Cross-lens alignments are added as an appendix ("Cross-lens notes") so the
  promoted body stays intact.
- 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.