Prove who you are
Use legal identity and authentication methods already available in the profile before asking for new evidence.
Live
Goal: Prove who signed and can act.
AccordFlow — the Trust Layer of robo-Meister
Signature router that assigns proof methods by availability and jurisdiction. Reusable Trust Profile collects all evidence and requests only what is missing.
Live demo - test evidence
Service Agreement
Poland ↔ United States
| Requirement | Status |
|---|---|
| Legal identity | Ready |
| Strong authentication | Ready |
| US signing route | Ready |
| Selected Polish route | Method required |
| Company authority | Ready |
| Manual review | Required |
Accepted method added: Demo Polish qualified-signature provider.
Capability now available: Polish provider route for this demo policy. Disclosure remains limited to certificate subject, provider reference, and signing timestamp.
One profile, many trusted actions
A Trust Profile is reusable evidence with boundaries. It helps prove who you are, prove that you can act, and prove what happened without exposing unrelated evidence.
Prove that you can act
Keep personal identity separate from organization authority, roles, policy approvals, and authority expiry.
Prove what happened
Record requirement checks, evidence used, document hashes, policy versions, disclosures, and review decisions.
How AccordFlow works
Create / receive agreement
Start from a sample, upload a document, or receive an agreement from the Legal cycle.
Match requirements to Trust Profile
The router compares jurisdiction, risk, party role, and provider availability with reusable profile evidence.
Complete only missing evidence + request signatures
AccordFlow asks for the smallest missing proof set, then requests signatures through the selected route.
Sign, protect and verify with decision record
The final record explains selected proof methods, disclosures, warnings, hashes, and verification outcomes.
Use cases: router + profile
AccordFlow is not another e-signature button. It decides which proof route is acceptable, then reuses Trust Profile evidence across the wider robo-Meister flow.
Tab Solo
Cross-border signing route
A company needs to sign in Poland and the United States. AccordFlow checks availability and jurisdiction, then selects an accepted route such as QES, BankID, passport check, passkey-backed identity, or manual review when automation is not enough.
Tab Inside
Legal cycle evidence collector
Inside the Legal cycle, the Trust Profile gathers KRS registry data, powers of attorney, authority records, and evidence logs, then sends targeted follow-up requests only for the missing items.
Cross-border readiness
AccordFlow shows a requirement matrix instead of a universal compliance promise.
| Route or requirement | Status | Accepted alternatives | Disclosure |
|---|---|---|---|
| US signing route | ready | BankID, passport check, passkey-backed identity | Legal name, session authentication, document hash |
| Polish provider route | method available | Demo Polish provider route, EU provider route | Certificate subject and provider reference after confirmation |
| Company authority | missing evidence | Registry lookup, admin attestation, board resolution reference | Role and authority reference, not raw evidence |
| Manual review | review required | Reviewer approval or counterparty acceptance | Change summary and reviewer decision |
| Unsupported route | unsupported | Use manual review or a different policy | No automated route is represented as sufficient |
Boundary: applicability can depend on document type, governing law, organization policy, provider availability, and local requirements. This page demonstrates readiness mechanics, not legal advice.
Why was this signer accepted?
Explanation recorded
- ✓ Legal name verified
- ✓ Signing key controlled during the session
- ✓ Organization authority active
- ✓ Document hash matched
- ✓ Policy version recorded
- ✓ Manual review completed
Not disclosed
- × National identifier
- × Raw identity document
- × Unrelated profile methods
Encryption and controlled access
Access follows profiles and roles rather than vague promises.
Profile-bound access
Named profiles and organization roles determine who can open confidential documents.
Keys and recovery
Key rotation, revoked access, and recovery policy are recorded with profile context.
Access audit
Workspace audits show access attempts, revocations, role changes, and recovery events.
Every agreement can make the next one easier
A required method was added for this agreement.
New reusable capabilities unlocked by this demo method and policy:
- ✓ Polish provider route
- ✓ EU provider route
- ✓ High-assurance organization approval
- ✓ Stronger profile recovery
Protect the decision, not only the PDF
Warnings are explainable transaction signals. AccordFlow does not call this a credit score.
- Document changed after review
- Key replaced shortly before signing
- Authority expired
- Provider evidence revoked
- Unexpected recovery event
- Profile changed during the agreement
Exact capability status
Every homepage capability maps to src/main/resources/public-capabilities.yaml.
| Capability | Status | Scope | Provider dependency | Known limitations | Last verified |
|---|---|---|---|---|---|
| Reusable Trust Profile | implemented | Individual and organization profiles | None | Demo policies are examples. | 2026-07-10 |
| Agreement readiness matching | implemented | Agreement, parties, jurisdictions, configured policy | None | Applicability depends on local requirements. | 2026-07-10 |
| Polish provider route | provider integration | Live demo test route | Demo Polish qualified-signature provider | Not a final legal determination. | 2026-07-10 |
| US signing route | implemented | Demo agreements using reusable evidence | None | Policy can require extra evidence. | 2026-07-10 |
| Organization authority evidence | beta | Organization roles and authority references | Organization registry or administrator attestation | Authority can expire. | 2026-07-10 |
| Document integrity verification | externally verified | Demo document and evidence hash comparison | None | Depends on supplied evidence package. | 2026-07-10 |
| Profile-bound encrypted access | beta | Profiles, roles, rotation, revocation, audit | None | Recovery policy depends on workspace configuration. | 2026-07-10 |
| Transaction warning rules | candidate policy | Change, key, authority, provider, recovery warnings | Configured providers for revocation signals | Review signals, not legal conclusions. | 2026-07-10 |
| Public verification demo | implemented | Live demo test evidence package | None | Test/demo evidence only. | 2026-07-10 |
Live verification demonstration
Use test/demo evidence only. Verify the original, change the document, then verify again to see integrity failure.
Fictional Service Agreement
Parties: Demo US LLC and Demo Poland Sp. z o.o.
Hash marker: ORIGINAL-DEMO-HASH
Demo evidence package
Expected hash marker: ORIGINAL-DEMO-HASH
Verification not started.
Built for the people who need the decision explained
Individuals
Know which profile evidence is used, what is private, and what is disclosed per agreement.
Organizations
Separate personal identity from company authority, policy approvals, and access controls.
Product builders
Use demonstrable verification and readiness flows without advertising unavailable SDKs or controls.
Pricing comes after readiness
Start with demo verification, then choose a plan. Existing-agreement verification and evidence retention do not disappear after downgrade.
Free
Try sample agreements and public verification.
View pricingTeam
Reusable profiles, organization roles, and agreement readiness workflows.
View pricingContact
Organization/demo contact remains available for rollout planning.
Contact organization demo