A record your CA can read
Every change leaves a proof record. Here is what’s in one.
Checked and recorded by the elan1 layer. Records are hash-chained: each carries a fingerprint of the one before it, so any later edit to the chain shows.
Illustrative · design preview
- Sequence. Its place in your site’s chain. #8,413 of 8,413.
- Changeset. Exactly what changed: fields, scripts, rules, columns.
- Base hash. The schema the change was built against, read again at publish to make sure nothing moved.
- Asked by. The person, the channel and the time.
- Checks. Each check’s result, with the suite version and the data it was computed from.
- Approved by. The named approver, the one-time code, and what they looked at before deciding.
- Snapshot. Taken just before publish, kept for the undo window.
- Inverse. How to undo, built from the change itself, never by a model.
- Meter line. The credits used and the invoice they appear on.
Watch a chain being written.
Each row’s SHA-256 is computed here, in your browser, from the row before it.
Illustrative
Proof records · hash-chained
| # | Change | Outcome | By | Undo / cost | Chain |
|---|
What we don’t claim yet: records are tamper-evident, not tamper-proof, and verification today runs on elan1’s own records. Independent third-party verification comes with elan1 L2. About elan1
Start with one process. Add the next when it holds.
10 design-partner slots for Phase 1. 90 days free, onboarding done for you, a named founder on WhatsApp.
Not for service firms under ₹1 crore, firms above ₹250 crore, or anyone whose CA won’t take a call.