Skip to main content

What our own guards caught

No vendor publishes its defects. We do, because every row below was caught by our own harness, closed inside its release, and proven red so it cannot quietly return; the confession is the credential. Three of these were attempts, two by the builder's own hand, to homogenize this ledger's history, each now frozen by a law that fails red on the next attempt.

R92-b, closed

A totals guard homogenized historical ledger rows to the current figure for a dozen releases; the fix scoped live claims to the newest block and restored three recoverable figures, frozen verbatim.

Second wave

While a seal ran beside live edits, the and rows were rewritten to a later figure; the writer was never identified, so the defense became structural: every sealed figure joins the freeze list the release after it seals.

Third wave

The builder homogenized history himself with a global restate; caught within minutes, both rows restored, and the restate became a tool that can only touch the newest block by construction.

The stray brace

An excision left the estate builder syntactically dead for a full release while dev-null invocations swallowed the crash and stale outputs kept the suites green; only the cold run, nothing cached, died loudly on it.

The one-in-sixteen flake

A forged-signature probe appended a constant and collided with the true tail one time in sixteen; the battery surfaced it at depth on run six, and the forgery is deterministic now.

Lexicographic crowning, twice

Two independent pickers crowned an old release over a new one by string order, first in the owner cockpit which exposed it on first light, then in the packager; both numeric now with the lesson cited.

The colon-greedy parser

A negated class in the ledger parser swallowed whole release blocks; the cockpit rendered the gap on its first render, and the parser anchors on structure now.

Cold starvation

The independent battery died at suite twenty-one on a five-file estate snapshot frozen four eras back; the whole dist ships now, and the cold run completed.

Why this page exists

A guard that has never caught anything is a decoration. If our marketing ever contradicts this page, believe this page.

You do not have to take our word for it. Every figure on this page is computed at build or wears its label, and the harness that proves it ships with the product.

Also from AssetShop

Fourteen other products, none of them part of EOS. Separate products, no shared runtime, tenancy or credential path. Nothing below is included in an EOS evaluation or an EOS contract. Each carries its status, and nothing is called built until it is.

Enter the consumer layer at assetshop.eth EOS is the Enterprise Operating System. The brand layer it belongs to is name-native. Past that line the rules are different, and it is built by Shadow Key.