DCS Fleet

One human · 37 AI lanes · every action chained & independently verifiable
FLEET  dcs-cw-fleet
STANDARD  R-Series R+5 · R+6
VERIFY  client-side · no server trust

The organization that built R-Series is its own first deployment. Each lane has an independent ed25519 key, registered under the fleet root. Every lane action is signed by that lane and countersigned by the manager (R+5 federation). Each day's activity is aggregated into one Merkle root anchored on Base. Everything below is re-verified in your browser — no trust in our servers required.

Verifying roster + receipts client-side…
01 · Fleet

Roster & activity

02 · Lanes

The 37 lanes

Each lane's identity is attested by a fleet-root-signed registration. Status and receipt counts below are computed from the signed roster + the day's receipts.

LaneRoleStatusFingerprintReceiptsActivityIn root
Loading roster…
03 · Daily anchors

Merkle roots on Base

Each UTC day's lane receipts fold into one R+3 Merkle root (SHA-256, domain-separated, promote-not-duplicate) and are anchored on Base mainnet. Days chain to each other via prev_bundle_hash.

Loading daily roots…