Architecture Source Archive

Status: reference-only source snapshots, preserved 2026-09-11. These are architectural provenance, not the active build specification. Start with the current authority map.

The four documents below contain substantial architecture developed before the rework. They are not disposable marketing-platform legacy. Their useful decisions, rationale, examples and constraints have been incorporated into canonical successors; each original is retained without byte changes.

| Preserved source | Active destinations | |---|---| | 00 combined handoff | Corresponding product, technical and MVP successors below; the combined source is not another editable authority. | | 01 product and principles | Product, capabilities, objects/types, retrieval, evolution. | | 02 technical architecture and data | Canonical documents reached through the architecture map, not independent definitions in the map itself. | | 03 engines, workflows and MVP | Roadmap, capability scenarios, knowledge, workflows, evolution. |

The source ledger records exact source-section destinations, SHA256 hashes and old-document dispositions. All three standalone texts occur in the combined document; only its title/version/introduction and separators are additional wrapper material. Different source version labels and repeated section numbers are preserved as historical facts, not repaired in the snapshots.

Where source text and current canonical prose differ, apply the current specification and human clarifications. In particular, do not treat engine lists as fixed software modules, read the old "core primitives" list as multiple foundational models, or use provisional examples to resolve open decisions. Archive contents are excluded from normal agent build routes.

The obsolete marketing-platform documentation is not copied here wholesale. Compatible lessons are in active implementation documents and selective legacy reference; superseded paths are explicitly recorded in the ledger.