Fleet analyst
Ask what the fleet did.
The model reads the fleet subgraph through The Graph’s Subgraph MCP server — mints, record writes, role changes and heartbeats, in one index. It answers in sentences and shows the GraphQL it ran, so you can check it.
reading capsulefleet.eth (the default — connect a wallet for yours)
Mints come off CapsuleMinter; record writes and role changes come off each owner’s PermissionedResolver. Nothing emits both. “Did anything stop beating before it was recalled?” is a join across two contracts on two different cadences — which is a field in the index and a program everywhere else.
Each of these needs history, not state — the part a contract cannot answer about itself.
Every answer carries the GraphQL that produced it. An answer with no query under it did not read the chain, and the tag under it says so.
The fleet dashboard reads the same subgraph, scoped to the same name. The analyst is not a second source of truth about the fleet — it is a second way to ask the first one.