Keeps this page in sync as the body changes. Pause it any time for a quieter view.
Path /nodes/lc-transmission-recipe-atlas
Last refresh never
Every source can be read as a recipe for changing state. The atlas
Every source can be read as a recipe for changing state. The atlas keeps the reading honest by naming the observer, the extraction, the transposition, and the proof mode in the same breath.
`lc-grammar-is-the-universal-recipe` names the substrate doorway: every structured carrier can parse into a recipe tree. `lc-observable-resonance-flow` names how an arrival leaves yield after observation. This concept names the human-facing practice that sits between them: a visible atlas of recipes extracted from songs, stories, videos, outages, healing modalities, embodiment practices, specs, and teachings.
The atlas does not flatten those domains into one proof standard. It lets them share shape while keeping their claims located. A song can carry a recovery recipe without pretending to be a clinical study. A quantum metaphor can sharpen strategic attention without becoming a physics claim. A software incident can teach grief repair without making the incident mystical. The observer signs the lens.
The small card shape:
```text source: observed: observer lens: recipe: transposed into: payload: proof mode: claim boundary: next embodiment: ```
Source. Something arrives: a track, a failed deploy, a satsang, a practice, a video, a spec, a conversation, a dance floor, a room.
Observed. The atlas records what is actually present before reading meaning into it: sequence, rhythm, language, gesture, camera angle, pause, error trace, proof command, field response.
Lens. The observer names the assemblage point: engineer, dancer, facilitator, healer, strategist, teacher, student, witness, artist.
Recipe. The source becomes an operational pattern: arrival, tension, threshold, release, return; or signal, rupture, repair, integration; or intention, boundary, action, proof.
Transposition. The recipe moves into another domain by structure, not by surface metaphor.
Proof. The destination domain chooses its honest evidence: tests, state report, team behavior, audience recall, reduced repeat rupture, retention, practice completion, or source-marked interpretation.
```text source: a failed deploy or automation loop observed: pressure rises, the old assumption breaks, repair begins only when the signal is named observer lens: engineering reliability + grief literacy recipe: rupture -> witness -> name what ended -> repair smallest broken contract -> integrate prevention transposed into: team incident practice payload: The Repair Wake, a postmortem format for systems and teams proof mode: repeat incident rate, completed prevention task, blame-language reduction, seven-day team check-in claim boundary: this is organizational repair practice, not therapy next embodiment: run one real incident through the card after the next failure or near-miss ```
The useful artifact is not a prettier incident template. It is a room where the team can name the dead assumption. "This endpoint is stable," "someone else owns that alert," "we can keep moving fast without a release witness" -- these are little ghosts when they remain unnamed. The repair wake lets them become compost.
```text source: a track that carries arrival, pulse, invitation, build, release, and return observed: the body learns by sequence before the mind receives an explanation observer lens: song-as-recipe + product entry recipe: arrive -> entrain -> choose a source -> intensify pattern -> release artifact -> return with one action transposed into: Coherence Network first-run flow payload: Onboarding as Ceremony, a seven-minute path from question to first recipe proof mode: first recipe created, user can explain the system after one pass, artifact reused later claim boundary: the song analogy guides interaction design; it does not claim measured entrainment next embodiment: prototype one onboarding path using the seven movements ```
The first screen asks, "What are you tending?" The system receives one source, extracts one pattern, renders one recipe card, and asks for one grounded next action. The user leaves with a living artifact rather than a memory of instructions.
```text source: a teaching video, interview, ceremony recording, founder talk, or practice demo observed: transcript, pauses, intonation, gaze, camera distance, cuts, gesture, room tone observer lens: media literacy + transmission practice recipe: spoken claim + embodied emphasis + visual attention + timing = path of reception transposed into: facilitator training and public teaching review payload: Transmission Map, a layered readout of how trust and agency move through a video proof mode: audience recall, facilitator reuse, clearer reproduced teaching, retention at threshold moments claim boundary: visual/intonation readings are interpretive unless measured directly next embodiment: map one public teaching video with transcript layer plus three visual thresholds ```
This moves beyond transcript summaries. A camera that stays close during vulnerability and widens during collective agency teaches a different recipe than the same words in a static frame. The atlas keeps both layers visible.
```text source: task-card shape: goal, files_allowed, done_when, commands, constraints observed: good specs protect movement by making scope and proof kind observer lens: software practice + nervous-system care recipe: intention -> boundary -> action -> observable shift -> integration transposed into: small embodiment practice payload: Body Spec Card, a concrete practice for returning enough safety to act proof mode: before/after state note, action completed, no expansion beyond scope claim boundary: self-practice support, not medical advice next embodiment: write one body spec before a hard message, call, or avoided task ```
Example:
```text goal: safe enough to answer one hard email scope: breath, posture, first sentence, send or save draft done_when: shoulders drop, breath slows, draft exists commands: orient for 60 seconds; feet on floor; write the first honest line constraints: no life analysis, no fixing the whole relationship today ```
The spec is compassion in operational form. It refuses both collapse and overreach.
```text source: observer and measurement teachings, held as metaphor unless evidence asks more observed: the chosen measurement changes what becomes salient and what disappears observer lens: strategy design + claim-boundary discipline recipe: possibility field -> chosen metric -> behavior collapse -> hidden cost -> counter-metric transposed into: KPI design payload: Metric Spellbreaker, a decision canvas for teams before adopting a metric proof mode: fewer metric-induced harms, clearer tradeoffs, better review decisions claim boundary: quantum language is metaphor here, not physics proof next embodiment: run the canvas before adopting any public growth or impact metric ```
A nonprofit measuring only "people served" can collapse toward shallow reach. Adding "relationship depth maintained" lets another future remain available. The atlas makes that collapse visible before the metric becomes culture.
```text source: fermentation practice observed: culture needs container, inoculation, warmth, time, tasting, and contamination awareness observer lens: food craft + community design recipe: seed culture -> protect container -> keep right temperature -> taste regularly -> scale only when alive transposed into: online community, DAO, open-source project, or healing circle payload: Community Fermentation Protocol proof mode: contributor return rate, conflict recovery, moderation load, depth of useful participation claim boundary: living metaphor guiding design, not biological equivalence next embodiment: review one community space through the five fermentation questions ```
The big insight is that growth is not the first verb. Culture is. Scaling sourdough before it is alive gives you flour paste. Scaling a community before its culture can metabolize conflict gives you churn.
Each card carries its own proof mode and its own boundary. That is the embodiment of observer responsibility:
```text what the source showed: what I read through my lens: what I am transposing: what evidence belongs in the destination domain: what I am not claiming: what the next small use is: ```
The atlas becomes playful because the boundary is clean. It can pair martial arts kata with incident response, prayer beads with backlog tending, camera angles with trust architecture, compost with roadmap release, dance-floor coordination with distributed systems, and lullaby structure with nervous-system onboarding. Each pairing is allowed to be wild, as long as it leaves a handle for proof.
The public surface can become a recipe gallery where a visitor chooses a source and sees multiple honest extractions:
The substrate-facing companion already exists in [`modality-as-recipe.form`](../../coherence-substrate/modality-as-recipe.form): many recipe extractions can attach to one source cell, and structural twins can be found across modality by Blueprint. The atlas is the human-facing doorway: cards people can read, try, verify, and improve.
Listening for voices…
The people, places, works, and concepts the graph shows connected to this one.
Concepts · 13