SIGNET by Syahi

The approval method behind it has run Syahi's own outbound since August 31, 2026

What you approved is what goes out.

Your agent drafts the reply. You see every word on your phone. Then it sends. Signet sits between your agents and your customers: anything client-facing waits until you've verifiably seen it. Nothing sends that you didn't verifiably see. Veto is one tap and it always wins. A freeze button stops everything, from your phone, in one motion.

How it works

Three beats, in order

  1. Agent drafts

    Your agent finishes the words itself: the email, the quote reply, the reminder. It doesn't send it. It shows you the exact text, not a summary of what it plans to do.

  2. You see and tap

    The draft lands on your phone, word for word. Approve it. Veto it, and veto always wins. Or let the hold clock run: it releases only once you've verifiably seen it.

  3. Receipt lands

    What was sent, who approved it, when. A permanent line in the ledger. Yours to point to, months later, without asking anyone to remember.

How it's different

One of these is a decision. The other is a reflex.

Every other approval tool

You approved a sentence about the draft. The draft itself? Never saw it. That tap is a reflex, and a ledger full of reflexes proves nothing.

Signet

You read the words that will actually leave. Your approval is sealed over those bytes, and changing one byte kills it. That tap is a decision.

Not a demo film. A real run.

We ran the battery on ourselves first

Signet productizes the approval system Syahi already runs on its own outbound. On August 31, 2026, we put that system through a live battery against our own production releases, on the phone, with real clocks. Here's what happened, told straight.

  • Hash mutation, caught item B

    A draft's content changed after the founder had already looked at it. The old approval died on the spot; the system didn't let the changed text ride on a stale seal. It re-flagged the item as new and made her look again. She vetoed it. This is what content-pinning means in practice: you approve the exact bytes, not a label that says "email sent."

  • Veto won the race item C

    An item was already counting down on its hold clock, seconds from release. The veto beat the clock. It never went out, and the veto is on the record.

  • Freeze, from a phone item A

    One tap, from her phone, froze every pending release at once, mid-clock. No agent could lift it. Only she could authorize the lift. That's the rule now: any agent may freeze, no agent may unfreeze.

  • One send, only after her seal item E

    One real email went out: checked against the approved recipient and the signed template, sent only after she approved it, sealed in the record.

Two other drafts never made it to her phone at all. The system's own checks refused them first: one recipient wasn't on the approved list, one body had drifted off template. Caught before they became her problem, not after.

Sealed by Signet

The seal can travel with the message

Every approved send already mints a signed certificate. Opt a draft class in, and the send carries it outward: one footer line whose link opens a public verification page. The recipient sees who approved this exact message and when, checked against the signature in their own browser. No account, no trust-us.

Off by default, opted in per draft class. And the guarantee runs the other way too: a rejected or unverified send can never carry the footer — it is appended only after the certificate verifies.

Promised only when true

Two things this page refuses to fake

The demo The live screen capture lands here the day Syahi's own approvals run on the product itself. Not a mock, not a film, not before. If this box is empty, that day hasn't come yet.
The ledger, counted Decisions held, approved and vetoed will be counted here from the live ledger once real decisions flow through it.
held ____ · approved ____ · vetoed ____

Who it's for

Built for the owner who already does this by hand

You already read every quote before it reaches a client. Every reminder before it lands in someone's inbox. Signet does the same job when the hand doing the drafting is an agent's.

This is for you if

  • You run agents that talk to your customers
  • You want to see the exact draft, not a summary
  • One owner should hold the seal, not a queue
  • You want a receipt you can point to later

Not what this is

  • A shared review inbox for a dev team
  • A compliance audit log nobody reads
  • A public app you can sign up for today
  • A system with customers running it besides us, yet

Request a demo

See it happen on your own draft

The method runs Syahi today. The product is being built in the open, and it isn't open to outside customers yet. Book 25 minutes, bring a real email or quote you'd hand an agent, and we'll show you the actual ledger, not a slide.

Book a 25-min demo

Just a conversation for now. No checkout, no commitment.