Honest status
Runtime and verification are tested. The device is specification and bill of materials. The hardware has not been produced.
ASSURANCE FACE
Field custody you can verify without the originating runtime.
VIDERIS holds evidence, intelligence, and verification to one record. Latin vīderis, “you will have seen.” Veil-and-verify resurrection: unstructured exports, scans, and decommissioned-system data in, labeled hashed cargo out. The software path is tested. The hardware is not yet produced. That distinction is the claim.
ASSURANCE FACE
Evidence, intelligence and verification, held to one record.
Esse quam videri: to be, rather than to seem.
VIDERIS — Vectorized Intelligence Deployment for Edge Reconnaissance, Inference, and Signaling. It is the assurance face of Blackbox Systems: the same deterministic discipline applied to how evidence is gathered, how intelligence stays bounded, and how a result is independently verified. It sits inside the Blackbox family and is held to the same canon. Implemented, deployed and proven stay separate states, and public language stays inside the strongest state current evidence can support.
VIDERIS device and integrityDEVICE AND STACK
Specify the kit.
Public language stays inside the strongest state current evidence can support. A bill of materials is not a finished appliance.
Edge target
NVIDIA Jetson Orin class edge. MIL-STD-810 is a target, not a completed qualification.
Cryptographic stack
SHA-256 and SHA3-256 dual hash, both checked. Ed25519 detached signatures, pinned to the RFC 8032 test vectors. Confidentiality is destinatario-scoped redaction, not encryption at rest: keys never transit.
FIPS posture
Level 1 validated-module build against AWS-LC-FIPS, CMVP #5314, where EdDSA on curve ED-25519 is an approved service under FIPS 186-5. Level 3 needs hardware — a software module cannot validate above Level 1 — so signing can delegate to a PKCS#11 token where the key is generated in-token and never exported.
Field form
IP67 ingress. 58 mm thermal receipt. Offline verify. Module bill of materials targets $2,507.
Someone else’s evidence, made checkable by whoever receives it.
A producer already proves what happened. What it cannot do alone is prove the record was not edited afterwards, or say who stands behind it. RedTail PrecisionLabs turns flight telemetry into per-axis evidence; VIDERIS seals that record under a dual hash and signs it. Neither side gains authority in the exchange: RedTail still never declares a finding, VIDERIS still cannot act. This adds custody, not judgement.
337 artifacts
One mission record sealed as a single cargo: 30.9 MB across every plot, export and analytical record.
8 stages
An inventory root over the path-sorted artifact list, the four analytical records, and each ACMI export on its own. A renamed file is as detectable as an edited one.
Tamper, located
One newline appended to one 3,293-byte ACMI export moved the manifest hash and named that export. The other 336 artifacts were cleared in the same operation.
Verified offline
The recipient checks the file. No API, no account, no network, no runtime of ours. That is a product boundary, not an engagement.
INTEGRITY
Tamper evidence is a test suite, not a marketing adjective.
Specs can adapt to Department of Defense or Department of War review, NVIDIA Jetson edge, and verification into Palantir Foundry or Apollo. Adaptation is not an award.
68 / 68
Tests passing, on each of the two cryptographic backends.
16 / 16
Planted defects killed. The suite is checked by breaking it on purpose.
5,000 / 5,000
Single-byte tampers caught.
Execution authority: none
By design. A witness that can act is not a witness. No targeting, no electronic warfare, no kinetic function.