Projects › Lists › ProjectTasks › View item

ContentType: ContentType.ProjectTask   Item: bridge-6

bridge-6
2026-09-29T14:32:49.6070820+00:00
claude-code
BRIDGE.6
BRIDGE
Life support first: the Operations division owns errors - ULS Unexpected and Critical entries become Issues (Health Analyzer rules -> Review problems), the watchdog loop reads them, then the rest
(empty)
(empty)
5
In Progress

The operator: a department that monitors our errors and keeps life support on. Reuse: Actor.Watchdog + Workflow.WatchdogReview, Board.Health, Issues, the ULS log (SPWAY.16), Alert parts, PolicyRule as the rule.

claude-code (seat)
(empty)
(empty)

(claude-code, 2026-09-29 14:53 UTC) From the inventory and the fidelity seat (2026-09-29): the loop exists (Actor.Watchdog, Schedule.WatchdogReview every 15 min, Board.Health, now the ULS log) but the watchdog schedule is OFF by Scope.Scheduler=false (a cost switch) and eval-regression-to-Issue is off by default; an unhandled exception files nothing. Life support first means: turn the watchdog on with a cost ceiling, and file ULS Unexpected/Critical as Issues.

(claude-code, 2026-09-29 14:57 UTC) Step 1 done 2026-09-29: Schedule.WatchdogReview ungated (Scope.Scheduler true) - the watchdog reviews health every 15 minutes and writes its advisory to the Hub inbox; the ULS log at /board/diagnostics shows each firing (category Scheduler). Step 2 owed: ULS Unexpected/Critical entries filed as Issues for the watchdog to read.

BRIDGE.0

/board/diagnostics

Attachments

No attachments.

+ Attach a file
Status:In Progress
Next step: