You write notes. Some of them run.

A note is the unit of work in Seraa. It has a title, a kind, and a body: prose, references, and structured content suited to its kind. In a Task, each statement is a step written as an instruction plus the things it refers to — a document, a rulebook, a person.

Write the instructions in the note and use @ to link the resources they need.

Review the [Acme MSA] against the [Vendor Terms Rulebook].
Record the findings for [Maya].

The bracketed pieces are references. They are not text that happens to match a name. Pick existing documents, rulebooks, and people from the @ menu. You can also declare an output for a step to create.

What happens next

A Task must be activated before it can run: Seraa checks its structure, then seals that version. Choose Run and supply any missing people or values. Each run keeps its instructions even if you later deactivate and revise the note.

A run works through the steps and stops where a person is needed — an approval, a signature, an answer. It waits there until that person responds.

Where to go