Loomworks candidate seed — declared shape types draft
For. Insertion into candidate seed v0.5, between the "Public Memory by default" constraint and the "Declared render-types" section.
Date. 2026-04-28
Declared shape-types
Loomworks-the-engagement commits to produce the following shape-types. These are the intermediate shaped forms that sit between a Manifestation and the Renders that consume them. Each shape type selects and organizes material from Memory (through the current Manifestation) for a specific consumer class. Declaring them makes the selection stream explicit, parallel to what the declared render-types section does for the rendering stream.
Multiple render-types can draw from the same shape-type. The shape-type defines what material is selected and organized; the render-type defines what final-form artifact is produced from that organized material.
Build shape-types
These correspond to the material selections the engagement has been performing in practice throughout its construction.
- Phase execution context. Selects current-phase material from Memory: the methodology state bearing on this phase's work, the build state (substrate tests, frontend surfaces, git tags), scoping decisions made, residues carried, substrate endpoint shapes and response schemas relevant to the phase. Consumer: Claude as CR and scoping note drafter, CC as executor, Operator as reviewer. Source for render-types: phase change request, phase scoping note, phase handoff, phase implementation notes.
- Project state. Selects cross-cutting project state from Memory: the full inventory of phases completed, documents produced, vocabulary in force, residues open and resolved, named principles, git tags, test counts, frontend surfaces, document authority chain. Consumer: fresh Claude chats orienting to the project, Operator reviewing overall state. Source for render-types: project state manifest, standing note, infrastructure change request, engagement seed.
- Methodology narrative. Selects the methodology as a coherent body of knowledge: the pipeline (Memory → Manifestation → Shaping → Render), the principles, the vocabulary with its corrections and renames, the worked examples, the trajectory from earlier positions to current ones. Consumer: anyone needing to understand what DUNIN7 is building — future Claude chats, Operator, future implementers of the methodology. Source for render-types: methodology document, philosophy and architecture document.
- Discovery trajectory. Selects the path of a specific inquiry: positions considered, alternatives set aside and why, corrections that landed, moments where something new crystallized, the distinction between what was established knowledge and what emerged. Consumer: future methodology revisions, Operator reviewing how decisions arrived. Source for render-type: discovery record.
Commons shape-types
These serve the educational and community purpose, parallel to the commons render-types.
- Commons education. Selects methodology and system concepts from Memory and organizes them for accessibility: what each concept means in plain language, how it works, how to participate, what the system expects of Contributors. The selection criterion is approachability — material is chosen and organized so that a person encountering Loomworks for the first time can orient without needing to read phase CRs or methodology documents. Consumer: every person in the system. Source for render-types: concept reference, contributor guide.
Shape-type to render-type mapping
| Shape-type | Render-types it sources |
|------------|------------------------|
| Phase execution context | Phase change request, phase scoping note, phase handoff, phase implementation notes |
| Project state | Project state manifest, standing note, infrastructure change request, engagement seed |
| Methodology narrative | Methodology document, philosophy and architecture document |
| Discovery trajectory | Discovery record |
| Commons education | Concept reference, contributor guide |
Five declared shape-types source thirteen declared render-types. Every render-type traces to exactly one shape-type. Every shape-type sources at least one render-type.
Draft for Operator review — 2026-04-28