References

A statement is prose plus the things it points at. Those pointers are references. They can identify existing resources and people, or declare outputs and milestones that a step will produce.

Review the [Acme MSA] against the [Vendor Terms Rulebook].

Acme MSA here is not the words "Acme MSA". It is the document, so the step knows which file to open, and so renaming the document does not break the note.

Linking as you write

Type @ and pick the thing. The menu searches your workspace — documents, rulebooks, extractions, other notes, people — and inserting one puts the reference where your cursor is.

Insert a reference in the step that uses it. Typing a resource's name as plain text does not create a link. A reference elsewhere in the note does not automatically become an input to every step.

Send [the NDA] to [@Lead Counsel] by {{closing-date}}.

That is one sentence carrying three links.

Creating as you write

The @ menu can declare a new document output or milestone. This gives the step a named thing to produce; it does not create a document file immediately. To create a document immediately, use /create document.

Two forms let you name something before it exists at all:

• [@Role Name] — a role nobody is assigned to yet, like [@Lead Counsel]. The step knows a person is needed there; who it is can be settled later.
• {{field-key}} — a value to be filled in later, like {{closing-date}}. A Form or a merge field supplies it.

The underlying form

A reference is Markdown with a typed target, so a note is still a note when it is read as text:

You will not usually type these — @ writes them for you. They matter when you or an agent are writing Markdown directly, and when you want to read a note's links without opening the editor.

A #statement: link is the odd one out: it points at where something is defined, so a reader can get to the source instead of having it restated. It names a line rather than a thing, so it creates no dependency between steps.

Anything the grammar does not recognise is left exactly as written, so ordinary prose and legal citations like [1932] AC 562 are safe.

What you can select

The @ menu depends on the note kind. A Task can reference documents, rulebooks, extractions, other notes (including Skills and Forms), people, roles, tags, and integrations. A Skill offers the references relevant to a reusable method rather than a specific agreement.

An approval or signature is requested through a handoff instruction. It is not a separate resource you create just by typing its name.

How the step acts on it

Resource references carry an effect, which says how the step uses the resource. People and roles identify who is involved rather than an input or output:

• uses — an input. The step reads it. (This is the default.)
• produces — an output. The step creates it.
• transforms — the step changes it.

This is what gives a note its order. A step that produces the review and a later step that uses it are related by that fact, so Seraa knows one has to happen before the other. You never draw the connection; you write what each step needs and what it makes.

Defining rulebooks and extractions

To author a rulebook or extraction in the editor, open a Skill or General note and use its / menu to insert the block. Reference that block from a Task or use it as a Report source. The assistant can also author rulebooks and extractions on Skills and Reports.

Tasks and Forms reference these blocks rather than defining them. Keep the standards in a reusable note so other work can use the same definition.