The .yawn file
A small beginning can grow into a connected, inspectable operating record.
On this page
What the file carries
A .yawn file is an inspectable record. Existing files can carry identity and source links, language and qualifications, open questions, possible moves, proof conditions, boundaries, and history. Some use frontmatter and prose; specific consumers also validate a typed payload.
The filename does not make arbitrary prose executable. Behavior comes from the application that reads the record: its parser, projection, interface, and authorized operations. This guide and the proof game each read a deliberately public, fixed source record.
Leave what is unknown open
A seed may begin without answered questions. Missing semantic values should stay absent or explicitly unresolved until there is support for them. An empty string, null, an empty list, zero, and false are not interchangeable meanings.
An empty local container still needs whatever identity and envelope its consumer requires. A readable zero-byte file does not automatically pass the repository contract validator, become a saved Company, connect to intelligence, or obtain permission to act.
- Not recorded, not disclosed, unavailable, and known absent describe different situations.
- A proposed answer stays a proposal. A disputed claim does not become settled through inheritance.
- There is no universal minimum or maximum file size: each consumer defines its own validation and limits.
Keep the words and their standing
Retain attributable language, exceptions, uncertainty, disagreements, and corrections. A concise projection can make the interface useful while keeping the supporting source inspectable.
Linked context carries its origin and scope. A child does not inherit truth, consent, or authority just because it sits under a parent. Missing permission grants nothing.
A draft is different from an operation
Company's name is trimmed and limited to 1–180 JavaScript string code units. Description and goal each accept 1–4,000 code units, reject blank expressions, and retain the original words and whitespace. Optional boundaries, off-plate, keep, requirements, proof, and resources can remain empty. These are Company operation limits, not a limit on the expressive size of .yawn.
The cognitive-container runtime is a deterministic local domain contract. That contract alone does not prove cross-session storage, live agent ingress, or a deployed service. Each runtime must supply its own evidence.