The next move comes from current company state, dependencies and the work that is actually ready.
Read the files before proposing work
profile.json describes the company. state.json holds current progress. The build map, ledger, dials and other local context establish what has happened, what is allowed and what is ready. The session should not re-invent those facts from memory.
/casa-next is a harness skill, not a shell executable. In a harness without native skill registration, read and follow the corresponding SKILL.md from the Casa checkout.
This opening read is what makes a session a continuation of the business. A previous decision may rule out an otherwise attractive task. An unfinished dependency may make a play unavailable. A department dial may change how execution proceeds. Those facts should shape the next move before an operator spends time producing a deliverable that cannot be used.
Produce and review a concrete artifact
The chosen operator works to a playbook’s deliverable and rubric. A Phase 0 product-flow play, for example, produces a Mermaid file in its own output directory. The review is about whether that artifact meets the contract, with evidence for its claims.
A file existing on disk is not sufficient reason to mark a play complete. Resolve review findings, keep the artifact path and relevant commitments in the recorded work, and obtain approval for actions that cross a gate.
Review the artifact in the context of the company, not just as a well-formed file. For a product flow, check whether its actors and transitions agree with the brief, whether failure paths are understandable and whether planned behavior is presented as planned. A syntactically valid diagram can still describe the wrong product.
When a review finds a gap, return to the deliverable with a specific correction. Keep unresolved findings open and distinguish a proposed action from an executed one. This creates a record that a founder or a later session can follow without guessing which parts of the work were actually accepted.
Record the result and understand the connection
The brain preserves state, events and decisions so the next session begins with the updated company. Ordinary local work does not need a public service. A bound integration has a separate continuing publication path, including a guarded SessionEnd hook.
The website’s operating examples use synthetic demo data. They illustrate a workflow, not a live customer transcript or measured business performance.
A useful handoff connects three things: the artifact path, the review outcome and the resulting company state. The next session can then see what changed and what remains ready to do. If an important business choice was made along the way, preserve its reasoning in the appropriate decision record rather than expecting an event entry to explain it fully.