BLACKWAVE // CAMPAIGN 2026-08

FOLLOW THE
EVIDENCE.

Different hardware. Common language. A distributed physical operating model by fR3k.

THE THESIS

01 // SYSTEM

The network is not the system.

Connectivity is a bearer. BLACKWAVE owns the authority boundary: identity, capability, authorisation, transport, state, sessions, observability and recovery.

02 // EVIDENCE

Capability is earned.

Build, probe, flash, boot and physical validation are different states. One cannot silently promote another.

03 // FLEET

One fleet, many machines.

ABYSS, RELAY, NEXUS, SPECTRE, SCOUT, SIGNAL, VIGIL, CHRONOS, PULSE and PATHFINDER specialise instead of pretending to be identical.

THE CURRENT STATE

SOFTWARE BUILD

46 release artefacts

Public build ledger dated 2026-08-29. Source and evidence links live on the canonical BLACKWAVE page.

TESTING

82 pytest passes

Tests are evidence of tested software paths—not proof that every physical device is field validated.

DISCLOSURE

Blocked stays visible.

SPECTRE and other physical gates remain evidence-gated. Campaign renders are synthetic HyperFrames compositions, not physical proof.

THE NEXT SIGNAL

Follow the public validation sequence: inspect the contracts, watch the build gates, compare the evidence, and challenge the claims.

BLACKWAVE is the engineering proof surface. MCP Intelligence is the commercial autonomous-agent systems layer.