Tamper check
Logbook — 350 entries checked ⓘEach logbook entry locks the one before it. If an entry is edited or torn out, the links break here.
intact Every entry links to the one before it. Latest entry: #350A short code computed from a file's exact contents. Change a single character and the code changes completely. b83b7c8492272ad9e404c7b4797e433eaf4136a59e3cd5027afeda595fdb66b6
Each entry locks the one before it, so tearing out a page leaves a gap you can see. What it cannot do on its own is stop somebody who controls the whole database from rebuilding the logbook from a chosen point — every page would agree with the next, because they were rebuilt together. That is what the published totals below are for. The other known answer, signing each entry with a key the database never holds, is not built, and we would rather say so than let you assume otherwise.
Published totals ⓘThe logbook's running total, written down outside the system at chosen moments. A rebuilt logbook cannot match a total that was already written down.
all match 2 of 2 published totals still match what this logbook adds up to.
| At entry | Written down | TotalA short code computed from a file's exact contents. Change a single character and the code changes completely. | When | Still matches |
|---|---|---|---|---|
| 67 | 2026-10-26 | 6cd45ee8fd0f…6cd45ee8fd0fd130d9edd40f9625f92942b5dbd203abdafe652005bd7daaf371 | after accrediting 1.0 | yes |
| 350 | 2026-10-26 | b83b7c849227…b83b7c8492272ad9e404c7b4797e433eaf4136a59e3cd5027afeda595fdb66b6 | end of seed | yes |
At chosen moments the logbook’s running total is written down somewhere else. Once a total is out, no amount of rebuilding inside the database can make the logbook add up to it again, and the earliest total that disagrees says roughly when the rebuild happened. To be clear about what is built: the mechanism works, and you can watch it catch a rebuild. Where the totals should actually be kept — a witness service, another office’s system, a partner’s, a printed page in a binder — is a decision nobody has made yet. Right now they sit next to the database, within reach of anyone who can edit it, which makes them worth nothing as assurance. The mechanism is the same wherever they go.
Records ⓘThe data in the database still matches what the logbook recorded when it arrived. An edit made directly in the database — behind the system's back — shows up here.
matches Overhead detector — version 1.0 62 documents checked · accredited
seal intactA fingerprint of exactly what was decided and the evidence it rested on. Edit anything afterwards and the seal no longer matches. Accredited by Accrediting official, judged as of 2026-10-24
matches Overhead detector — version 1.1 62 documents checked · submitted
matches Overhead detector — version 1.2 62 documents checked · submitted
matches Overhead detector — version 1.3 62 documents checked · under review
matches Coastal vessel classifier — version 2.3 59 documents checked · 1 allied partner approval checked · submitted
Latest logbook entries ⓘEvery action ever taken in this system, in order. Each entry locks the one before it, so removing or editing one leaves a visible gap.
| # | What happened | Who | FingerprintA short code computed from a file's exact contents. Change a single character and the code changes completely. |
|---|---|---|---|
| 350 | Version submitted | ML engineerml.engineer@coe.ic.gov | b83b7c849227…b83b7c8492272ad9e404c7b4797e433eaf4136a59e3cd5027afeda595fdb66b6 |
| 349 | Allied partner approval applied | Allied partner reuse (automatic)recognition-engine | 40b76b48dfe3…40b76b48dfe3b54f1146bd2115baa2a1ca63a14c12c23c7c9e428cc146aa8bac |
| 348 | Document added | ML engineerml.engineer@coe.ic.gov | a7f901eec6a6…a7f901eec6a68cb4b2937e7388c289704dd86d7547322d6e701c50cece2f2d5a |
| 347 | Document added | ML engineerml.engineer@coe.ic.gov | fe2c8df3a4c6…fe2c8df3a4c6d280286b360c825467a7b65d8a1f31ca6b9c9ff4dc0af10250c0 |
| 346 | Document added | ML engineerml.engineer@coe.ic.gov | d8a73fda714d…d8a73fda714de0ef810874c0082eab8afb62eeae924969c289c42206260d5bb5 |
| 345 | Document added | ML engineerml.engineer@coe.ic.gov | dbbe1b9d9f39…dbbe1b9d9f395312e8efa748eb60646785639b0bcbc547056531ac9a0c8ebbab |
| 344 | Document added | ML engineerml.engineer@coe.ic.gov | b1a782018fad…b1a782018fad8fdcef50a9857074285eaab1953c3dc8881df83bb0b7f2f43725 |
| 343 | Document added | ML engineerml.engineer@coe.ic.gov | dec6c5367bb1…dec6c5367bb1785e9747ded3ec71c254e90acca8446a38fd4fbadd08713949d7 |
| 342 | Document added | ML engineerml.engineer@coe.ic.gov | 09b1848539a1…09b1848539a10f04787b7ed9748464edbad170c8bd5c6c371244ebfff71a3751 |
| 341 | Document added | ML engineerml.engineer@coe.ic.gov | f9aab9837220…f9aab9837220a40f56b67e418c9a3e1f28633550c37d97b893c9237b122d1de5 |
| 340 | Document added | ML engineerml.engineer@coe.ic.gov | deb31b72883b…deb31b72883bdc481e5a64d0f47f6e63221a9cb1513dff0ecfade7cd412e59af |
| 339 | Document added | ML engineerml.engineer@coe.ic.gov | 4d89d4893833…4d89d4893833a12022ad3cb7067797aca625a0049ce98685cf137ec78bb99b9b |
| 338 | Document added | ML engineerml.engineer@coe.ic.gov | 899e69488ae8…899e69488ae8285031af55f71bdfce9cc761f303200cf491a7d8aee4e7fc5f42 |
| 337 | Document added | ML engineerml.engineer@coe.ic.gov | 6f336f918a14…6f336f918a14cbec1727927d2f924414203cddea1090cb9d35b8cb8d5cb6dd24 |
| 336 | Document added | ML engineerml.engineer@coe.ic.gov | e55df1f6eb58…e55df1f6eb5842ab7fe0365776a91d99c2fd9ce9f42346237d3267828b4bed80 |