Scenarios
Each of these is played through a real core as a test, the way its sources would report: records over HTTP, files through the probe, the clock moved by hand. The numbers come from those tests.
Each asks the two questions — what needs me, and what does it mean in money — and the hand-over, the Brief.
A freelancer’s office
Section titled “A freelancer’s office”Nothing here is infrastructure.
Sources: a Beancount ledger (the books), a todo.txt (the duties), a CSV exported from a spreadsheet (contracts, the depreciation of a laptop).
| Question | Answer |
|---|---|
| What needs me? | The VAT return, marked important and six days late (critical); an invoice overdue since 22 October (warning). |
| What about the money? | Brandt brings 1,200.00 EUR, costs 35.49, balance 1,164.51. Miller owes 2,400.00 USD. The office costs 516.64, including the laptop’s depreciation. |
| The Brief | “Write a friendly payment reminder to Miller Ltd: 2400.00 USD, due …” |
| Ticking off | A payment booked in the ledger, an x in todo.txt — and Nota follows. |
Three files met on one thing: the client’s name came from the spreadsheet, the retainer was declared there, the server was booked in the ledger. No source knew of another.
A homelab
Section titled “A homelab”Sources: an agent on a host, two probes outside, a nightly job.
| What happens | What Nota shows |
|---|---|
| One probe sees a failure, the other does not | a warning, not an alarm |
| The disk fills | critical, from a number and a threshold |
| The host dies | the host is the cause; the service on it is shown as a consequence and pages nobody |
| The backup does not run | noticed without anyone reporting a failure |
| It comes back | everything resolves by being reported again; no acknowledging, no closing by hand |
An AI process
Section titled “An AI process”Every step costs something else.
Source: the process itself, reporting its steps as events.
| Question | Answer |
|---|---|
| What did it cost? | 22.10 USD itself, 24.80 with its nightly evaluation. Tokens are priced by the configuration; a tool call brings its own price. |
| Does it pay? | 57 solved tickets at 0.40 brought 22.80 USD: the client’s process runs at −2.00. |
| A step fails | Critical; the Brief carries the model and the ticket the step knew. |
| The evaluation silently stops | Noticed after a day and an hour. |
A small agency, per client
Section titled “A small agency, per client”Sources: an inventory, and monitoring that speaks about services and servers and never about clients.
| Question | Answer |
|---|---|
| What does this client cost and bring? | Brandt +254.51 EUR, Miller +587.60 USD, side by side. |
| Is my client all right? | Brandt: critical, one cause and one consequence. Kaya: all clear, a certificate coming due. |
| A server two clients share fails | For the agency one cause with consequences; for each client, the thing that is wrong. |
A project run by a way of working
Section titled “A project run by a way of working”Source: one file — the template “app development”, copied, cut to size and given a start date.
- Template: steps with “after which step” and “offset”, and in
summarywhat done means. - Customise: copy it, delete steps and add your own.
- Make it concrete: the project, its name and client in the first row, a date on the first step.
- Use it as a source: every step is a deadline on the project.
| Question | Answer |
|---|---|
| What is ahead? | The client’s line shows the concept in 14 days and its invoice after it. |
| The concept slips | A warning three days before; the Brief says what done means. |
| It is done four days late | Every step after it moves by four days. |
| The invoice | Planned until the milestone is done, owed from that day, booked on the client when paid. |
The Brief of a step says what done means — that is the hand-over to a coding agent. How to set this up: plans from a template.
What the scenarios did not need
Section titled “What the scenarios did not need”No scenario needed a query language, a user, a role, or anything acted upon. Everything arrived as one of the record types, and the rules — threshold and absence — were enough for every “notice this” above.
Three things they left open: the widget shows cost only; what time changes, the core notices at its next tick, seconds later; and a plan knows no parallel people and no effort.