Source, runtime, and authority
How the existing pieces connect, and what each one can establish.
On this page
From a source to an interface
A source record carries authored context. A consumer validates the parts it understands. A projection presents that record as questions, an interface, a Story, a paper, a graph, or a model. The existing public catalog connects explicitly registered public coordinates to their useful destinations.
This documentation follows that pattern: a fixed public .yawn payload supplies the articles; the server validates it; the interface provides local search and links. The Explore links below resolve only this guide's curated coordinates through the existing public catalog.
authored source → validated record → authorized projection → useful interface
↓
explicit choice → bounded operation → receipt → reviewFiles and canonical state have different jobs
A public .yawn contract describes product behavior and its boundaries. Private Company facts are stored in the canonical owner-bound orientation stream and projected only after authorization. A browser draft, a committed event, and a derived view are different artifacts.
The local cognitive-container contract joins identity, state, messages, permissions, proof, and replay in a pure aggregate. A local contract or passing unit test does not establish that a database migration, durable broker, or automatic agent connection is deployed.
Scope survives the links
Each canonical Yawn has at most one primary parent. Reference links and visual proximity do not create containment. Accepted inherited context retains its origin, scope, revision, and provenance; a descendant may narrow privacy or authority, while widening needs an explicit rightful grant.
The protocol lock pins exact upstream .yawn artifacts. Sync verification checks those artifacts; it does not deploy software, apply a database migration, or activate an agent. An implementation claim needs its own runtime evidence.
Keep the boundary useful
A view switch changes presentation. A saved source preserves an attributable record. A connection response establishes a current metadata check. A committed operation has a scoped receipt. An observed result supports a specific claim.
Tie those pieces together before adding another system. Reuse the current record, composer, catalog, grants, operation, and receipt loop where they already fit. If an interface is not provisioned or evidence is unavailable, leave that limit visible.
The experience vocabulary
Game gives the larger activity its meaning; its menu also helps you navigate the authorized parent, children and related Yawns. Quest names the bounded outcome being pursued. Level describes the actual work phase where a loop applies: Company uses Orient, Act and Learn. Viewing Learn does not complete the work.
Mode is how you engage with the same subject, such as Story, Model, Graph, Documentation or Research paper. Focus is the aspect you inspect, such as Purpose or evidence. Type is the semantic record contract, usually available through Inspect .yawn.
Projection is the authorized representation resolved for you. Expression is its concrete rendered form. Vibe shapes Guidance, Detail and Energy; Density describes spacing. Scene selects an available visual setting. An obstruction is a relevant missing condition or boundary. None of those presentation choices grants permission or changes shared facts.
Your experience can follow you
An explicit entrance or current choice wins, followed by a valid selection restored for this coordinate and tab. Explicitly saved participant defaults then supply how you prefer to engage, before an entrance policy or configured Interface. An unconfigured interface leaves the missing capability visible and offers permitted inspection.
Changing a view is local and reversible. Save as my default explicitly retains Mode and Guidance, Detail and Energy through the existing account preference ledger. Those numbers describe the encounter, not your personality. A reaction such as boring does not silently become a new preference.
The current participant receives effective preference values without private conversations, source explanations or preference identifiers. Dave and Brody can experience the same company differently while sharing the same underlying facts. Scene and Focus remain local choices in this first preference extension.
When an expression is missing
Selecting Documentation for a context keeps that selection even when its content has not been computed. Compute expression is an explicit request to produce a bounded, attributed representation from the currently authorized source. Navigation and ordinary view switching do not run a model.
Current, missing, stale, running, failed, uncertain, unsupported and denied are different states. A source or dependency correction makes the old expression stale; reading its request status never restarts inference. A late result cannot pull you back from a newer selection.
The first computed-expression contract produces validated text sections with source references and limits. It uses the existing main intelligence and durable run ledger; Jev remains the typed judgment capability. It does not produce arbitrary executable UI, new scene artwork or proof of the claims it describes. The local implementation requires its matching database migration and release verification before a live capability is claimed.
Give a correction the right destination
That explanation missed the point can mean the expression needs correction, the recorded Purpose needs correction, or both. Yawn must preserve your words and the chosen destination; it cannot infer a semantic edit from a negative reaction or a different Mode.
An explicit canonical correction follows the existing command and receipt boundary. Dependent expressions can then be checked against the revised source. Whether the new presentation helped and whether the next action achieved its intended result are separate observations.
A small thought can remain small. It does not need a Game, Quest, Level, cube and proof condition merely to exist. The consumer determines which envelope and values are required; absent information remains absent.