Live status board for this fleet: who is running, what is scheduled, and what changed — refreshed automatically.
agents · environments · projects — auto-generated from work/fleet-map/fleet.yaml
panel toggles (per view)
home (landing) — priority order
landing (CaDa 11-02): agents (ruling 10669 — click a card to expand its board; pin a card to keep it open side-by-side for comparison) + projects + life — everything stays toggleable via panels ▾, toggle order = priority
loading…
L0 — is anything wrong? · fresh <1h · settling <6h · stale <48h · gone >48h · click a row → L1 entity card · events: 0 today
fleet status mix
projects by state
probe freshness
health gauges shared threshold map
life cada's day — edit work/life/cada-input.yaml
fleet
health gauges — shared threshold map
projects
life — per-bot lane state
deep docs
actions
File a quest into tasks/ via GitHub API (token stays in your browser localStorage, used only for this repo)
quest for
goal
releases
zed-hermeszed-hermes-35eb4c7— LIVE CROSS-PLATFORM: win x64 zip (~123MB) + linux x64 tarball (519MB, sha c9ca8954…f978 round-trip-verified) + SHA256SUMS.txt (API-verified; private repo needs GitHub login to view) · linux tarball attaches on land
sha256verify via SHA256SUMS.txt in the release assets
bots post questions here — NOT in the Telegram chat · CaDa answers whenever he wants, right here · bots: ask only what needs HIS decision · every agent reads the board each tick (30s refresh)
bots: ask a question
open questions
answered
404 — view not found
no view matches ·
bot state timeline
memory / self-improvement autonomy
zed-hermes (workbox lane)
org calendar — rhythm + deadlines
rhythm from the shared calendar (weekly rhythm) · deadlines with owner + countdown · partition-class entities carry "syncs on wake", not deadlines
ops calendar — cron schedules (§5: from fleet.yaml calendar: + running cron defs on each node)
lane per bot, sorted by cadence hour · stale cadence = node's cron host down — cross-check probe light on overview