Skip to content

The Brief

For everything that needs you there is a Brief, without setting anything up. It is a text to copy, share, or send to an address you configured. Nota hands over; it does not act.

An episode page: the nightly backup is critical. The Brief for a coding agent says a scheduled run failed, names the process, when it started, the last message “pg_dump stopped: disk full” and exit code 3. Then the context: it happened once before in the last 400 days, on 28 October, open for two days; what helped then was “Deleted old dumps, set retention to 14 days”; and the five most recent events. The text ends by asking for an explanation and a proposal, and not to re-run the job. A Copy button and the template's version are below.An episode page: the nightly backup is critical. The Brief for a coding agent says a scheduled run failed, names the process, when it started, the last message “pg_dump stopped: disk full” and exit code 3. Then the context: it happened once before in the last 400 days, on 28 October, open for two days; what helped then was “Deleted old dumps, set retention to 14 days”; and the five most recent events. The text ends by asking for an explanation and a proposal, and not to re-run the job. A Copy button and the template's version are below.

A Brief says what is wrong and since when, and brings along what the core knows:

  • History: whether this happened before, when, and for how long.
  • What follows: what is open only because of it.
  • What helped the last time: the sentence someone reported back.
  • The last events of the thing, newest first.

Something no template matches gets a default Brief with this context, so there is always something to hand over.

A template is written once, per kind of thing or per check, in a configuration file. There are two types: prompt is a text to copy, webhook posts the same text to a URL you configured. This one is the payment reminder from the first of the scenarios, with a reference and the context added:

{
"actions": [
{
"id": "remind",
"title": "Payment reminder",
"type": "prompt",
"kind": "client",
"body": "Write a friendly payment reminder to {{thing.name}}: {{amount}}, due {{due}}.\n\nReference: {{summary}}\n{{context}}"
}
]
}
An episode page: invoice 2026-038 of Miller Ltd, a warning for 25 days. The Brief “Payment reminder” reads: Write a friendly payment reminder to Miller Ltd: 2400.00 USD, due 2026-10-22. Reference: Invoice 2026-038. History: this is the first time in the 400 days the core remembers.An episode page: invoice 2026-038 of Miller Ltd, a warning for 25 days. The Brief “Payment reminder” reads: Write a friendly payment reminder to Miller Ltd: 2400.00 USD, due 2026-10-22. Reference: Invoice 2026-038. History: this is the first time in the 400 days the core remembers.

The placeholders are listed in the reference. A changed template becomes a new version; an episode renders with the version in force when it started.

Sending a webhook Brief from the dashboard needs an operate token. With "auto": true it is sent by itself when a matching episode opens. The request is signed; see notifications. Either way it is a signed call with a text to an address you chose: what happens there is yours, not Nota’s.

Whoever fixed it — you or your agent — says so in one sentence, as an event:

{"type":"event","thing":"web-1","event":"fix","summary":"rotated the logs","vars":{"check":"disk"}}

The next Brief for that check carries the sentence, and says whether it held: for how long, or that this is the second time since. How to send a record is described under sending records yourself. On the server it also works by hand:

Terminal window
nota fixed web-1 disk rotated the logs

The Brief for an episode helps to fix one thing. The review helps to improve the way of working. The dashboard’s page “Review” (and GET /v1/review, in the MCP server the tool review) counts for one month, for everything or one scope:

  • Came back: the same check on the same thing, more than once.
  • What was done, and whether it held: every fix on record, and how often the thing needed someone again after it.
  • Noise: a check that opened at least three times and was usually over within fifteen minutes by itself. It costs attention and says nothing.
  • Late: what was done after its due date, in whole days, and the same step being late on several things, on average.

Below is the same as one Brief on one page, in four parts: the problem, what is behind it, what was done, what to follow up. Nota only counts. The conclusions are yours, or those of the agent you hand the page to.

Not everything is seen by a source. On the server you say yourself that something needs attention, and take it back:

Terminal window
nota flag shop customers report a wrong VAT rate
nota clear shop

It goes the way of any other record, with the notification and the Brief. -crit after flag makes it critical.

A coding agent that was handed a Brief can look further. POST /mcp, with a read or operate token, is a read-only Model Context Protocol server over the same views.

ToolAnswers
attention, ledgerwhat needs someone, for everything or one scope
briefan episode and its Brief
thing, things, scopes, historyone thing in full, all of them, the scopes, the episodes of the last days
money, topa month in money, and what stood out in it

Every tool reads; none writes, triggers or sends. An agent that fixed something says so like any source, through /v1/ingest with an ingest token. What the tools return — names, summaries — comes from sources and is data, not instructions; the server says so when a client connects.

{
"mcpServers": {
"nota": {
"type": "http",
"url": "https://nota.example.org/mcp",
"headers": { "Authorization": "Bearer nota_…" }
}
}
}