Meet Yawn
A little context. A useful next move. A way to see what changed.
What is Yawn?
Yawn helps you turn something you care about into a clearer situation, a chosen move, and a check on what happened. The character is your guide into that work. The record behind the character keeps the context, questions, choices, evidence, and corrections connected.
A Yawn can represent an inquiry, a game, a relationship, or a company. Its current interface is one way of working with that record. A different view should help you understand the same thing, without quietly changing its identity or permissions.
Start with what you have
You can begin with an idea, a question, or words you have not sorted out yet. A local seed can have no supplied semantic answers. More detail becomes useful as you understand the work; filling a large template is not the goal.
A saved operation has a more specific contract. For example, creating a Company requires a confirmed name, description, and starting goal. A blank draft and a committed company are different states.
Follow the loop
Understand the situation. Choose one move. Say what would count. Record what happened. Assess the result and decide what to keep, correct, or try next.
Yawn keeps those distinctions visible. A suggested move has not been chosen. A chosen move has not necessarily happened. A saved report is an attributed report; it does not automatically establish the larger goal.
Choose a useful view
The shared Yawn workspace opens its provisioned Interface, or your explicit retained view. Some commissioned experiences begin with a short Story. Questions and Model let you inspect the same source more closely.
This reference guide explains those experiences. The existing /docs surface remains a local orientation lab. Reading, searching, copying a page, or following an article does not run an AI model or authorize an action.