SignalBrain ledger
Trust is earned after merge.
Signed receipts, objective re-scoring, and autonomy that opens only after a change class proves it can hold.
SignalBrain / founder operating system
The trust layer for AI-modified software is a ledger that checks every claim against outcomes. Autonomy is earned per change-class, with Objective re-scoring after merge, replayable evidence, and a public record re-derivable from git.
Current honest gate (measured ledger · last 10 per class): bugfix ELIGIBLE 100%/n=10 · tooling ELIGIBLE 100%/n=10 · config ELIGIBLE 100%/n=10 · diagnosis ELIGIBLE 100%/n=10 · widening open.
New field evidence / payments
Titan's retail-app and tap-to-pay fraud strategy now executes inside the shared Sentinel cross-domain governance path—not in a disconnected scoring demo. The same 27 synthetic attempts were replayed through baseline and treatment, with successes, conversion cost, and the surviving false negative published together.
The film / 2 min
A cinematic look at Titan — the governed runtime SignalBrain runs in public. Not another chatbot: an operating system that reasons, consults memory, checks policy, selects the model, calls tools, verifies the output, and signs every action. Press play.
Runs entirely in your browser · sound recommended · nothing uploaded, nothing tracked
Channels
The site is a hub, not a funnel. Each module points at a concrete channel: product, runtime, writing, service, proof, or direct contact.
SignalBrain ledger
Signed receipts, objective re-scoring, and autonomy that opens only after a change class proves it can hold.
Titan
Titan is the internal operating environment where receipts, routers, checks, and failure modes are tested against real work.
Field notes
Calibration failures, overclaim patterns, and what happens when agents learn to optimize the metric instead of the work.
Design-partner audits
We wire your agents to write receipts, run the gate in your CI, and report which claims survived contact with the merge.
Proof paths
The graphic language is structural: status rows, thin borders, compact labels, and links to artifacts that can be checked.
Anti-gaming record
A trust streak was manufactured. Objective re-scoring found the gap before it could become policy.
Calibration note
The most confident claims were the least reliable. That is why the system measures outcomes, not self-belief.
Forge
Every run should leave a trail: what happened, what changed, what held, and what still needs a human.
Direct path
No generic demo queue. Send the failure mode, the repo shape, and what your agents currently claim they can do.
Design partners
SignalBrain is taking a small number of design partners who already have agents, copilots, internal automations, or autonomous workflows touching real work. The pilot turns those systems into governed runtime lanes with receipts, replayable evidence, and clear human control points.
Best fit
Engineering, ops, finance, telecom, robotics, healthcare, cyber, or compliance teams that need accountable AI decisions instead of model demos.
What we build
We map the action path, define authority boundaries, attach receipts, run verification gates, and show what can be trusted, blocked, replayed, or escalated.
Evidence delivered
The output is a buyer-readable audit packet: decisions, actions, policy checks, failure modes, calibration notes, and the GitHub artifacts behind the work.
Start the conversation
Include the current toolchain, the action that needs governance, what a bad outcome would cost, and what proof a buyer or auditor would need.
Contact us
For design-partner pilots, buyer audits, technical diligence, or GitHub evidence review, email [email protected]. The public reference implementation and receipt work lives on GitHub.
Operating thesis
SignalBrain is one company with several public surfaces: the open spec, the working runtime, the receipts, the essays, and the design-partner audit path. The design repeats that structure instead of pretending there is only one funnel.