fleet/fleetd
3
0
Fork 0
Code Issues 73 Pull Requests Actions Packages Projects Releases 1 Wiki Activity

M4: align design status with CB-573
CI / contract (pull_request) Successful in 43s
Details
CI / build (pull_request) Successful in 1m28s
Details

Browse Source
This commit is contained in:
Dai Ha
2026-08-15 05:56:00 +02:00
parent 17468a234a
commit 20e0e68ad7
1 changed files with 6 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/M4-Fleet-Health.md
+6 -4
View File
@@ -1,11 +1,13 @@
# M4 - Fleet health, recovery, routing, and capacity
**Status:** Design accepted on 2026-08-15. No M4 implementation exists yet.
**Status:** Design accepted on 2026-08-15. CB-573 part 1 has shipped the classification model and
the `bridge_list` capacity view; the remaining M4 units are not yet shipped.
**Scope:** Fleet evidence, safe mechanical repair, lead routing, capacity reporting, and optional
human notification.
**Grounded in:** `inject/StatusPoller`, `inject/StatusRefiner`, `inject/CompletionResolver`,
`inject/Injector`, `session/SessionManager`, `msg/MessageService`, `msg/ReplyInbox`,
`msg/ReplyPushLoop`, `msg/LeadHeartbeatLoop`, `mcp/PrimaryRegistry`, and `herdr/AgentControl`.
**Grounded in:** `health/FleetHealth`, `health/PaneBudget`, `inject/StatusPoller`,
`inject/StatusRefiner`, `inject/CompletionResolver`, `inject/Injector`, `session/SessionManager`,
`msg/MessageService`, `msg/ReplyInbox`, `msg/ReplyPushLoop`, `msg/LeadHeartbeatLoop`,
`mcp/PrimaryRegistry`, and `herdr/AgentControl`.
## 1. Problem and decision boundary