Skip to content
8BraidCreators of
8DB

Journal series · 3 articles

Fielded Systems

Read the complete sequence or enter at the question most relevant to your architecture.

Engineering note

Fielded Systems

One Component in the Boundary, No Keys in the Field, and an Artifact for Every Question the Assessor Will Ask

A data layer for platforms that operate cut off, keep records longer than the algorithms that protect them, and have to be assessed on what can be shown. 8DB puts persistence, governance, protected transfer, recovery and diagnostics in one qualified runtime, leaves no key table on the platform, and answers each of the seven questions an assessor asks with an artifact that already exists. Here is what goes in the binder, question by question.

14 min readTested claims · An evidence page per question · Four-host release harnessRead article
Engineering note

Fielded Systems

One Sealed Store for Every Shape of Data, and It Works With the Network Gone

Edge nodes hold telemetry, geospatial data, imagery, relationships and time series, usually in five engines with five governance models and no connection to the services that were supposed to protect them. 8DB holds all of it in one sealed store, survives power loss, works with no reach-back, and moves sealed intelligence between nodes when a link appears. Each of those is a tested claim an independent evaluator can run on an isolated host.

6 min readTested claims · Evaluator harnesses · Explicit non-claimsRead article
Engineering note

Fielded Systems

Before a Fleet Trusts the Model, It Has to Trust the Data Under It

Predictive maintenance for a fleet lives or dies on whether a maintainer believes the alert, and that belief rests on the data layer, the part nobody designed. 8DB gives a sustainment program a substrate in which telemetry, subsystem relationships and events are captured on the platform, sealed at write, kept from leaving where they may not go, attributable to their source, and provable to a reviewer months later, with every one of those guarantees tested under independent evaluation.

7 min readTested claims · Deployment boundaries stated · Model layer excludedRead article