Liability you define, not liability you inherit
For most of your team's work, a verification request arrives with no statement of what you would be standing behind if you answered it. That is why issuing anything formal can feel like accepting exposure with no edges. Signura inverts the order.
Before a single relying party can depend on a fact, your governor decides which facts the organisation will attest to and the liability it is prepared to accept. Each attestation type then carries explicit, scoped liability terms and an expiry, written with their boundaries intact. You are not signing an open-ended promise; you are publishing a bounded one, on terms you set in advance.
Where the accountability sits
A fair objection is that a reliance layer merely moves liability around rather than removing it. Signura does not claim to remove it. What you stand behind stays exactly what you chose to attest to, within the scope you defined — the layer adds an accountable party where there was none, rather than reassigning one.
Signura does not become a relied-upon party beyond the integrity of the cryptographic proof and the accuracy of the freshness and revocation status it reports. A relying agent verifies your signed proof at the moment it acts and keeps it as evidence, and every reliance event is logged — so accountability rests with the party that signed the claim, which is you.
Why a reusable attestation beats a bilateral request
Today your team fields the same requests — licence validity, policy status, certification — again and again, per integration, producing no reusable output. When you publish a fact once as a signed attestation, relying parties consume it directly, and your staff stop confirming the same fact by hand.
On price, there is no established pattern for agent-to-agent reliance yet, so we are plain about it: issuance fees and attestation-management subscriptions cover the issuing side, reliance is metered per event on the relying side, and the specific scope, thresholds and limits are agreed with you per engagement rather than quoted from a rate card we cannot yet justify.