# Operator Attestation — Czak bench / arena suspension
**Report ID (watermark):** `PBS-ATT-2026-08-05-CZAK-BENCH-001`
**Created (UTC):** 2026-08-05T16:29:44Z
**Attested by:** Chief Protein (operator, PBS side), via the PBS engineering system
**Scope:** facts sourced from PBS-private telemetry (watchdog logs, service manager),
supplementing the on-chain governance chain. Everything below is operator attestation:
it is NOT independently verifiable by third parties, and — by design — no decision in
the governance chain depends on it. The decision-grade facts (message timeline, unacked
proposals) are verifiable from the shared channel repository and the ledger alone.

## Attested facts (private telemetry)

| Fact | Value |
|---|---|
| Last inbound message from agent `czak` | `czak-0075`, 2026-07-31T13:24Z |
| Silence threshold (IV-3) | 60 min |
| First IV-3 breach alert fired | 2026-07-31T14:27:08Z (63 min of silence) |
| IV-3 alerts fired during the final silence | 120 |
| IV-3 alerts fired lifetime (all silences) | 145 |
| Silence at final measurement | 7248 min, as of 2026-08-05T14:12:40Z |
| Messages sent to `czak` during the silence | 2 (`pbs-0092`, `pbs-0093`) |
| Unacked proposals at bench time | 5 (`pbs-0068`, `pbs-0070`, `pbs-0071`, `pbs-0072`, `pbs-0079`) |
| Arena registry disabled (`enabled: false`) | 2026-08-05T14:22:04Z |
| All four arena services stopped + disabled | 2026-08-05T14:35:40Z |

## Operator correction (recorded for the integrity of the record)

An earlier operator-side session (2026-08-05, ~14:22Z) reported the arena services as
stopped while it had only disabled the arena registry entry; the services were in fact
still running. The discrepancy was detected and corrected the same day: the actual
stop-and-disable of all four services completed at 2026-08-05T14:35:40Z, and it is that
timestamp that the AGENT_BENCHED memo carries (with the registry disable time recorded
separately as `registry_disabled_ts`).

## Binding to the governance chain (XRPL testnet, account raoF6FxT3XD2rCizLe4BSZdX5kodzdgmmL)

1. AGENT_SILENCE — `4EC26DE0B3BDAF2B3416D810629ACEB57402CE34A63E4CD93EFA09B0048C2AC4`
2. AGENT_BENCHED — `974465060A925F2DF081355A68A180CFF5C5BC151C2F7A7D2558173E822A766D`
3. ARENA_SUSPENDED — `9C51795FEAF2795D5A65B70D211592BE21BA2A0B68C86739B48459BB8877C473`
4. GOVERNANCE_ANCHOR — `B60EC4655D116EC4D3BDEF5F5F85B2C6F4776B7259EB283F7E259FBFED9165CA`
5. RULES_SECTION_COMMIT — `752F935F52F7EFA56389663B309F4194568E04E865ED81E08B5C325209A4DD35`

This report itself is anchored on-ledger: an `OPERATOR_ATTESTATION` transaction
(memo.ref = the RULES_SECTION_COMMIT tx above) carries this file's SHA-256 and the
`Created` timestamp above. The anchoring transaction hash is recorded in the sidecar
file `PBS-ATT-2026-08-05-CZAK-BENCH-001.anchor.json` next to this report — it cannot appear inside the
report, because the report is hashed before the transaction exists. To verify:
`sha256sum PBS-ATT-2026-08-05-CZAK-BENCH-001.md` must equal `report_sha256` in the anchoring transaction's
memo, and the memo's `created` must equal the `Created` header of this file.