an instrument, not an agent

Instruments,
not agents.

A family of tools built on one rule: the machine amplifies what you do and cannot override you. Its authority is bounded to a fraction of yours — in force, in text, in code, in sound, in ink. You lead. It lifts.
01 — the through-line

One governor, many instruments.

| the machine |  ≤  β · | you |

Every TFB instrument is a fast reflex loop and a slow deliberation loop, joined by a single immutable gate — the governor — that bounds the machine's move to β (under 1) of yours. It can't move unless you move, its share is always smaller than yours, and it can never reverse you. The same clamp runs in all of them; proven once, carried everywhere.

you0%
the machine0%
β0.85
ceiling holds ✓ — the teal bar never crosses the line
02 — the line

Two built deep. The rest, the same blood.

Helm and the Tokenizer are specified and verified end to end. They sit in a wider line of instruments that share the thesis.

force · robotics

Helm

A powered handle that can be stronger than you and physically cannot overpower you. Seen, Felt, Force-true — a servo arm, a backdrivable knob, a load-cell handle.
the hand
your measured force
the lift
bounded motor torque
status — twin + 3 build tiers, governor verified in C
text · tokenization

Tokenizer

A context-aware tokenizer that adds adaptivity without losing determinism. A deterministic base is the hand; the adaptive and LLM layers may only lift where the base is unsure.
the hand
deterministic base
the lift
bounded adaptation
status — spec + diagram + reference impl, invariants verified
code · pairing

Code

You write; it suggests within bounds. Your intent is the hand, its edits the lift — applied only with your hand on the wheel.

sound · music

Duet

You play; it harmonizes under the ceiling. Your line leads; its accompaniment can color but never take the melody.

ink · drawing

Ink

You draw; it firms toward your own ideal, bounded by β of your deviation. The closest sibling — it already runs the same clamp.

03 — the mapping

The same five rows, every domain.

What makes it a family and not five demos: the governor instantiates the same way each time. The hard part is naming the hand, the lift, and the budget honestly per domain.

instrumentthe hand (trusted)the lift (bounded)the budgetfail-safe
Helmyour forcemotor torqueyour measured forceblind sensor → motor off
Tokenizerdeterministic baseadaptive / LLM resegmentationbase uncertaintylow detection → base
Codeyour code & intentsuggested editsyour activity & acceptancelow confidence → no auto-apply
Duetyour playingharmonic / rhythmic assistyour notes & timingsilence → your line passes
Inkyour strokefirming toward your idealyour own deviationuncertain → raw stroke
04 — the shared primitive

What every instrument inherits.

the governor

One immutable gate

The single path from intelligence to action, bounding the machine to β of you. The smart layer can't reach past it.

receipts

Provenance, always

Every move carries what it was, how confident, and how far it deviated from you — auditable, not opaque.

the autonomy dial

β is a knob

β = 0 is the deterministic, fully-yours floor; turn it up for more lift. One artifact serves the cautious and the eager.

fail-safe

Blind means powerless

Lose the trusted signal and authority collapses to zero — never expands. A fault can't be read as permission.

the immutable anchor

It can't rewrite itself

The reference the machine is bounded against is frozen and versioned; change comes only by signed promotion, never live.

verifiable

Dare it, don't trust it

The guarantees are testable properties, checked in compiled C and Python over millions of cases — not promises.

05 — the discipline

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

A real instrument increases your contact with reality. The honest ledger, across the line.

Verified

  • Helm governor in C: 0 breaches, 0 reversals, 0 authority-on-fault over millions of ticks.
  • Tokenizer invariants in Python: determinism, ceiling, no-reversal, fail-safe, anchor immutability — all pass.
  • The same clamp shape across instruments — proven once, reused.
  • Ink already ships the β = 0.85 covenant in production code.

Not yet

  • Hardware not flashed — Helm builds await the kit (~July).
  • The trusted measurement (force, calibrated uncertainty) is the real attack surface and the real work.
  • The bound governs force/deviation, not goals or intent — one primitive, not a whole safety story.
  • Live feel and production quality are things only real use can judge.
06 — the red-team

Where the ceiling can fail.

The clamp is the strong part. The trusted input, the calibration, the cumulative and multi-DOF accounting, and the governance around it are where the risk and the work live. The honest list — with what each demands.

weaknessmitigation
The measured signal is the attack surfaceA spoofed or drifting "your force" grants real authority. Harden the input, not just the clamp: redundant, diverse, signed sensing; plausibility limits; force–motion cross-checks.
Silent sensor failure beats fail-safe"Blind ⇒ zero" needs blindness to be detected. Watchdogs, cross-modal consistency, bounded rate-of-change, bias to zero on disagreement.
Per-tick bound ≠ cumulative boundA persistent in-budget bias can ratchet you over time. Bound cumulative authority over windows; decay the budget; require net-human-positive.
Multi-DOF leakageBudget earned on one axis can be spent on another you aren't driving. Bound each DOF independently; zero budget on idle axes.
It bounds force, not goalsA harmful objective pursued within budget is still harmful. Keep human goal-authority; receipts and interpretability on the slow loop. One primitive, not a whole safety story.
It protects the reference even when wrongNo-override faithfully preserves a confidently-wrong base. Demand calibrated (not merely high) confidence; promotion paths to fix the base; monitor locked-in errors.
Calibration & the deviation metric are hardThe whole guarantee rests on them. Conformal / temperature calibration; semantic-aware deviation; conservative defaults.
Sometimes the machine should dominateE-stop, collision, tremor arrest. A separate, narrow, certified safety authority may exceed β — only to reach a safe state, never to pursue a goal.
Governance reduces to keys + a sliderThe anchor is immutable only if keys and the build pipeline are. Multi-party signed promotion, reproducible builds, key custody; principled β defaults, β = 0 floor.
"Can't overpower me" invites over-trustThe real guarantee is narrow. Scope every claim precisely; keep the honest-limits ledger as loud as the promise.