Shape type: Education Shaping: Methodology concepts for newcomers Against Manifestation: v1 (15 assertions, #1–#15)
An accessible introduction to Loomworks for a person encountering the system for the first time. Covers what the system is, how knowledge works inside it, and how to participate.
Seven concepts, each a self-contained explanation:
Temporal (primary): concepts ordered from simplest to most complex. The reader encounters engagements first (the container), then Memory (what accumulates), then contributions (how knowledge enters), then the pipeline stages in order (Manifestation → Shaping → Rendering). Each concept builds on the previous.
Proportional: Memory and contributions receive the most space (approximately 40% combined) because they are what the newcomer will actually do. Manifestation, Shaping, and Rendering receive less space (approximately 40% combined) because the newcomer observes them but doesn't operate them. The engagement concept and provenance receive the remaining 20%.
Contributions produce assertions. Assertions accumulate in Memory. Memory is organized by Manifestation. Manifestation is selected by Shaping. Shaping is produced by Rendering. Each stage depends on the previous — you cannot explain Shaping without Manifestation, and you cannot explain Manifestation without Memory. The ordering is not arbitrary; it is the dependency chain.
Provenance connects to contributions: when a person contributes, the system records who, when, and how automatically. The newcomer needs to understand this because it means they do not need to explain their own lineage — the system handles it.
Each concept explanation is 80–150 words. Total specification: 700–1,000 words. Reading level: accessible to a person with no technical background, no knowledge of the methodology, and no prior exposure to Loomworks. No abbreviations. No jargon. Where a methodology term is used (assertion, engagement, Manifestation), it is defined in the same sentence it first appears.
The concept of "engagement" must be established before "Memory" (Memory belongs to an engagement). "Memory" must be established before "contribution" (contributions enter Memory). "Contribution" must be established before "provenance" (provenance is a property of contributions). "Memory" must be established before "Manifestation" (Manifestation organizes Memory). The full pipeline sequence (Memory → Manifestation → Shaping → Rendering) must follow these individual concept introductions.
| Concept | Source assertions | |---|---| | What an engagement is | #2 (revised, v4) | | What Memory is | #1 | | Contributions and provenance | #6, #7, #8 | | What a Manifestation is | #13 | | What Shaping is | #14 | | What Rendering is | #15 | | How provenance works | #7 (automatic provenance), #1 (Memory records who, when, how) |
Excluded assertions and reasons:
| Assertion | Reason for exclusion | |---|---| | #2 (partial) | Pipeline detail at technical depth — simplified version used | | #3 (designations) | Operator/Contributor distinction is a system-governance concept, not a newcomer concept | | #4 (seeds) | Seeds are an Operator concern; the newcomer contributes, not creates engagements | | #5 (contribution as compounding) | The compounding thesis is philosophy, not orientation | | #9–#12 (contribution guidance) | Practical guidance for contributors — relevant but a separate shape type (a "how to contribute" guide, not a "what is Loomworks" introduction) |
Every person who creates a Loomworks account. This is the broadest possible audience — no assumed expertise, no assumed context, no assumed motivation beyond "I just signed up and I want to understand what this is." The reader may be a domain expert in their own field (a geologist, a banker, a farmer) but is a complete newcomer to this system.
Rendered for the engagement overview surface within Loomworks. The reader encounters this within the product, not as a standalone document. Format: structured text (markdown or HTML), rendered inline in the UI. Not a PDF, not a slide deck, not a standalone document.
An educational introduction follows concept-ladder grammar: simplest concept first → each subsequent concept builds on the previous → the reader ascends from "what is this place?" to "how does the full pipeline work?" without any step requiring a leap. The ladder has no gaps — every rung connects to the one below.
Within each concept: definition first (one sentence), then elaboration (what it means in practice), then an everyday analogy if the concept is abstract.
Read once during the newcomer's first encounter with the system. Skimmed on return visits if the newcomer needs a refresher. The content is reference material, not interactive — the reader reads, absorbs, and then participates. The successful outcome is that the reader closes the explanation and contributes their first assertion without confusion about what Memory is or where their contribution goes.
Education Shape — Loompa-structured — against Manifestation v1 (assertions #1–#15)