Agreements you can verify later

Agreements you can verify later

Draft together, discuss inside the case, close it by poll, and anchor the result so that later changes are detectable.

Matter #CA-8891
CaseAnchor app home screen
Core Pillars

Four things the platform does.

Collaborative Drafting

One shared document, with the discussion kept next to the clause it refers to instead of in a separate email thread.

Continuous Sync

Hashed & Signed

The finalised agreement is fingerprinted and sealed, so a later change can be spotted.

Verifiable Commitment

Polls to Close

A poll attached to a message settles the open question. Each option is hashed and the signed result travels with that message.

Recorded Outcome

Keys Held Outside

Agreement content is encrypted before it is stored, and the key is held outside the application.

Keys held outside
Fast-Track Alignment

Close the open question with a poll

Long email threads lose the decision. CaseAnchor attaches a poll to the message carrying the question, hashes the options, and signs the result.

  • The poll sits next to the clause it refers to, so the text and the discussion stay together.
  • A poll is signed as sign(hash(message_body) + '.' + hash(option_body)).
  • Votes have no root hash of their own: they are already covered by messages_root_hash.
Poll TrackerClosed
2/2Votes Cast
Next step: anchor the casePending: anchor
File Storage
Attachments linked to the case
Fingerprint
Per case
Verifiable
Checkable later
Key custody
Held outside
Data Protection

Encrypted fields, keys kept outside the app

Agreement content is encrypted before it is stored, and the encryption key is held outside the application.

Encrypted at rest

Agreement content is encrypted before it is stored.

Keys held outside

The encryption key is not kept inside the application.

One Case

The case holds the agreement and everything around it

A case carries its participants, public keys, agreements and messages. The anchor payload structure is defined by the record specification.yaml.

Structure: case_info, participants, public_keys, agreements and messages.
Attachments are linked to the case rather than copied around.

Services Agreement

fingerprinted on sign-off

Anchored

Mutual Non-Disclosure Agreement

poll attached to a message

Voting

Work Order

awaiting signatures

Review
Where it fits

Built around agreements, not paperwork

Drafting, discussion, polling and anchoring are the same flow whether it is a small everyday agreement or a long negotiation.

Small business

Everyday agreements such as sales or services that should not be lost in a mailbox.

  • Simple shared drafting
  • Poll-based sign-off
See the specification

Legal teams

Longer negotiations that need a record you can point to months later.

  • Case-level discussion
  • Hashed commitments
Read the security notes

Organisations

Deployment and governance for teams running the platform themselves.

  • Deployment options
  • Key custody via an external vault
Contact us
FingerprintOn every case

A finalised agreement can be recognised later.

VerifiableCheckable any time

You can check a record against the published specification.

Tamper-evidentAlteration is detectable

A change after sign-off does not pass unnoticed.

PrivateEncrypted at rest

Agreement content is encrypted before it is stored.

“Anchoring has to answer two questions: does this record exist, and has it ever been altered. The register is built to answer exactly those two.”
The CaseAnchor specification
the published specification
Open specification

Check how it is done

The rules for how a record is kept are published as a versioned specification.