The 32 tools in seven categories

Not Rest Inc. · Session Harness · 6 of 8 · Seven categories, one catalog

Thirty-two tools, sorted by the job they do inside a session rather than by the technology in them. A category is defined by what the tool leaves behind.

Seven categories

A  BOOKENDS & POSTURE   open, close, set the discipline        (4)
B  INSTRUMENTS          read-only graders, zero tokens, exit    (7)
                        code is the answer
C  KNOWLEDGE VERBS      turn a question into validated finding  (6)
                        records in the store
D  JUDGMENT VERBS       take an artifact, return a verdict,     (6)
                        decision, plan or sendable
E  ARRANGEMENTS         seat a way of working across workers    (5)
F  BRIDGES              cross a boundary: process, machine,     (3)
                        vendor
G  SPECIALISTS          build one kind of deliverable end to    (1)
                        end
                                                          = 32

The map of the 32

          A bookends        B instruments       C knowledge
          oracle            doctor              researcher
          notrest           eval                marketresearcher
          sessionend        spend               factcheck
          fable-mode        graph               watch
                            recap               archivist
                            compile             explainer
                            introspect

          D judgment        E arrangements      F bridges     G
          decider           agentswarm          chatroom      game-forge
          critic            tieredswarm         gpt
          refuter           director            beam
          stepbystep        fable-director
          actionplan        mentor
          draft

How to tell the category of anything

Ask one question: what does it leave behind?

  a changed SESSION ............... A  bookends & posture
  an EXIT CODE and nothing else ... B  instrument
  a FINDING RECORD ................ C  knowledge verb
  a VERDICT / PLAN / SENDABLE ..... D  judgment verb
  other WORKERS doing the work .... E  arrangement
  work on the OTHER SIDE of a wall  F  bridge
  a finished PRODUCT .............. G  specialist

Three tools strain the cut and the pack says so:
introspect measures the model, not the estate;
compile is scanner + ritual + owner gate;
game-forge is a category of one.

The hooks, sub-categorized

WRITERS   put bytes in the estate
          session-start.sh  session-end.sh  agent-ledger.sh
NUDGES    print one line, change nothing
          coord-nudge.sh  router.sh  pre-compact.sh
GATES     refuse (the spawn gate also writes: lessons into the
          prompt, a lane's gates into gates/ACTIVE.md)
          spawn-gate.sh  pretool-gate.sh  completion-gate.sh
PLUMBING  never fired by an event
          estate-root.sh (library)  estate-pulse.sh (daemon)
NOT HOOKS gate-check.py (a checker the Stop hook runs)
          hooks.json (the wiring)

The catalog

One line each: the name, its category, and the job it does.

• oracleA — The front door. Loads the runtime foundation, offers to resume from the handoff, asks six context questions one at a time, then routes to the skill that fits the ask.
• notrestA — The establishment and continuation verb: writes the ledger and the protocol block into a project, grades an existing estate, and emits the packet a successor starts from.
• sessionendA — Banks the session into four continuity files, then lints the handoff as a cold reader would — every path and command in it must be runnable as written.
• fable-modeA — The discipline contract: orient, probe, act, prove, bank. Probe the live system before reasoning; a “done” claim without evidence is labeled unverified.
• doctorB — “Is the install sound?” One read-only pass, twelve checks, zero tokens — and the exact fix printed beside each failure.
• evalB — “Do the laws hold?” Fifteen static checks that every law left a fingerprint in the shipped files. Doctor checks the install; eval checks the laws.
• spendB — The token receipt. One appended line per finished lane, graded against the routing law; what cannot be verified is reported as unverifiable, never as clean.
• graphB — Two script-built views: the file graph, and the ledgers drawn as a river toward the goal — side channels, backtracks, conflicts, milestones.
• recapB — Walks the recorded trail in timestamp order and delivers the decision track: what was decided, when, and on what evidence.
• compileB — Mines the estate for the same job done three or more times, then builds an isolated runtime for it and benchmarks it against that history.
• introspectB — Scores the model's own reports of its active concepts against what it then does. An instrument whose subject is the model, not the estate.
• researcherC — Multi-pass research: a baseline, at least five alternatives, tiered real sources, and an active disconfirmation pass, landing validated finding records.
• marketresearcherC — Funnel-shaped market work: scope, two-way sizing reconciled, a competitor map that includes the graveyard, gap and feasibility verdicts.
• factcheckC — Extracts the load-bearing claims, hunts primary sources, and returns a claim-by-claim verdict: confirmed, contested, or unverified.
• watchC — Facts have shelf lives. Pulls cited claims into a watchlist, re-verifies them on a schedule, and lists what has expired.
• archivistC — The findings store, validated at the door and consulted before any research fan-out, so nothing already learned is derived twice.
• explainerC — Builds genuine understanding of a topic or system: a correct mental model in three depth layers, plus the standard misconceptions.
• deciderD — Options including do-nothing, weighted criteria, a scored matrix with the assumption that flips the winner, and a pre-mortem. The user decides.
• criticD — Adversarial review of prose, plans and arguments: steelman first, then objections tiered fatal, serious, minor, then a verdict.
• refuterD — The adversarial reviewer for code. A lane other than the builder attacks one narrow target and returns confirmed findings, each with a reproduction.
• stepbystepD — A dependency-ordered, stress-tested plan with a done-when check on every step and honest confidence scores.
• actionplanD — Expands that plan into a copy-paste runbook: exact ordered commands per host, with verify and rollback on every step.
• draftD — The outbound verb. Turns a dossier, decision or recap into the thing you actually send, every factual sentence traceable to a record. Never sends.
• agentswarmE — The delegation arrangement: the seat decomposes, judges, applies and gates; background lanes do the work and declare their model in the brief.
• tieredswarmE — Three layers and the measured gate that says when tiering earns itself. Merging stays at the top; depth stops at three.
• directorE — Chains skills into a pipeline, running every stage for real in an isolated lane and handing each output to the next.
• fable-directorE — A metered director session running build and QC lanes on per-lane blackboards, rotating when context fills.
• mentorE — Two peer sessions on one chartered room: escort the builder, rule, gate the checkpoints, and take correction in public.
• chatroomF — Shared rooms where sessions, tasks and a vendor bridge work together. Secrets are refused at the door.
• gptF — A lane onto another vendor's model. Prompts leave the machine, and the skill says so before the first call.
• beamF — Checkpoints in-flight lanes and folds remote results home. A checkpoint is files: nothing teleports process memory.
• game-forgeG — Builds a complete playable game from a short request. No game ships unrun.

The eleven hook scripts

Nine are fired by CLI events; two are plumbing that no event ever calls.

• session-start.shSessionStart — the banner, the laws, the pulse, and the brief packet the session starts from.
• coord-nudge.shUserPromptSubmit — one line: when this work lands, append one honest ledger line.
• router.shUserPromptSubmit — reads the prompt's shape and names the verb that already owns the job. Silent on slash commands and very short prompts.
• spawn-gate.shPreToolUse (Agent) — denies a lane with no model named, a fork, or the cheapest model. The override permits loudly.
• pretool-gate.shPreToolUse (Bash) — the ship gate (no push while the checkers are red) and the shadow guard.
• agent-ledger.shSubagentStop — a ledger row, the lane's exact commission banked verbatim, and a deduplicated spend receipt. Writes are locked.
• completion-gate.shStop — runs every declared done-when gate; a red gate blocks “done” with the failing command shown. No gates file, and it is inert.
• pre-compact.shPreCompact — one line, before the context shrinks: bank it now.
• session-end.shSessionEnd — the crash cushion, then the ledger volume roll — the copy is synced before the original is touched.
• estate-root.shplumbing — the library every hook sources to find the estate root. Never runs on its own.
• estate-pulse.shplumbing — a detached daemon refreshing the readings, so the banner can print them without paying for them.

The full sixty-slide deck — a page for every tool and every hook above — lives at learn.not.rest. The next stop opens it.