Glossary

Note — The unit of work. A title, a kind, and a body of statements.

Statement — A passage of prose with references. In a Task, a statement defines a step to execute.

Reference — A link to a resource or person, or a declaration of an output or milestone that a step will produce.

Effect — What a step does with a reference: uses it as an input, produces it as an output, or transforms it.

Task — A note that performs work. Runnable.

Skill — A note holding a reusable method, and the rulebooks or extractions it depends on.

Report — A note that collects results from its sources once activated.

Form — A note that asks for values. Compiles no steps.

General note — Authored prose. Seraa keeps one per day as your daily note.

Activation — Checking that a note's body holds together and sealing that version, so runs are held to it.

Run — A record of work against an activated note: a Task execution or a Form response. Task runs track steps, results, and handoffs.

Handoff — A step that needs a person — an approval, a signature, an answer. The run waits there until they respond.

Rulebook — A block of review standards. Author it in a Skill or General note using the editor, or ask the assistant to author it on a Skill or Report. Tasks reference the block.

Extraction — A set of data points to pull out of documents. Defined and referenced the same way as a rulebook.

Command — A / action run from inside a note. Happens once, leaves a receipt, and never becomes part of a run.

Receipt — The line a command leaves behind, recording what was asked and what happened: pending, ok, failed, or unknown.

Section — A ## heading and the statements under it. The sections are the note's shape.

Role — A person a step needs who has not been named yet, written [@Lead Counsel].