Handover, Version 5

Turn a rough prompt into finished work.

Handover asks a few questions. You approve once. It runs the plan itself. Each run caps at $2, and it runs supervised.

How it works

Three steps. You approve. Then it runs.

  1. 1

    Translate the rough prompt

    Handover turns your rough prompt into a full plan and orchestration. It asks only the early questions needed to set the plan.

  2. 2

    Approve in two stages

    Stage 1 approves intent. Stage 2 approves the execution manifest. Two approvals catch a wrong plan before any work starts.

  3. 3

    It runs inside the envelope

    A coordinator owns the plan and runs it with full autonomy inside the approved envelope. Each run caps at $2, and it runs supervised.

The author is never the verifier, and the judge rules in a fresh context. That split keeps a weak result from passing its own test.

Two tall marble pillars at night with a glowing gold seal floating between them

The gate

Nothing runs until you approve it twice.

Stage 1

Stage 1 approves intent. It checks the goal is the one you meant before any plan is written.

Stage 2

Stage 2 approves the execution manifest. It checks the exact work before the run starts.

A repair that changes the manifest needs reapproval. A gap is never converted into a pass, and a dead end report comes when the predicate is unmet.

The 16 engines

Sixteen ways to think. One umbrella over them.

All 16 engines plus the Discovery umbrella were proven Nov 12 to 14, 2026. Each proof used sealed tests with 2 fresh blind trials and a fresh judge.

The core 4 loop

  1. Anomaly Hunting finds what breaks the model.
  2. Abduction names the best cause.
  3. Falsification tests it.
  4. First Principles sits underneath.

Invention is the outcome, not a 17th skill. The loop turns a broken model into a new idea.

01

Anomaly Hunting

Research

Finds what breaks the model.

02

Abduction

Research

Names the best cause.

03

Falsification

Proof

Tests the cause.

04

First Principles Questions

Research

Sits underneath the loop.

05

Induction

Research

Builds a pattern from cases.

06

Deduction

Proof

Draws what must follow.

07

Analysis and Synthesis

Research

Splits a problem, then rebuilds it.

08

Thought Experiments

Stuck

Runs a case in the mind first.

09

Analogy and Cross-Domain Transfer

Research

Carries a working pattern across fields.

10

Inversion

Stuck

Starts from failure and works back.

11

Counterfactual Thinking

Stuck

Asks what changes if one fact flips.

12

Constraint-Based Discovery

Search

Uses limits to narrow the search.

13

Search the Possibility Space

Search

Maps options before picking one.

14

Evolutionary Search

Search

Keeps what works and varies it.

15

Serendipity plus Prepared Mind

Search

Notices a surprise and knows what it means.

16

Consilience

Proof

Checks that separate lines agree.

17

Discovery

The umbrella over all 16 engines. One skill holds the router, the phases, and the core 4 loop.

16 engines, one chart. The router picks the engine the work needs.

Proof

Router run 3 passed on Nov 14, 2026.

Both fresh blind trials passed both test situations. The run cost $0 of the $4 cap.

2fresh blind trials
2test situations passed
5 of 5repeats each
$0of the $4 cap
12 of 14spawns used
2 of 3fix cycles used
16 engines, each proven on sealed tests. The workshop holds 16 tools, one per engine. The router picks them.

Limits

What the proof does not cover.

  • The loader check never ran, because no Muse skill loader command exists in the environment where the proofs ran.
  • The router proof covers two test situations, not live use of all 17 skills.

Guides

Read the manual, or inspect the schema.

Visual guide

Parts, 6 assembly steps, loop and graph, and troubleshooting. The full IKEA-style manual for Handover v5.

Open the visual guide →

Field kit and graph

The schema, the kit diagram, the graph diagram, the per-unit list, and the map from each drawing to its schema path.

Open the field kit and graph →

Star Handover on GitHub.

Version 5 is on GitHub now. A star tells the next visitor the work is worth a look.

Star Handover on GitHub
Hermes delivers the work with proof. The check seal marks it done.