Mock · TypeSafe-style art direction on Marrow

TUFSTXcgQkVGT1JFIEFDVCAvIENPTU1JVCBBRlRFUiAvIEFDUk9TUyBFVkVSWSBIQVJORVNT

Introducing Marrow ...................... Control beyond logs

The Seatbelt For Agent Fleets; Marrow Gives Work The Properties Of Proof

Get a key Watch a fail

MRW.GATE.01

Clock Tool 1.1

Friday, Sep 18, 2026
21:45:37

THINK×

Intentdeploy production worker
surfaces: repo / prod

GATE×

BLOCKtests missing
same fail 14×

COMMIT×

Sealedsha · smoke · rollback
fleet can reuse

We took the opposite product direction.

Everyone else traces after the crash. Marrow sits in front of deploy, merge, and spend. Policy first. Proof after. Same contract on Grok, Claude, Codex, and CI.

Decisions, not diaries

A green exit is not a green release. The outcome stays open until proof lands.

Calibrated stop

Allow, warn, hold, or block — from the last failure, not a vibes checklist.

Built for fleets

One hive across harnesses. The next agent inherits the scar.

Before.Runtime gate. Prior fails. Then the tool runs — or doesn’t.

After.Commit with tests, SHA, smoke, rollback. Or it didn’t happen.

We give a FAQ

Is this a model?

No. Marrow does not replace Grok or Claude. It governs them — think, gate, commit — so work has a receipt.

What do I do in the first hour?

Get a key. Catch one real fail. Commit the outcome. That’s the product. Not a strategy deck.

Does free actually stop a deploy?

Free is the diary. Paid is the brake. The loop is the same either way; enforcement is the plan upgrade.

Get a key Read the docs