Olivium · Receipts

The receipt layer is the trust layer.

Every important action can become a record: upload, share, open, view, sign, approve, revoke, complete, or export — owner-scoped and built to be preserved.

Receipts are owner-scoped: you see only your own account's records. Nothing here is fabricated.
Receipt timelineProtected
1Action happensUpload, share, view, or sign.
2It's recordedAn event joins the trail.
3It carries a referenceEach event has its own reference.
4It's preservedThe trail is append-only.
What becomes a receipt

The actions that matter, on the record.

A receipt isn't paperwork — it's the proof that the work happened, and who touched it.

Upload

A file enters your owner-scoped vault.

Share

A controlled link is created and sent.

View

A recipient opens a shared file or room.

Sign

A document is signed or completed.

Approve

An internal review is recorded.

Revoke

Access is cut off, on the record.

Owner-scoped, append-only, yours.

The trail is built to be preserved and to belong to one account. No cross-account mixing, no editing history out from under you.

Enforced at the database layer — every record is scoped to its owner.
  • Owner-scopedYou see only your own records.
  • Append-onlyBuilt to be preserved, not rewritten.
  • ReferencedEach event carries its own reference.
  • TimelineA clear order of what happened.