The record
The audit trail
is the product.
A newbuild's technical dialogue outlives the people who had it. Decklog keeps every comment, query, approval and revision as one event on an append-only, hash-chained record — so two years on, you can show who agreed to what, and why.
Append-only
Nothing is edited or deleted. A correction is a new event that supersedes the old one — the original stays on the record, visible.
Hash-chained per project
Each event carries the hash of the one before it. Tamper with any entry and the chain breaks — the console flags it instantly.
One event per comment
Raised, classified, linked, answered, signed — each step is its own timestamped event, attributed to a person or to Decklog.
A name on every decision
Nothing ships on model output alone. Sign-off is human, recorded and permanent — who closed it, when, in what capacity.
A project's deck log
- #157 2026-06-08 09:13 comment.extracted C-143 DECKLOG
- #158 2026-06-08 09:14 comment.linked C-143 DECKLOG
- #159 2026-06-08 09:41 conflict.flagged C-143 ↔ D-031 DECKLOG
- #160 2026-06-09 11:02 response.drafted C-139 DECKLOG
- #161 2026-06-09 14:20 response.signed C-139 J. LINDQVIST
Verification isn't a marketing claim — it's a function of your console. Inside Decklog, the chain check runs on every project and shows ● RECORD VERIFIED the moment the hashes line up, or flags the break if they don't.
06 · Who it's for
Built for the design office.
Everyone joins the record.
Design offices
Twenty to two hundred engineers answering to a yard, an owner and class at once. Every comment lands on your desk and every answer carries your name. Decklog makes your office the keeper of the record — without an engineer spending Fridays filing it.
Yards
Technical queries answered in days cost weeks at the block stage. When the yard joins the shared record, the answer is findable before the steel is cut.
Owners & class
Supervision runs on trust in the record. Audit any decision back to its origin — who raised it, who closed it, what it touched.