Image operators
Error-level analysis, 8x8 boundary energy, clipping, edge and noise maps, black-point and gamma sweeps. Each reports a value; a highlighted region is a candidate for grading, never a verdict.
IMPLEMENTATION EVIDENCE
Current implementation, verification and stress-testing evidence.
The product record distinguishes implemented controls, executed engineering evidence and bounded operational activation so technical claims can be reviewed without turning them into broader certification or deployment claims.
MEASUREMENT METHODS
What the operators read — and the restraint they run under.
The method stack is deterministic measurement, and the non-authority posture is enforced by the runtime itself, not asserted in prose.
Audio operators
Deterministic STFT spectrograms, windowed signal metrics, and on-device transcription kept answerable to the measured signal. Unsupported formats are declared, not reconstructed.
Cadence and correlation
Perceptual frame cadence (duplicate-like / cut-like) and multi-event temporal correlation that returns a bounded result class with a mandatory limitations statement — comparison only, never causation or attribution.
Enforced non-authority
The runtime cannot write a conclusion word. Prohibited-term guards, a non-authority notice compiled into every packet, an open human review that revokes delivery authority, and method internals that cannot surface to a client record. The restraint is code, not a style guide.
THE BASELINE
This record was built CPU-only.
Everything above was produced without a GPU. The number to read is not the ceiling — it is the floor accelerated compute multiplies.
Built CPU-only
The implementation and every executed campaign above were produced without a GPU. The record is the baseline; accelerated compute is the multiplier on top of it, not a prerequisite that was missing.
Runs where it must
The same deterministic methods run on a server, a Windows offline command line, and a phone. Portability is a property of the method, not a port.
Reproducible by the reviewer
Fixed parameters mean the same input yields the same output on any machine. A reviewer recomputes rather than trusts; receipts and manifests are SHA-256 bound.
EXECUTED PROOF INDEX
Different campaigns. Different proof semantics.
Bar length shows execution scale only. Stress corpora, independently verified assurance, and signed release verification remain separate evidence classes.
4 segments / cycles4 workers0 observed failuresPASS
receipt 6b224a11b427a74bfcd9996e2fb66e278c08c3bcf01b29bbaf06abc6fedd60e472 segments / cycles4 workers0 observed failuresEXECUTED_ARCHIVED
20 segments / cycles2 workers0 observed failuresEXECUTED_ARCHIVED
80 segments / cycles5 workers0 observed failuresVERIFIED
release 3526232b2dbb3115e392cc3c12a86ee696e57840c3fefaa7ea972be444af438aOpen the 20M execution reconstructionCampaign counts are shown side by side for scale. Distinct evidence classes are not semantically additive and MUST NOT be represented as one combined proof claim.
Inspect the machine-readable proof indexRelease export
3526232b2dbb3115e392…44af438aRelease manifest
156bec2bbbca309d5720…640f8fd4Source revision
a3ebe984cf713b6fdf20…4975d84dReceipt-chain semantics
Canonical bbs.receipt.v2 records deterministic sequence, linkage and independent chain-verification behavior.
ImplementedCrash-safe persistence
Serialized append, chain-head allocation, advisory process locking, fsync durability and torn-tail handling are implemented in the current source.
ImplementedDetached signatures
Ed25519 signing and public-key verification are separated from the originating runtime and private signing key.
ImplementedTransactional signed journal
Receipt construction, signing and durable append execute under one chain-head lock and append unit.
Implemented; operator-controlled activationDetached release verification
Declared ZIP payloads, self-hashed manifests, optional detached signatures and embedded receipt verification are implemented.
Implemented; default packet compilation under operator controlLegacy migration
Migration preparation preserves legacy bytes and canonical-row digests while historical and migrated chain state remain separately identified.
Implemented preparation pathLarge-corpus assurance
Preserved campaigns include independently verified assurance, segmented stress corpora, and a detached signed external-run release. Each class is presented separately below rather than collapsed into one aggregate proof number.
Executed engineering evidenceWHAT GETS READ
A catalog of what the measurement surfaces — by family.
Each is a reading the operators can raise as a candidate, never a verdict. The runtime cannot write a conclusion word — “forged,” “tampered,” “guilty” are refused in code, not by policy. Grading, and the finding, stay with a named person.
File identity
Extension-vs-signature mismatch, zero-byte, truncated header, double extension, unsupported container.
Time
Future timestamps, internally inconsistent times, metadata-vs-filesystem conflict, impossible simultaneity across independent records, sequence gaps.
Metadata
Absent EXIF/GPS where expected, edit-software indicators, metadata-strip indicators, internally contradictory fields.
Encoding
Re-encode signatures, multiple-JPEG-save artifacts, transcoded-audio markers, atypical bitrate or sample rate.
Duplication
Exact duplicate by hash, same name with different hashes, near-duplicate suspects by deterministic metric.
Lineage
Derivative without source, missing reproduction parameters, output hash missing, report without references.
Integrity
Hash mismatch, original appears modified after intake — the breaks that end a chain of custody.
Audio & visual
Hard-cut / splice boundaries, clipping and saturation, high transcription uncertainty, underexposure, posterization.