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

CB-566: add fleet charter config #36

Closed
agent wants to merge 1 commits from worker/u1-469dce-1 into main
pull from: worker/u1-469dce-1
merge into: fleet:main
Conversation 0 Commits 1 Files Changed 6
+187 -36
agent commented 2026-08-15 04:50:02 +02:00
Member
Copy Link
Copy Source

Adds hot fleet.charters config, strict charter validation at startup and reload, example documentation, and reload tests. Tests: mvn clean install (649 tests, all passing).

Adds hot fleet.charters config, strict charter validation at startup and reload, example documentation, and reload tests. Tests: mvn clean install (649 tests, all passing).
agent added 2 commits 2026-08-15 04:50:02 +02:00
CB-560/562/563: the shipped block tells the truth again 890190263e 
The canonical CLAUDE.md block is the instruction surface this daemon ships to
every agent that mounts it, so a code change that silently invalidates it is an
incomplete change. CB-548 added a third principal kind and the block was never
revisited. Four statements in it were simply false:

  * whoami was documented as returning only primary or worker;
  * "spawn/stop/send/drain are lead-only" — Authz permits SEND to an architect;
  * delivery was documented as idle/blocked — injectable() is IDLE|BLOCKED|DONE,
    and a spawned member must also have mounted the bridge MCP, which is the
    exact condition that made every architect undeliverable for a day;
  * the tool table said bridge_list returns `workers` — the JSON key is
    `members`.

Also corrected: the fallback ladder claimed each one-way signal identifies a
"worker", but an architect gets the same charter, the same mount and the same
env, so those signals identify a spawned member and only bridge_whoami
separates the two. The safe default stays "act as a worker" — it is the most
restricted member role.

The turn contract now covers both member kinds, and says why the completion
fallback is not a substitute for bridge_reply: it returns at most the last 4000
characters, so a long report reaches the lead with its end cut off. That is not
hypothetical — it happened twice today.

Found by a reviewer asked whether the block still matches the code. Verified
against injectable(), Authz, BridgeMcp.listFleet and LeadLauncher before
applying. The wiki template is updated in the same shape and re-checked
byte-identical.
CB-566: add fleet charter config
CI / build (pull_request) Successful in 1m13s
Details
CI / contract (pull_request) Successful in 1m15s
Details
d9e45f8c2a
agent closed this pull request 2026-08-15 04:50:35 +02:00
Some checks are pending
CI / build (pull_request) Successful in 1m13s
Details
CI / contract (pull_request) Successful in 1m15s
Details

Pull request closed

Please reopen this pull request to perform a merge.
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
Clear labels
blocked
Cannot start until something else lands. The body says what.
 needs-live-proof
Merged and green, but never shown working on the running daemon. Not the same as done.
 ready-to-delegate
Scope, files and acceptance criteria are written. A worker can be briefed from the body alone.
 silent-default
A feature that compiles, passes tests, and ships turned off. Nine recurrences and counting.
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
agent kevin ltms
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: fleet/fleetd#36
Delete Branch "worker/u1-469dce-1"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?