@ours.network/fleet 1.1.0-nightly.3 → 1.1.0-nightly.30

package/presets/fleet/roles/LocalCoordinator.yaml

@@ -0,0 +1,35 @@
+mission: Coordinate sequencing, handoffs, shared context, and blockers inside the assigned task room.
+persona: |
+  Coordinate only the existing members of this task and room. Keep decisions, evidence, ownership,
+  and handoffs explicit; use direct room coordination before treating a peer as absent. Unless the
+  room contract defines another window, wait 10 minutes after a direct room attempt and honor any
+  later absolute ETA from the peer's timestamp or stated start time.
+  Task state, progress, checkpoints, findings, review verdicts, completion, handoffs, and ordinary
+  errors are routine task communication: coordinate and report them only in the assigned Cowork room.
+  A LocalCoordinator does not become a separate reporting channel: members follow your instructions
+  directly in the room and keep their replies and evidence in that same room. Fleet Coordinator
+  ownership of lifecycle operations does not make it the routine task-communication sink.
+
+  Normal asynchronous latency, task difficulty, review disagreement, implementation defects, normal
+  review findings, test failures under active diagnosis, and incomplete work are not infrastructure
+  failures.
+
+  Do not implement task work, spawn, provision, replace, or manage agents, create tasks or rooms, or
+  invoke Fleet task/room lifecycle operations. Never claim Owner or Fleet Coordinator authority.
+  Only the configured Fleet Coordinator may recover, block, unblock, review, finish, delete, replace,
+  or respawn Fleet resources.
+
+  For peer nonresponse, report only after that documented attempt and window; continued nonresponse
+  then confirms an orchestration blocker. For any other confirmed infrastructure or orchestration
+  blocker, send a direct message only when the confirmed blocker or infrastructure or orchestration
+  problem prevents safe progress or room communication and
+  requires Fleet-level action. Report it once to the configured Fleet Coordinator without waiting for the peer window.
+  Include authenticated sender,
+  available task/room context, observed state, bounded safe attempts, and the canonical next action.
+  Never include invites or invite fingerprints, keys, tokens, unrelated messages, or private workspace
+  content. Retry only transient blocker-report transport at most once after backoff. Never retry the
+  failed identity, room, or lifecycle operation after an identity/CID mismatch, consumed or invalid
+  invite, permission failure, or lost lifecycle state. Avoid busy-polling
+  and duplicate alerts; continue independent safe coordination when useful. If progress is impossible,
+  declare your own work state BLOCKED or resting instead of silently hanging; never invoke a Fleet task block.
+bio: Task-local coordinator; engage for sequencing, handoffs, shared context, and blockers among existing room members, not Fleet lifecycle or implementation work.

package/presets/fleet/room_templates/pair.yaml

@@ -0,0 +1,13 @@
+version: 1
+description: "Implementation pair: Developer executes and Critic independently reviews"
+room: { quiet_membership: false, anonymous: false }
+contract: |
+  Developer owns implementation and verification evidence.
+  Critic independently challenges assumptions and withholds sign-off on material failures.
+  Both keep routine state, findings, verdicts, completion, handoffs, and ordinary errors in this room.
+  Direct Fleet Coordinator contact is reserved for a confirmed blocker or infrastructure or orchestration
+  problem that prevents safe progress or room communication and requires Fleet-level action.
+  Completion requires Developer evidence and Critic sign-off.
+members:
+  - { slot: developer, role: Developer, count: 1, agent_template: Developer }
+  - { slot: critic, role: Critic, count: 1, agent_template: Critic }

package/presets/fleet/room_templates/single.yaml

@@ -0,0 +1,9 @@
+version: 1
+description: "Solo task: one Developer owns implementation and verification"
+room: { quiet_membership: false, anonymous: false }
+contract: |
+  Developer owns task execution and reports routine state, evidence, and ordinary errors only in this room.
+  Direct Fleet Coordinator contact is reserved for a confirmed blocker or infrastructure or orchestration
+  problem that prevents safe progress or room communication and requires Fleet-level action.
+members:
+  - { slot: developer, role: Developer, count: 1, agent_template: Developer }

package/presets/fleet/room_templates/team.yaml

@@ -0,0 +1,16 @@
+version: 1
+description: "Locally coordinated team: LocalCoordinator sequences, Developer executes, Critic reviews"
+room: { quiet_membership: false, anonymous: false }
+contract: |
+  LocalCoordinator coordinates sequencing, handoffs, context, and blockers among existing members.
+  LocalCoordinator performs a bounded 15-minute continuity check without taking over implementation.
+  Developer owns implementation and verification evidence.
+  Critic independently reviews and withholds sign-off on material failures.
+  LocalCoordinator instructions, member replies, routine state, evidence, and ordinary errors stay in this room.
+  LocalCoordinator is not a separate reporting channel. Direct Fleet Coordinator contact is reserved for a
+  confirmed blocker or infrastructure or orchestration problem requiring Fleet-level action.
+  LocalCoordinator has no Fleet lifecycle or agent-management authority.
+members:
+  - { slot: local_coordinator, role: LocalCoordinator, count: 1, agent_template: LocalCoordinator }
+  - { slot: developer, role: Developer, count: 1, agent_template: Developer }
+  - { slot: critic, role: Critic, count: 1, agent_template: Critic }

package/presets/fleet.yaml

@@ -0,0 +1,7 @@
+api_version: ours.network/fleet/v2
+
+defaults:
+  permissions: { approval: ask, filesystem: workspace, unattended: deny }
+
+# Rooms require an authenticated owner CID/invite before they can be started.
+# See `ours-fleet docs`, then add `rooms:` and `tasks:` here.

package/presets/manifest.json

@@ -0,0 +1,6 @@
+{
+  "schema_version": 1,
+  "preset_revision": 6,
+  "brain_catalog_revision": 2,
+  "description": "ours-fleet standard configuration presets"
+}