The Harness

f453452 deployed build
working tree UNKNOWN — no git here

2 decisions need you · 2 instruments red3 other thing(s) only glanced at — see Health.

What needs me

Decisions actually waiting on your ruling — not the marker count. Rule them →

why the distinction matters

Those two counts differed by 135× for a fortnight and the wrong one was on the red row.

BLOOM.md — 1 pending

tools/game_factory/BLOOM.md

DRIFT_BOARD.md — 1 pending

tools/settings_manifest/DRIFT_BOARD.md

16 sources could not be read — the count may be low

Sources that could not be read

purple-team — clone not found at C:\Users\dansl\purple-team

b4him — clone not found at C:\Users\dansl\b4him

omen — clone not found at C:\Users\dansl\Omen

pc-health — clone not found at C:\Users\dansl\pc-health

harness attention issues — [Errno 2] No such file or directory: 'gh'

Sobevista/harness PRs — [Errno 2] No such file or directory: 'gh'

Sobevista/agent-mesh PRs — [Errno 2] No such file or directory: 'gh'

Sobevista/arcade-progression PRs — [Errno 2] No such file or directory: 'gh'

Sobevista/b4him PRs — [Errno 2] No such file or directory: 'gh'

Sobevista/CAS_lens PRs — [Errno 2] No such file or directory: 'gh'

Sobevista/LiftLens PRs — [Errno 2] No such file or directory: 'gh'

Sobevista/Pong_Tower-Repo PRs — [Errno 2] No such file or directory: 'gh'

Sobevista/GC_Junior PRs — [Errno 2] No such file or directory: 'gh'

Sobevista/prompt-coach PRs — [Errno 2] No such file or directory: 'gh'

Sobevista/dan-lens PRs — [Errno 2] No such file or directory: 'gh'

Sobevista/Retro-Dev-Lab PRs — [Errno 2] No such file or directory: 'gh'

What is broken

Every instrument that could not see gets its own row. Could not look is not a pass — a component that cannot see reporting green is the oldest defect in this estate. The full board →

two homes agree35 unapplied ruling(s) name only paths that do not exist — they can never be applied and

local stackdown: n8n, job door, ollama

write sidecould not look — could not look: RuntimeError: git log failed; refusing to report a ver

decision inbox26 hours ago — stale

fleet status26 hours ago — stale

What ran while you were away

The jobs that fire on a clock without anyone watching. Silent is not the same as fine. Which ones →

unattended workers0 reported ok · 0 failing · 3 silent · 25 not visible from here

What we did

The last 36 hours of commits, while it is still fresh enough to correct. All of it →

Nothing committed in the last 36 hours.

The maps

Everything above, at full depth — and the surfaces that are not part of a morning.

Plans in flight

Plans still running, blocked, unreadable, or gone stale since verified — with their receipts. Zero means everything is done and still valid.