7 micro-topics in Reliability & Operations, each with the evidence that proves you have it and the written reason behind every link. Before you start, it rests on 6 other domains. Nothing in the map rests on it yet — it is a leaf.
7 topics · depth 11–16 of 16 · 6 internal links · 7 in · 0 out
Load-bearing links first. Each one says what in this domain rests on what outside it, and why.
2 links
Distinguish a harness from an execution layer rests on Run an agent loop
A harness wraps a loop that runs.
Set retry and budget ceilings rests on Bound loops with budgets
The ceiling moves the loop's budget into the harness.
1 link
Add an independent checker rests on Write deterministic checks
A checker needs a definition of correct.
1 link
Encode a harness after observed failure rests on Trace LLM applications
You encode failures you observed.
1 link
Write a policy layer rests on Defend against prompt injection
Untrusted input is the reason the policy exists.
1 link
Define rollback boundaries rests on Roll back safely
Reversibility is the same discipline applied to agent actions.
1 link
Distinguish a harness from an execution layer rests on Handle exit codes and errors
Exit codes are the simplest pass-fail signal a harness reads.
In prerequisite order. Each idea names the artifact that closes it, the market demand that put it on the map, and what it stands on.
Depth 11 · conceptual · scaffolded · M32
Knows what shell access alone does not give you
Run an agent loop · Agents
A harness wraps a loop that runs.
Handle exit codes and errors · Shell Scripting
Exit codes are the simplest pass-fail signal a harness reads.
Depth 12 · conceptual · scaffolded · M32
Separates the maker from the judge
Distinguish a harness from an execution layer
The checker is the component the definition demands.
Write deterministic checks · LLM Evals
A checker needs a definition of correct.
Depth 12 · conceptual · scaffolded · M32
Bounds cost and looping at the harness level
Bound loops with budgets · Agents
The ceiling moves the loop's budget into the harness.
Distinguish a harness from an execution layer
Bounding is a harness responsibility.
Depth 13 · meta · guided · M32
Knows which parts survive a model upgrade
You classify components you have built.
Depth 14 · meta · guided · M32
Builds on the second occurrence, not the first
Separate connective from compensatory harness
Knowing which kind you are building tells you when to build it.
Trace LLM applications · Observability
You encode failures you observed.
Depth 15 · representational · guided · M32
Allowlists actions and sandboxes execution
Policy decides what the checker's verdict permits.
Defend against prompt injection · AI Safety & Governance
Untrusted input is the reason the policy exists.
Depth 16 · conceptual · guided · M32
Makes agent actions reversible
Reversibility is what makes a permissive policy survivable.
Roll back safely · Delivery & CI/CD
Reversibility is the same discipline applied to agent actions.
Everything downstream that names an idea here as a prerequisite, grouped by where it lives.
Nothing in the map rests on this domain yet — it is a leaf.
Retool. Retrain. Relaunch.
375 ideas. 17 weeks. No tuition, ever.
Vets Who Code is a veteran-run 501(c)(3). The accelerator is free, remote, and we don’t take a share of your first paycheck.
Free · Remote · 17 weeks · EIN 86-2122804