Input and identity boundaries
Zod validates domain and transport input. Uploaded content and registry responses remain untrusted.
Security model
Fail closed when authority cannot be proven.
WhoActs treats credentials, uploaded evidence, external sources and requested actions as untrusted until the relevant control has checked them.
Sandbox ≠ productionSandbox-only signing materialNo qualified trust status
Signing material
Secrets and private signing material are server-only. Connected mode refuses known sandbox key identifiers.
Tenant and role controls
Connected persistence defines tenant RLS and private tenant-prefixed evidence storage.
Verification and audit
The verifier checks signed claim binding and current mandate state; audit events are hash-linked.
Threat to control
What the implementation checks—and what still remains.
Forged credential
ES256 verification, kid/JWKS and issuer policy
Protected production keys and rotation
Valid token used out of scope
Deterministic action, resource, jurisdiction, amount and supplier policy
Relying-party vocabulary mapping
Hidden revocation
Exact registered mandate version checked on verification
Partner Token Status List profile and SLA
Malicious document
MIME and size bounds; extraction treated as untrusted
Malware scanning, quarantine and disarm
Webhook forgery or SSRF
HMAC, timestamp and DNS-vetted public IP pinning
Rotation and durable delivery evidence
Audit mutation
Previous/current SHA-256 locally tamper-evident chain
External anchoring and WORM export
Production boundary
Repository controls are not operational assurance.
Production reliance still requires protected key custody, connected-environment evidence, authenticated user operations, backup restore tests, alerting, dependency monitoring, penetration testing, incident ownership and an agreed provider trust model.
Security reports can be sent to rob@mrprime.com. Do not include live credentials, secrets or personal data in the first message. Robert Prime aims to acknowledge a genuine report within two UK business days; that is a response target, not a remediation SLA.
The machine-readable reporting route is published at /.well-known/security.txt.
Design-partner programme
Put the authority flow in front of your security team.
We will map the principal, representative, action, resource, policy and relying-party decision with your legal, security and operational stakeholders.