Meridian Verity Group builds HALTSEAL, execution-time control for money movement.
Try the demo · Inspect the control tests · Review one workflow
A $10,000 payout times out. The original may already have paid, or it may still pay. A backup provider is available. Changing the route must not create new payment capacity for the same obligation.
On governed release paths, HALTSEAL is designed to check the exact proposed payment, current authority and evidence about prior attempts at the last reversible moment.
| Decision | What it means |
|---|---|
| ACCEPT | The exact proposed payment passes the current release checks. |
| HOLD | The prior payment may still take effect, or required evidence is incomplete. |
| REFUSE | The proposed payment is not permitted, including when the obligation is already fully paid. |
ACCEPT is a release decision. It does not confirm that a payment completed.
Start with the Payment Fallback Control Tests: 16 synthetic cases, four reference models and an offline R02 replay.
| Public repository | What you can inspect |
|---|---|
| haltseal | Synthetic payment-decision contract, signed receipts, a local mock, and offline Python and TypeScript verifiers. See the repository for hosted launch status. |
| permit-receipt | Exact-action binding, current authority, revocation and anti-replay evaluation accompanying the individual Internet-Draft. |
| acceptance-plane | The broader architecture for checking consequential machine actions before effect, with a runnable synthetic evaluation. |
| public readiness kit | Educational scenarios, a local browser demo and tools for reviewing action-acceptance questions. |
Public repositories contain synthetic evaluation and research materials. They do not establish production readiness or independent validation. Review each repository's scope, license and patent notices.
ACM Queue · A Valid Tool Call Can Still Be an Invalid Effect
Scott Lee on execution-time control for consequential machine actions.
IETF Internet-Draft · Permit Receipts for Permit-Before-Commit Authorization
An individual submission and work in progress, not an IETF standard.
Agree a scoped paid assessment of your existing payment controls. Where the findings justify further evaluation, review decisions in Shadow without payment authority. Consider selective enforcement after technical validation and customer approval.
Request a workflow review · Review the evidence and limits
Founded by Scott Lee, who designed HALTSEAL's control model and wrote its core reference implementation.
Founder website · Company · HALTSEAL
Decision before action. Proof before consequence.