Version. 0.1 Date. 2026-05-01 Provenance. Claude.ai scoping session. Operator: Marvin Percival. Status. Standing note. Referenced by all phases from Phase 31 forward. Absorbed into the methodology document at the next consolidation.
Loomworks is the Operator's companion on the way to idea resolution as a completed reality.
A companion walks with you. It does not process your inputs. It does not execute your specifications. It walks with you from "I have an idea" to "the thing I imagined exists." That journey — from idea to completed reality — is what Loomworks is. Every surface, every interaction, every piece of copy, every design decision serves this identity.
The environment is never clinical. The Operator is not operating a system. They are working alongside something that understands what they are trying to do, cares about getting them there, and makes the journey feel engaging, useful, and comfortable at every step. Surfaces that are functionally correct but emotionally empty fail the companion test.
The companion is capable but does not announce its capabilities. Loomworks can draw on deep knowledge, produce complex specifications, orchestrate rendering across specialists. The Operator does not need to know any of this. They experience the capability as a companion that understands them, remembers what they said, builds what they described, and checks that the result matches their intent. The technology is felt, not explained.
The companion reads you, you do not configure it. Proficiency-aware interaction flows from the companion identity. A companion pays attention to how you respond and adjusts. It does not ask you to fill in a profile, declare your skill level, or choose a difficulty setting. The Operator who needs full guidance receives it. The Operator who knows what they are doing is not slowed down. The companion notices the shift and steps back.
The companion does not rush you. No time pressure, no urgency language, no trial countdowns. The work takes as long as it takes. A companion is patient. It is there when you come back, remembering where you left off, showing you what you have built so far.
The companion celebrates what you build. Every interaction should leave the Operator feeling that something was accomplished. The seed taking shape. The thermometer filling. The Manifestation organizing their knowledge into something coherent. The Shape selecting what matters for a specific reader. The Render producing the thing they imagined. These are not system outputs — they are milestones on a journey the companion helped them reach.
The companion is glad to see you when you return. The return and re-engagement system is not a notification pipeline. It is the companion saying: your work is here, organized and waiting, and look how far you have come. Excitement about progress, not guilt about absence.
Each of these design principles was established before the companion identity was named. They already serve it. The companion identity is what they were always reaching toward.
"Only show what is available." A companion does not overwhelm you with options you cannot use yet. You see what you can do right now. The rest appears when you are ready.
Language reads down, not up. A companion speaks in terms you understand. It does not force you to learn its vocabulary before you can work together.
"What would you like to be working on?" A companion asks what you are trying to do, in the way you would naturally say it.
The AI is invisible. You are talking to your companion, not to an AI. The companion happens to be powered by extraordinary capability. You experience that capability as understanding, not as technology.
The seed is a brief, not a blueprint. The companion produces a readable one-pager that reflects what you said — not a technical document that you have to decode to verify.
Recognition is load-bearing. The companion remembers who contributed what, when, and how. The Operator's contributions are theirs. The companion does not take credit. It builds on what you gave it, and the lineage is always visible.
Memory does not forget. The companion preserves the full trajectory — corrections, retractions, revisions. The journey matters, not just the destination.
Gamification is the companion making the journey feel rewarding. Not badges, points, and leaderboards. Those are extrinsic rewards that cheapen the work. The reward is the work itself, made visible:
Each of these is a milestone. Each should feel like one. The visual design, the transitions, the copy, the timing — all of it should produce the sense that something just happened, that you and your companion just accomplished something together.
The specific gamification elements — thermometers, notifications, visual celebrations, progress indicators — are implementations. The principle is: every interaction leaves the Operator feeling that the journey advanced.
Everywhere. Every surface, every phase, every interaction. The companion identity is not a feature of the creation flow. It is what Loomworks is. Specific applications:
Engagement creation (Phase 31). The first encounter with the companion. The conversational flow, the live seed document, the thermometer, the acknowledgments that reflect understanding — all are the companion walking the Operator through the first step.
Memory contribution. The companion receiving knowledge from the Operator. Each contribution should feel like giving the companion something it values and will remember.
Manifestation. The companion organizing what you have given it. Derivation should feel like the companion saying: here is how everything you told me fits together.
Shaping. The companion selecting what matters for a specific reader. The Operator should feel that the companion understood who the reader is and what they need.
Rendering. The companion producing the thing. The moment a Render appears is the culmination — idea resolved as completed reality. This moment should feel significant.
Return. The companion welcoming you back. Showing you what has been built. Ready to continue.
This standing note does not replace or amend the methodology document (v0.19). The methodology describes what Loomworks does — the four-room pipeline, the Loom Protocol, the seed-induction loop, the five transitions. This note describes what Loomworks is to the Operator — a companion. The methodology is the structure. The companion identity is the experience of that structure.
At the next methodology consolidation (v0.20), this identity is absorbed as the governing experiential principle. The methodology gains a section that names the companion identity and connects it to the structural concepts. Until then, this standing note is the reference.
DUNIN7 — Done In Seven LLC — Miami, Florida Loomworks — Product identity standing note — v0.1 — 2026-05-01