Demoted, never hidden. Only asks with nothing human in front of them are surfaced. A requirement waiting on another requirement is listed as waiting, not asked for: a list that mixes the two teaches its reader to skim both.

These are real requirements that nobody can start. Printing them next to the ones that can be started is how a register teaches its reader to skim — so they are listed here, with the thing they are behind.

• Enrol home1 on the tailnet 2026-08-16
  Closed by: bootstrap evidence E6 — the MagicDNS name answered from VIN when the 10.10.0.10 literal did not
  Closed by evidence rather than by a tick. It is kept here because it is the case that proves the closure model: the requirement stopped being asked for when something observable became true, and the inventory entry was corrected in the same movement.
• Issue home1 a node credential so it can heartbeat 2026-08-16
  Closed by: the identity registry at /etc/jarvisos/node-identities.json carries a home1 entry; the console stores only its SHA-256 digest
  Replaced the shared ingest token. The console reports presence and lifecycle metadata and has never held the value.

• crit Mint the read-only Coolify API token
  Coolify exposes no route for minting or revoking API tokens (gap coolify-no-token-api), so every token in this estate is created by hand in the UI. Without the read token the adapter cannot list servers, resources or deployment status, which means `jarvisos-estate.mjs reconcile` cannot run and the 26 live Coolify resources stay unclaimed by the inventory. Blocks: Estate reconciliation, the catalogue's Coolify source, deployment status for every application, and gap estate-unclaimed, which is currently the largest crit in the repository.
• crit Sign the Claude CLI in as the jarvis service account on home1
  Claude Code is the engineering worker. Its sign-in is an interactive OAuth device flow: it prints a URL, waits for a browser, and writes the credential itself. Nothing headless can complete it, and until it is done home1 can be dispatched planning work but no code. Blocks: All engineering dispatch to home1. The node will onboard, heartbeat and advertise capacity without it — and every coding task will still land on VIN's single slot.
• warn Decide whether the estate gets a second public edge
  Gaps deployment-single-edge and estate-lifecycle-single-point say the same thing from two directions: one edge, one control plane, and every HA property in three registers is a plan rather than a fact until that changes. The auth register makes it sharper — one forward-auth upstream means an auth container failure reads as the whole estate being down. Blocks: The multi-node deployment register's edge layer, the second forward-auth upstream in the identity register, and any honest claim that this estate survives losing VIN.
• warn Create a jarvis service account on the NAS and authorise the control-plane key
  The storage register places every byte on a tier and says when that tier runs out, but the numbers behind it are derived from what the register places, not from the pool. The measured answers are `df` and `du` on a machine this process has no account on. A NAS with no service account is a NAS whose occupancy is an estimate that will be believed. Blocks: Measured storage occupancy for nas-backups and nas-media, and therefore any honest 'days until full' figure. Also every future remediation that would touch the NAS, which currently cannot be attempted at all.
• warn Sign the Codex CLI in as the jarvis service account on home1
  Codex is the reviewer in the dispatch model, so without it home1's work is written and merged by the same worker. Its sign-in is the same interactive OAuth flow and equally cannot be automated. Blocks: Independent review of work produced on home1.
• warn Enrol the node on the tailnet
  Joining a private network is an act of enrolment. It needs an auth key or an interactive login from the admin console, and this kit deliberately has neither: an installer that can add machines to your private network is an installer that can add anyone's. Blocks: Everything. Nothing else in the kit runs without the private plane.
• warn Approve the elastic-compute spending ceiling
  The burst register is adopted with zero recurring cost as the default and the rollback plan, and no billable operation is executable: the runner prints the provider request and refuses it. What it does not have is a person's agreement to the ceiling, and every grant in that register is issued against a budget this approval sets. Blocks: Every billable burst operation, and therefore the write-scoped Hetzner token that would carry one out.
• warn Write the tailnet ACL for tag:burst
  Gap tailnet-acl-for-burst is a crit: the burst plan attaches rented nodes to the private mesh and no ACL for tag:burst exists. A burst node with the default policy is a machine somebody else's hypervisor is hosting, sitting on the same flat network as the Postgres primary. Blocks: Attaching any burst node to the mesh. It is a prerequisite of the write-scoped provider token, because the first thing that token would do is create a node that joins the tailnet.
• warn "Run the quarterly off-site restore drill, in person" has lapsed and is being asked for again
  The inventory declares gwscli-s3-offsite's verification as a quarterly restore drill. A drill that happened once is a drill that proved the backup worked in April. It fell due on 2026-07-19, 31 day(s) ago. It closed itself once and it will close itself again.
• warn 12 asks are open against a declared ceiling of 6
  Either the estate genuinely needs that many decisions, or this register has stopped prioritising. Deliberately not fatal: a build that fails because the world has work in it is a build nobody trusts.
• note Give the NAS a stable name instead of a LAN literal
  The NAS is registered at 10.10.0.20. Home1 was registered at 10.10.0.10 until 2026-08-16, and that literal answered nothing from VIN — bootstrap evidence E6. The same failure is sitting in the register unexercised, and it will be discovered during an incident rather than before one. Blocks: Nothing today, because nothing on VIN currently talks to the NAS. It blocks trusting the NAS address the first time something does — which is the moment when finding out is most expensive.
• note Mint the read-only Hetzner token for the burst-only project
  The read credential is what turns the burst register's arithmetic from committed numbers into verified ones: it reads the provider's own price list, the server types and this month's usage. It is free, it cannot change anything, and the provider itself refuses it on every mutating route — which is why it is the credential every automatic operation uses. Blocks: Price verification (gap prices-unverified) and usage-against-ceiling reporting. Nothing spends money as a result of this token existing.
• note Supply the actual VIN invoice figure
  Gap prices-unverified: every euro in the burst comparison is a number committed to a register, not one taken from an invoice. The comparison's whole claim is that renting is cheaper than upgrading, and that claim rests on what VIN actually costs today. Blocks: Nothing operational. It blocks the burst decision being evidence rather than an estimate — and the break-even line, which is the number at which the entire policy inverts.
• note "Mint the deploy-scoped Coolify API token" is not an ask yet
  Waiting on coolify-read-token. Deliberately not surfaced: nobody can start it, and printing it would train its reader to skim the ones they can.
• note "Mint the read-write Hetzner token for the burst-only project" is not an ask yet
  Waiting on burst-spend-approval, tailnet-acl-burst, hetzner-read-token. Deliberately not surfaced: nobody can start it, and printing it would train its reader to skim the ones they can.

Principle

A requirement is a thing only a human can supply. Node access, a provider credential, an approval, a euro, or somebody standing next to hardware. If JarvisOS can do it, it is not a requirement, it is work.

Closure

Closure is derived on every render, never written down. A requirement carries the condition — a file becoming readable, a node advertising a capability, an entity appearing in the inventory — and stops being asked for the moment that condition holds. Where nothing can check, the register says why, and closure is a named person's attestation on the record rather than a tick.

Custody

No credential value appears in this file, in the API payload, in a page, in a log line or in a task report. A credential requirement carries a name, an absolute path outside this repository, and a rotation interval. Presence is established with accessSync — the file is asked whether it is readable, never what it contains — and a declared path inside this working tree is refused at load.

Surfacing

Only asks with nothing human in front of them are surfaced. A requirement waiting on another requirement is listed as waiting, not asked for: a list that mixes the two teaches its reader to skim both.

Next review

2026-09-14

Machine-readable at /api/v1/requirements · narrative in docs/REQUIREMENTS.md · node scripts/jarvisos-requirements.mjs next prints the same single ask in a terminal, with the same derivation.