Skip to content
8BraidCreators of 8DB
8Braid / Evidence / reviewed September 16, 2026
Evidence / reviewed September 16, 2026

Pick the question.
Follow the evidence.

Start with the behavior you need. Each public record identifies what was measured, which implementation produced it and how to inspect the result.

Evidence by decision

Make the next technical discussion concrete.

Record representation

What happens to storage size?

A controlled 115-byte record becomes 131 bytes under both key-establishment paths with the same record cipher. Key envelopes, signatures and full-database costs have their own accounting.

Inspect the size comparison ↗
Algorithm behavior

Do implementations agree?

ACVP demonstration-service records and interoperability checks document tested algorithm behavior. The repository includes public verification instructions and raw inputs.

Inspect implementation evidence ↗
Node-to-node exchange

Where does protection begin?

The source-bound explanation traces a recipient-specific encrypted message, independent receiver storage keys and the current lexical admission boundary.

Trace the protection path ↗
Two physical hosts

What survived receiver interruption?

The retained 512-record experiment finished with all exact typed records on both hosts after a receiver-process kill and same-store reopen.

Inspect the recovery record ↗
Stored-data migration

Can reads continue during a transition?

Four retained, four-CPU-limited 100,000-record runs cold-verified exact data. One met the declared read deadlines; three had misses. The public record keeps those outcomes and their conditions visible.

Inspect the migration runs ↗
Database workloads

How does the engine perform?

Browse the measured workload comparisons, including their hardware, workload definitions and differences between the systems being compared.

Explore database measurements ↗
Use the evidence well

Match the result to the decision.

Source: a result belongs to the implementation and configuration recorded with it.

Workload: a record-cipher measurement answers a different question from a governed write or network exchange.

Reproduction: public artifact verification checks retained evidence. Fresh execution of the engine needs the corresponding evaluation build.

Negative results identify the next engineering question. For the current integrated scope and remaining qualification, use the dated capability record.