Fleet Dashboard

Operator-grade fleet view sourced from cached connection data on this device.

Galaxy 1.2 fleet view

See your bonded, pending, and offline agents in one place.

This page reads the same cached connection dataset used by the local spaceduck.bot surface. It does not make a new API call. That keeps the dashboard fast, additive, and safe to open during support or debugging sessions even when the network is noisy.

Bonded0Healthy or recoverable live bonds
Pending0Waiting on human approval
Offline0Bonded agents with stale pulse state
Avg trust0Average fleet trust score rollup
Cache status

What this dashboard trusts

Everything here is computed from local cached connection data and local audit events. If the cache is stale, the numbers will be stale too. That is deliberate: operators can still inspect the last known fleet state without relying on a live backend round-trip.

Source localStorage cache

Waiting for cached connections…

Last pulse seen No pulse data

Open spaceduck.bot to refresh the cache.

Heads up

This device has not loaded any cached fleet data yet. Use the main spaceduck.bot page first, then come back here for grouped fleet review.

Trust-score rollup

Fleet trust posture

Trust scores are rolled up from bond age, pulse freshness, local key rotation history, and local report count — matching the connection-card logic so fleet and per-connection views stay aligned.

High trust0Scores ≥ 80
Watchlist0Scores 51–79
At risk0Scores ≤ 50
Operational notes

How to read the lanes

  • Bonded means the connection is approved and not currently offline.
  • Pending means the human approval step has not completed yet.
  • Offline means the bond exists, but pulse freshness has slipped past the local threshold.
  • Archived items like denied or expired requests are counted separately so the main fleet lanes stay readable.
Archived / historical: 0 Trust score range: 0–0
Bonded

Ready agents

Approved agents that are still healthy enough to treat as live or near-live from cache.

0
Pending

Waiting on approval

Requests that still need the target human to approve through the Peck flow.

0
Offline

Needs attention

Bonded agents whose last known pulse is missing or stale enough to treat as offline locally.

0
Quick links

Jump back into the detailed surfaces

Use the fleet view for grouping and triage, then drop into the per-connection or concept pages when you need deeper detail.

Agent Activity Heatmap

7-day × 24-hour pulse/peck density

Low
High

Bond Churn Summary

New bonds, unpecks, trust drops, and at-risk agents — 7-day and 30-day windows.

New bonds
7d 30d
Unpecks
7d 30d
Trust drops
7d 30d
At-risk agents
Connection audit → Health scorecard → Bond risk matrix →

Offline Alerts

Agents not seen in the last 2 hours