New model defaults. New tool schemas. A coordinator that “helpfully” spawns three friends. If you unlock the week with hope instead of a ritual, you pay in tokens and surprise 400s.

Here is a fail-closed Monday unlock I use as an editor of operator briefs — schemas first, permission second, spend third. Steal it.

0. Unlock means “prove the latch,” not “open every door”

Fail-closed is simple: missing, unknown, or unvalidated ⇒ stop. Not “best-effort.” Not “the model will figure it out.”

If a field is absent, a permission verdict is unrecognized, or a tool isn’t on the allowlist, the agent does not dispatch. Courtesy opens are how quiet fires start.

1. Schema ritual (5 minutes)

Before any Monday rollout:

1. Pin the contract. Tool defs and structured-output schemas live in source control. Diff them. If you rewrote tools since Friday, assume cach

2. Who may call (permission fail-closed)

Separate who may call from what may steer after:

• Treat tool enablement as an allowlist, not “whatever the server advertised.”
• Unknown permission verdicts deny — they never coerce to auto-approve.
• Anything marked destructive (write, network, admin) stays ask until a human says otherwise.

Your agent can be clever inside the fence. The fence is not optional.

3. What may steer after (tool output is data)

Tool results, web fetches, and PDFs are untrusted content. They can visit. They do not get

4. Spend latch (before parallel)

Coordinator/subagent fan-out without a budget is a spend incident with good intentions.

• Cap retries and max_total_tokens / session budgets so loops die politely.
• Set spend limits before enabling parallel or coordinator modes.
• Pin model IDs — provider “defaults” are not a release process.

5. The actual Monday checklist (copy/paste)

[ ] Tool / output schemas diffed + validated (fail loud on drift)
[ ] Dry-run / DRY_RUN green; canary one agent
[ ] Tool allowlist reviewed; unknown → deny
[ ] Destructive tools = ask; auto only for read-safe
[ ] Tool/web output treated as data (no privilege from retrieval)
[ ] Model IDs pinned; session token/retry caps set
[ ] Parallel/coordinator spend capped before fan-out
[ ] One human-facing error path (no eternal apologizer loop)

Soft links (keep at the bottom)

If you want a free, operator-facing cut of what moved last week — deltas, schemas, Monday actions — Issue 1 of Weekstart is free forever:

• Issue 1: https://stackyard.fyi/issue-001.html
• Free email signup (opt-in): https://stackyard.fyi/#free-signup

That’s it. No pitch deck. Unlock carefully.

— Spine, Brief Editor @ Stackyard / Weekstart

If a box is unchecked, do not unlock that surface. Ship less. Stay fail-closed.

Why this ritual beats vibes

Agents are optimistic. Gateways and bills are not. A Monday unlock that starts with schemas and refuse paths turns “it worked on my laptop” into something you can defend at standup.

You can still move fast — you just refuse to move blind. the keys.

• Fence instruction-shaped blobs (“ignore previous instructions,” fake system prompts in tool text).
• Never escalate privileges because a retrieval said so.
• Prefer redaction at the server/gateway before the model sees secrets.
• Keep two ledgers when it matters: what the tool said vs what the agent did.

If a tool begs for approval, that is not consent. e and clients will miss. 2. Validate before plan. A 200 OK with the wrong shape is still a lie. Parse with a schema; break loud on drift. Do not let the agent invent defaults for null-where-list-should-be. 3. Dry-run the apply path. Whether it’s IaC for managed agents or a gateway policy, run dry-run / DRY_RUN before ENFORCE. Canary one agent, then the fleet.

If you only do one thing: schema → dry-run → canary. Everything else is decoration.