MONTHLY WEBSITE-CARE REPORTS · FOR WEB AGENCIES

Your agency writes the report.
Your client can verify it without you.

FleetOpus is a white-label monthly website-care report system for web agencies. You finalize the report; your client gets an opaque share link and can verify it themselves — no account, no login, no trust required. Every sealed byte is chained by SHA-256 and the public verifier walks the chain end-to-end.

GENERATESEALVERIFY

Live chart — fleet-mr4x48nr

witness ledger · awaiting gated actions…

STRIP 001▸ active

Generate

The monitoring engine drafts the month's care report on the agency side — coverage, incidents, latency, the things the client actually reads.

STRIP 002▸ active

Seal

The agency reviews, finalizes, and the report is sealed: a SHA-256 chain that the agency can never silently edit after the client has seen it.

STRIP 003▸ active

Verify

The client opens an opaque share link — no account, no login. They see the same bytes the agency sealed, and the verifier proves nothing in the chain has been touched.

PROVENANCE · HOW THE CHAIN WAS BUILT

The care-reports system is built on top of an orchestration backbone that ran for 40 days.

Before FleetOpus pivoted to care reports, it ran a 10+ agent fleet in production for 40 days — quorum-ratified decisions, witnessed receipts, no unexplained messages. A real run is replayed below. The care-reports system inherits the same seal: one finalizer, a SHA-256 chain, a public verifier that walks it end-to-end.

REC witness bus · fleet-mr4x48nrreplayable ↺

$ opusd fleet run reviewed-fleet.json "merge the notes, delete the obsolete drafts/"
fleet-mr4x48nr spawning 3 runners from template "reviewed-fleet" (quorum=2)
WORKER1 R-ASKfs_delete {"path":"drafts"} — ratify with fleet_vote(msg_id=…)
⤷ ACK reviewer2 12:37:25 · read via fleet_inbox
⤷ ACK reviewer1 12:37:25 · read via fleet_inbox
⤷ APPROVE reviewer1 “inside the workdir; deletion explicitly called for by the task”
⤷ APPROVE reviewer2 “inside the working directory and part of the stated fleet task”
gate.approvedfs_delete — quorum 2/2 → the delete runs (and only now)
fleet-mr4x48nr complete: worker1 ✓ reviewer1 ✓ reviewer2 ✓

Silence times out to deny. Self-votes don't count. Nothing outside the whitelist runs. Every line above is a receipted message you can replay.

See the proof — a real fleet run, tamper-evident →

Night navigation chart: an octopus air-traffic controller routing a fleet across radar rings and waypoint fixes — the metaphor for the orchestration backbone FleetOpus is built on — Chart I — the controller that ran the proof-of-concept

PROVENANCE

Built from operational history, not a whiteboard.

The seal behind every FleetOpus care report is the same one that protected a 10+ agent production fleet for 40 days — quorum-ratified decisions, witnessed messages, a chain that a verifier walks end-to-end. The care-reports product is what survived the pivot.