Enforce boundaries. Verify evidence.
Current implemented protections and future release requirements are deliberately separated. The product is not independently security certified or approved for real-money workflows.
Implemented in v0.3
OIDC/JWT validation against a pinned issuer, explicit agent enrollment, scoped tenant membership, short-lived web sessions, browser-bound SSO login state, PKCE and nonce checks, CSRF protection, PostgreSQL-compatible storage, optional PostgreSQL row security, queue leasing and retries, AWS KMS signing integration, encrypted inquiries, and optional server-side Turnstile/email confirmation.
Not independently verified
One genuine Stripe TEST-mode draft has been created and observed. No production identity-provider enrollment, AWS KMS custody validation, managed production database, verified customer email transport, or separately operated witness has been established. No independent penetration test, SOC 2, ISO 27001 or PCI certification has been completed. Physical or financial outcomes are not certified.
Claims and evidence
A digital signature authenticates signed bytes under its key model; it cannot establish that a physical task succeeded. The first verification use case concerns only a draft invoice record in a designated test destination. Shared organizational control is disclosed, not represented as independent truth.
Enterprise release gates
Before accepting consequential access: authenticate the real customer tenant, validate external tokens and key rotation with the selected IdP, test PostgreSQL isolation and restore, verify KMS least privilege, confirm email DNS/delivery, review privacy and contracts, conduct an independent security assessment, instrument monitoring and rehearse incident recovery.
Report an issue
Use the contact channel pending activation of the verified security mailbox. Do not send exploit details or secrets through the public form.