Skip to main content
T4 epic · founders / executives: the flagship. Three branches gather in parallel (web signal, repo pulse, the KPI sheet), jq does the revenue arithmetic, a local model writes the brief, and one human decision at the root authorizes the whole run. It is also the smallest complete example of the lethal trifecta: private numbers, untrusted news and an outbound ping, held by that one gate.

The job

Monday needs one page: market, product, numbers, risks, the ONE decision. Assembling it eats an hour of founder time. This file assembles it in one run: a dated filename, revenue summed by jq rather than guessed by a model, and an optional founders ping that says whether the brief landed.
Limit on macOS in 0.124.3. The sandbox confines exec: git to the workflow’s declared filesystem boundary, which grants no read of .git or of git’s global configuration. The confined git exits with status 128, even inside a real repository, so pulse takes its recover: value and the brief is told the engineering pulse is missing. See Known limits.

The shape

The file

ceo-monday-brief.nika

How it works

1

Three branches, zero coordination code

News (HN API through mode: jq), engineering pulse (git shortlog) and the KPI sheet (read → convert → jq add) run concurrently. The revenue sum is jq arithmetic: deterministic, not model-guessed.
2

Dates come from a builtin

nika:date + an extract: slice (day: ".[:10]") stamp the filename briefs/2026-06-15-monday.md. Never let a model guess the date.
3

One decision at the root

approve is a nika:prompt with no default:, and every effect re-reads its answer (when: ${{ with.go == true }}): a « no » fetches, reads and writes nothing. The boundary permits all three legs of the lethal trifecta, so the human decision sits where it governs every one of them (Security).
4

The ping fires on every outcome

alert rides after: { save: terminal } and reads ${{ tasks.save.status }}, so an armed ping reports a brief that landed, failed or was declined. It uses terminal and not unwind: a cleanup failure is only logged, and an alert that cannot fail loudly is not an alert.

Constructs you just used

Run it

What it needs: A local model (Ollama serving qwen3.5:4b), network access to hn.algolia.com for the market signal (offline, it recovers to a labelled stand-in), and the sample KPI sheet. The engineering pulse reads Git, which is refused on macOS in 0.124.3 (Known limits).
1

Rehearse it

A mock model answers, the sample files come with it, and nothing is written in your folder. Its network fetches still go out: a rehearsal replaces the model, not the tools. Before it runs, nika try names those hosts: may reach: hn.algolia.com · hooks.slack.com — the mock replaces the model, not the network. It stops at the approve gate, as a real run does.
2

Get your own copy

Save the file above as ceo-monday-brief.nika in a new folder, then download the sample it reads:
3

Check it, then run it

The run writes briefs/<date>-monday.md.It asks at the approve gate before anything else runs. On a terminal you answer; in a script it pauses (exit 4) and prints the --resume line that continues it, or you answer up front with --answer approve=true.Any other model works: pass --model <provider>/<name> with its key, and cap a cloud model with --max-cost-usd.The founders ping stays off unless you add --var alert=true with FOUNDERS_WEBHOOK_URL set; armed without it, the run fails at alert (NIKA-VAR-001).

Make it yours

  • Add a fourth branch: support sentiment from Support triage’s board file.
  • Keep a budget when you move the brief to a cloud model: run it with --max-cost-usd, and a run whose cost floor exceeds the cap refuses to start (NIKA-1709).
  • Archive the history: the dated files under briefs/ are already your decision journal.

Back to all examples

You’ve climbed the whole ladder, starter to epic. Time to write yours.