an instrument, not an agent

You lead.
It lifts.

A machine that can be stronger than you — and physically cannot overpower you. Not a promise it makes, a rule it can't break: every instant, its force is bounded to a fraction of yours.
gold = your hand teal = the machine β < 1 · the agency ceiling
01 — the one rule

A single line decides everything.

| machine's move |  ≤  β · | your move |

It lives in firmware, between the intelligence and the motor — a dumb, tamper-resistant governor the smart part can't rewrite. Three things follow, by construction:

CONSEQUENCE 01

It can't move unless you do.

Your move is the budget. Take your hand off and the budget is zero — it stops. Nothing happens on its own.

CONSEQUENCE 02

You're always the majority.

Its share of any motion is strictly smaller than yours. You stay the senior partner in every movement, by arithmetic.

CONSEQUENCE 03

It can never reverse you.

Amplify you or drag on you — at most. The direction of the net motion is always the one you chose. It can't out-vote your hand.

02 — feel it

Drag the gold handle. Try to break the ceiling.

Push it toward the teal target and feel it help. Let go and watch it stop. Flip it hostile and try to lose control — you can't. The bar on the right is the machine's allowed force; it never crosses the line.

ceiling holds ✓
drag the gold handle along the track →
your move0%
machine move0%
β0.85
machine strength. even at the top, the ceiling holds and you still win — it just takes more effort.
03 — the parts

Built on a $45 modular kit.

The Axiometa Genesis Mini — an ESP32-S3 board with snap-in AX22 modules. Tap a part to see its role. Most of it ships in the starter kit; the actuator and force sensor are the add-ons.

04 — how it works

Two loops, one gate.

A fast reflex loop measures you and drives the motor ~100 times a second. A slow loop — the "AI" — only ever proposes a goal. Everything it wants passes through the governor, the single gate to the motor.

slow loop / "AI" — proposes a goal
GOVERNOR  ≤ β·|you|
motor
you — measured (turn / force)
GOVERNOR
your move sets the budget
// the immutable safety layer — the only path to the motor
float governor(float machineCmd, float humanForce) {
  float cap = BETA * fabsf(humanForce);   // your budget
  if (machineCmd >  cap) return  cap;     // grant at most β of you
  if (machineCmd < -cap) return -cap;
  return machineCmd;
}

The same function runs in this page, in the browser twin, and in every hardware build. Proven once — carried everywhere.

05 — three tiers

Seen. Felt. Force-true.

The same clamp, three depths of contact — from a pointer you watch obey you, to a powered handle that measures your force and can't overpower it.

06 — features & benefits

Trust by construction, not by promise.

corrigible by design

You can always win

Control isn't granted by a policy that might change — it's a property of the math, true on every tick regardless of what the intelligence above decides.

fail-safe

Blind means powerless

If the machine can't read your force — sensor stale, unplugged, implausible — its budget collapses to zero. A fault loses authority; it never gains it.

bounded autonomy

Strong, and still safe to hold

The motor can be arbitrarily powerful above the governor. The bound is enforced below it, in firmware the smart part can't reach.

verifiable

Dare it, don't trust it

The guarantee is something you can feel in your hand and test on a serial monitor — and that we verified in compiled C over millions of ticks.

07 — real-world uses

Anywhere a machine shares force with a person.

The same primitive — power steering for force — wherever capability has outrun trust.

08 — the proof & the honesty

What's proven, and what isn't yet.

A real instrument increases your contact with reality. So here's the honest ledger.

Verified

  • The governor compiled in C and run for millions of ticks.
  • 0 ceiling breaches — the machine never exceeded β of you.
  • 0 reversals — the net force always kept the sign of yours.
  • 0 authority-on-fault — a blind sensor always meant zero.
  • ~0.545 effort ratio — the predicted 1/(1+β) work saving.
safety core: correct in real C

Not yet

  • Full sketches not flashed — hardware ships ~July.
  • The force-isolating mechanism is the hard 80% of the build.
  • Load-cell bandwidth limits crisp haptic feel (a known fork).
  • Open-loop force is approximate; a product wants current sensing.
  • Live feel on real motors is the thing only a hand can judge.
honest about the gap