Pacterms
Home

Claim register

What we claim, what we do not, and when each was last checked

Most companies publish what they can do. This page also publishes what they cannot, with the date each figure was last read from the live system. It exists so a reviewer does not have to take a marketing page at its word.

Last checked: 2026-09-30

StatementStatusWhere it comes from
Attorneys admitted to the register: noneMeasuredlegal_advocates table
Clause versions released by counsel: noneMeasuredlegal_release_records table
Attestations recorded: noneMeasuredlegal_attestations table
Counsel-released clauses in a production document: noneMeasuredlegal_document_clauses table
Public verifier for a release certificateDesigned, not builtVERIFIER_IMPLEMENTED is false in src/lib/release-certificate.ts
The release register is reachable from the applicationDesigned, not builtNo route or component imports the register modules
Registration of partner-owned contentDesigned, not builtStated as the next implementation step, not shipped
The event trail cannot be edited after the factBuiltAppend-only trigger on agreement_events, enforced by the database
Document fingerprints are timestamped by an authority outside PactermsBuiltRFC 3161, DigiCert with FreeTSA as fallback
Independent third-party security auditNever measuredNone has been commissioned
Paying customersNever measuredPacterms is pre-revenue

Measured zero is not the same as never measured

A figure marked measured was read from the live table on the date shown. A figure marked never measured has no number because nobody has taken one — which is a different fact, and printing a zero for it would be a claim rather than a measurement.

What Pacterms will not say

Pacterms does not describe anything it produces as admissible, court-ready, attorney-verified, attorney-approved, enforceable, tamper-proof or guaranteed. Attorneys release language; they do not approve or verify it. These words are blocked in the build, not merely discouraged in a style guide.