Documentation
Stvor technical docs
Pre-execution verification that binds intent to execution. One gate: canonical payload hash compare at verify time — swapped destination → signed DENY, not a silent pass. Every decision gets an ES256 (P-256) Trust Receipt verifiable offline (ATS-1 draft).
How it works →
commit → verify → settle, attack/defense pairs, ES256 receipts, Stripe reference flow, threat model.
Integration guide →
@stvor/client quickstart, api.stvor.xyz endpoints, checkpoint placement, payment rails.
ATS-1 spec →
Trust Receipt schema, ES256 signing, verification gate, escrow lifecycle, offline verification.
Browser verifier ↗
Paste a Trust Receipt — ALLOW or DENY — verify ES256 signature with only the published key.
Test vectors ↗
Published fixtures/ — self-check your client before writing a line against the API.
Hackathon reference (nous) ↗
Hermes build with attack sim, agent arena, Stripe escrow — separate from production API.
/commitments, /verify, /receipt. White-glove pilot integrations available if you want help wiring the checkpoint in your stack.Start with How it works if you need the threat model. Read Integration guide to wire against the API. Implementers should read ATS-1 for the portable receipt format.
Ready to wire this in production?
I stand up a Stvor checkpoint in front of your execution flow — commit intent, verify at execution, settle only on ALLOW — plus a signed Trust Receipt for every decision. I do the integration. At the end it works and you keep going, or you pay nothing further.
Message @kun_sapog