Qualify
Confirm the principal, representative, action, relying party and the manual decision being replaced.
Design-partner programme
Bring the action your organisation cannot safely accept on identity alone.
We will map who appoints whom, what they may do, which constraints matter and what the relying party must verify.
6–8 week working plan Security review Legal boundary review
A useful first conversation
Concrete enough to test. Narrow enough to govern.
- One principal organisation
- One representative class
- One narrowly defined action
- One real relying party
- A revocation or expiry scenario
- Legal and security stakeholders
A paid, bounded pilot
Robert qualifies the workflow first, then issues a written scope and fee based on integrations, assurance and evidence requirements.
Send the workflow
Give Robert the action, actor and relying party.
Robert reviews suitable enquiries personally and aims to respond within two UK business days.
The working plan
Four stages. One inspectable authority decision.
Design
Map the mandate, vocabulary, limits, approval conditions, trust boundary and data flow.
Prove
Run issuance, presentation and verification in the scoped sandbox, including a denial and expiry or revocation.
Review
Walk legal, security and operations through the evidence, open gaps and a decision on any connected next step.
What the pilot leaves behind
Evidence your stakeholders can challenge.
- Authority-workflow and data-flow map
- Structured mandate and policy vocabulary
- Sandbox configuration and verifier walkthrough
- Decision receipts for permit, deny and approval-required paths
- Revocation or expiry test record
- Security, legal-boundary and production-gap review
Success means the relying party can explain why one real action is permitted, denied or escalated using current, inspectable evidence—not that the pilot has created a universal legal power or production certification.