Arm registry

arm: is the team registry of workflows the project proposes to fire. The file proposes. A machine edge disposes. Reading the file never schedules work.

One beat, complete

nika: v1

arm:
  - workflow: workflows/daily-brief.nika.yaml
    cadence: "TZ=Europe/Paris 30 7 * * 1-5"
    où: local
    plafond: 0.20
    manqué: rattraper-une-fois
    chevauchement: sauter
    après_saut: prochain-créneau
    par: operations

Key	Requirement	Contract
`workflow`	Required	Repo-relative `*.nika.yaml` path
`cadence`	Required	Readable schedule, TZ-prefixed cron, or `on-webhook`
`plafond`	Required	Positive per-tick USD ceiling
`manqué`	Required	`rattraper` · `rattraper-une-fois` · `sauter`
`où`	Optional	`local` by default · `cloud` as the declared remote locus
`chevauchement`	Optional	`sauter` by default · `file` for serialized overlap
`après_saut`	Optional	What follows an overlap skip
`actif` · `raison` · `jusqu_au`	Together	Auditable suspension state
`tolérance` · `décalage`	Optional	Declared tolerance and deterministic jitter lanes
`par`	Optional	Declared human, not machine authorization

plafond and manqué have no default. Choosing them implicitly would choose who pays or whether missed work is duplicated or lost.

Read before firing

nika arm

The report names each armed or suspended beat, its next slots, and whether a sidecar proves a previous fire. It ends by stating that nothing was scheduled.

DECLARATION IS NOT PROOF

Every door ends at one firer

nika arm fire <label> ─────┐
launchd / systemd unit ────┼── due window · miss · overlap · ceiling · ledger
nika serve ────────────────┘

This convergence matters. Changing how the project wakes up does not change the firing law.

Suspend with a reason

nika: v1

arm:
  - workflow: workflows/daily-brief.nika.yaml
    cadence: "TZ=Europe/Paris 30 7 * * 1-5"
    plafond: 0.20
    manqué: sauter
    actif: false
    raison: maintenance fournisseur
    jusqu_au: 2026-09-01

Deleting a row leaves no durable explanation. The suspension triple states that the beat is inactive, why, and until when.

Continue

Resident server

Keep the project clock alive without turning it into an HTTP API.

OS schedulers

Emit launchd or systemd user units.

Runtime state

Read firing ledgers, watermarks and run traces.

Full arm reference

Every policy, command, exit and sidecar file.

Overview

Start

Project · live

Local API · live

Runtime · live

Remote API · preview

Operations

Reference

Arm registry

One beat, complete

Read before firing

Every door ends at one firer

Suspend with a reason

Continue

Resident server

OS schedulers

Runtime state

Full arm reference

​One beat, complete

​Read before firing

​Every door ends at one firer

​Suspend with a reason

​Continue

Resident server

OS schedulers

Runtime state

Full arm reference

One beat, complete

Read before firing

Every door ends at one firer

Suspend with a reason

Continue