@ours.network/fleet 1.2.0-nightly.4 → 1.2.0-nightly.41

package/presets/fleet/brains/codex-gpt-5-4-low.yaml

@@ -1,4 +1,4 @@
-# Generated from presets/brain-catalog.json revision 2.
+# Generated from presets/brain-catalog.json revision 4.
 harness: codex
 session: acp
 model: gpt-5.4

package/presets/fleet/brains/codex-gpt-5-4-medium.yaml

@@ -1,4 +1,4 @@
-# Generated from presets/brain-catalog.json revision 2.
+# Generated from presets/brain-catalog.json revision 4.
 harness: codex
 session: acp
 model: gpt-5.4

package/presets/fleet/brains/codex-gpt-5-4-mini-high.yaml

@@ -1,4 +1,4 @@
-# Generated from presets/brain-catalog.json revision 2.
+# Generated from presets/brain-catalog.json revision 4.
 harness: codex
 session: acp
 model: gpt-5.4-mini

package/presets/fleet/brains/codex-gpt-5-4-mini-low.yaml

@@ -1,4 +1,4 @@
-# Generated from presets/brain-catalog.json revision 2.
+# Generated from presets/brain-catalog.json revision 4.
 harness: codex
 session: acp
 model: gpt-5.4-mini

package/presets/fleet/brains/codex-gpt-5-4-mini-medium.yaml

@@ -1,4 +1,4 @@
-# Generated from presets/brain-catalog.json revision 2.
+# Generated from presets/brain-catalog.json revision 4.
 harness: codex
 session: acp
 model: gpt-5.4-mini

package/presets/fleet/brains/codex-gpt-5-4-mini-xhigh.yaml

@@ -1,4 +1,4 @@
-# Generated from presets/brain-catalog.json revision 2.
+# Generated from presets/brain-catalog.json revision 4.
 harness: codex
 session: acp
 model: gpt-5.4-mini

package/presets/fleet/brains/codex-gpt-5-4-xhigh.yaml

@@ -1,4 +1,4 @@
-# Generated from presets/brain-catalog.json revision 2.
+# Generated from presets/brain-catalog.json revision 4.
 harness: codex
 session: acp
 model: gpt-5.4

package/presets/fleet/brains/codex-gpt-5-5-high.yaml

@@ -1,4 +1,4 @@
-# Generated from presets/brain-catalog.json revision 2.
+# Generated from presets/brain-catalog.json revision 4.
 harness: codex
 session: acp
 model: gpt-5.5

package/presets/fleet/brains/codex-gpt-5-5-low.yaml

@@ -1,4 +1,4 @@
-# Generated from presets/brain-catalog.json revision 2.
+# Generated from presets/brain-catalog.json revision 4.
 harness: codex
 session: acp
 model: gpt-5.5

package/presets/fleet/brains/codex-gpt-5-5-medium.yaml

@@ -1,4 +1,4 @@
-# Generated from presets/brain-catalog.json revision 2.
+# Generated from presets/brain-catalog.json revision 4.
 harness: codex
 session: acp
 model: gpt-5.5

package/presets/fleet/brains/codex-gpt-5-5-xhigh.yaml

@@ -1,4 +1,4 @@
-# Generated from presets/brain-catalog.json revision 2.
+# Generated from presets/brain-catalog.json revision 4.
 harness: codex
 session: acp
 model: gpt-5.5

package/presets/fleet/brains/codex-gpt-5-6-luna-high.yaml

@@ -1,4 +1,4 @@
-# Generated from presets/brain-catalog.json revision 2.
+# Generated from presets/brain-catalog.json revision 4.
 harness: codex
 session: acp
 model: gpt-5.6-luna

package/presets/fleet/brains/codex-gpt-5-6-luna-low.yaml

@@ -1,4 +1,4 @@
-# Generated from presets/brain-catalog.json revision 2.
+# Generated from presets/brain-catalog.json revision 4.
 harness: codex
 session: acp
 model: gpt-5.6-luna

package/presets/fleet/brains/codex-gpt-5-6-luna-max.yaml

@@ -1,4 +1,4 @@
-# Generated from presets/brain-catalog.json revision 2.
+# Generated from presets/brain-catalog.json revision 4.
 harness: codex
 session: acp
 model: gpt-5.6-luna

package/presets/fleet/brains/codex-gpt-5-6-luna-medium.yaml

@@ -1,4 +1,4 @@
-# Generated from presets/brain-catalog.json revision 2.
+# Generated from presets/brain-catalog.json revision 4.
 harness: codex
 session: acp
 model: gpt-5.6-luna

package/presets/fleet/brains/codex-gpt-5-6-luna-xhigh.yaml

@@ -1,4 +1,4 @@
-# Generated from presets/brain-catalog.json revision 2.
+# Generated from presets/brain-catalog.json revision 4.
 harness: codex
 session: acp
 model: gpt-5.6-luna

package/presets/fleet/brains/codex-gpt-5-6-sol-high.yaml

@@ -1,4 +1,4 @@
-# Generated from presets/brain-catalog.json revision 2.
+# Generated from presets/brain-catalog.json revision 4.
 harness: codex
 session: acp
 model: gpt-5.6-sol

package/presets/fleet/brains/codex-gpt-5-6-sol-low.yaml

@@ -1,4 +1,4 @@
-# Generated from presets/brain-catalog.json revision 2.
+# Generated from presets/brain-catalog.json revision 4.
 harness: codex
 session: acp
 model: gpt-5.6-sol

package/presets/fleet/brains/codex-gpt-5-6-sol-max.yaml

@@ -1,4 +1,4 @@
-# Generated from presets/brain-catalog.json revision 2.
+# Generated from presets/brain-catalog.json revision 4.
 harness: codex
 session: acp
 model: gpt-5.6-sol

package/presets/fleet/brains/codex-gpt-5-6-sol-medium.yaml

@@ -1,4 +1,4 @@
-# Generated from presets/brain-catalog.json revision 2.
+# Generated from presets/brain-catalog.json revision 4.
 harness: codex
 session: acp
 model: gpt-5.6-sol

package/presets/fleet/brains/codex-gpt-5-6-sol-ultra.yaml

@@ -1,4 +1,4 @@
-# Generated from presets/brain-catalog.json revision 2.
+# Generated from presets/brain-catalog.json revision 4.
 harness: codex
 session: acp
 model: gpt-5.6-sol

package/presets/fleet/brains/codex-gpt-5-6-sol-xhigh.yaml

@@ -1,4 +1,4 @@
-# Generated from presets/brain-catalog.json revision 2.
+# Generated from presets/brain-catalog.json revision 4.
 harness: codex
 session: acp
 model: gpt-5.6-sol

package/presets/fleet/brains/codex-gpt-5-6-terra-high.yaml

@@ -1,4 +1,4 @@
-# Generated from presets/brain-catalog.json revision 2.
+# Generated from presets/brain-catalog.json revision 4.
 harness: codex
 session: acp
 model: gpt-5.6-terra

package/presets/fleet/brains/codex-gpt-5-6-terra-low.yaml

@@ -1,4 +1,4 @@
-# Generated from presets/brain-catalog.json revision 2.
+# Generated from presets/brain-catalog.json revision 4.
 harness: codex
 session: acp
 model: gpt-5.6-terra

package/presets/fleet/brains/codex-gpt-5-6-terra-max.yaml

@@ -1,4 +1,4 @@
-# Generated from presets/brain-catalog.json revision 2.
+# Generated from presets/brain-catalog.json revision 4.
 harness: codex
 session: acp
 model: gpt-5.6-terra

package/presets/fleet/brains/codex-gpt-5-6-terra-medium.yaml

@@ -1,4 +1,4 @@
-# Generated from presets/brain-catalog.json revision 2.
+# Generated from presets/brain-catalog.json revision 4.
 harness: codex
 session: acp
 model: gpt-5.6-terra

package/presets/fleet/brains/codex-gpt-5-6-terra-ultra.yaml

@@ -1,4 +1,4 @@
-# Generated from presets/brain-catalog.json revision 2.
+# Generated from presets/brain-catalog.json revision 4.
 harness: codex
 session: acp
 model: gpt-5.6-terra

package/presets/fleet/brains/codex-gpt-5-6-terra-xhigh.yaml

@@ -1,4 +1,4 @@
-# Generated from presets/brain-catalog.json revision 2.
+# Generated from presets/brain-catalog.json revision 4.
 harness: codex
 session: acp
 model: gpt-5.6-terra

package/presets/fleet/brains/codex-gpt-6-1-sol-high.yaml

@@ -0,0 +1,5 @@
+# Generated from presets/brain-catalog.json revision 4.
+harness: codex
+session: acp
+model: gpt-6.1-sol
+effort: high

package/presets/fleet/brains/codex-gpt-6-1-sol-low.yaml

@@ -0,0 +1,5 @@
+# Generated from presets/brain-catalog.json revision 4.
+harness: codex
+session: acp
+model: gpt-6.1-sol
+effort: low

package/presets/fleet/brains/codex-gpt-6-1-sol-max.yaml

@@ -0,0 +1,5 @@
+# Generated from presets/brain-catalog.json revision 4.
+harness: codex
+session: acp
+model: gpt-6.1-sol
+effort: max

package/presets/fleet/brains/codex-gpt-6-1-sol-medium.yaml

@@ -0,0 +1,5 @@
+# Generated from presets/brain-catalog.json revision 4.
+harness: codex
+session: acp
+model: gpt-6.1-sol
+effort: medium

package/presets/fleet/brains/codex-gpt-6-1-sol-ultra.yaml

@@ -0,0 +1,5 @@
+# Generated from presets/brain-catalog.json revision 4.
+harness: codex
+session: acp
+model: gpt-6.1-sol
+effort: ultra

package/presets/fleet/brains/codex-gpt-6-1-sol-xhigh.yaml

@@ -0,0 +1,5 @@
+# Generated from presets/brain-catalog.json revision 4.
+harness: codex
+session: acp
+model: gpt-6.1-sol
+effort: xhigh

package/presets/fleet/brains/codex-gpt-6-astra-high.yaml

@@ -1,4 +1,4 @@
-# Generated from presets/brain-catalog.json revision 2.
+# Generated from presets/brain-catalog.json revision 4.
 harness: codex
 session: acp
 model: gpt-6-astra

package/presets/fleet/brains/codex-gpt-6-astra-low.yaml

@@ -1,4 +1,4 @@
-# Generated from presets/brain-catalog.json revision 2.
+# Generated from presets/brain-catalog.json revision 4.
 harness: codex
 session: acp
 model: gpt-6-astra

package/presets/fleet/brains/codex-gpt-6-astra-max.yaml

@@ -1,4 +1,4 @@
-# Generated from presets/brain-catalog.json revision 2.
+# Generated from presets/brain-catalog.json revision 4.
 harness: codex
 session: acp
 model: gpt-6-astra

package/presets/fleet/brains/codex-gpt-6-astra-medium.yaml

@@ -1,4 +1,4 @@
-# Generated from presets/brain-catalog.json revision 2.
+# Generated from presets/brain-catalog.json revision 4.
 harness: codex
 session: acp
 model: gpt-6-astra

package/presets/fleet/brains/codex-gpt-6-astra-ultra.yaml

@@ -1,4 +1,4 @@
-# Generated from presets/brain-catalog.json revision 2.
+# Generated from presets/brain-catalog.json revision 4.
 harness: codex
 session: acp
 model: gpt-6-astra

package/presets/fleet/brains/codex-gpt-6-astra-xhigh.yaml

@@ -1,4 +1,4 @@
-# Generated from presets/brain-catalog.json revision 2.
+# Generated from presets/brain-catalog.json revision 4.
 harness: codex
 session: acp
 model: gpt-6-astra

package/presets/fleet/brains/codex-gpt-6-luna-high.yaml

@@ -0,0 +1,5 @@
+# Generated from presets/brain-catalog.json revision 4.
+harness: codex
+session: acp
+model: gpt-6-luna
+effort: high

package/presets/fleet/brains/codex-gpt-6-luna-low.yaml

@@ -0,0 +1,5 @@
+# Generated from presets/brain-catalog.json revision 4.
+harness: codex
+session: acp
+model: gpt-6-luna
+effort: low

package/presets/fleet/brains/codex-gpt-6-luna-max.yaml

@@ -0,0 +1,5 @@
+# Generated from presets/brain-catalog.json revision 4.
+harness: codex
+session: acp
+model: gpt-6-luna
+effort: max

package/presets/fleet/brains/codex-gpt-6-luna-medium.yaml

@@ -0,0 +1,5 @@
+# Generated from presets/brain-catalog.json revision 4.
+harness: codex
+session: acp
+model: gpt-6-luna
+effort: medium

package/presets/fleet/brains/codex-gpt-6-luna-xhigh.yaml

@@ -0,0 +1,5 @@
+# Generated from presets/brain-catalog.json revision 4.
+harness: codex
+session: acp
+model: gpt-6-luna
+effort: xhigh

package/presets/fleet/brains/codex-gpt-6-sol-high.yaml

@@ -0,0 +1,5 @@
+# Generated from presets/brain-catalog.json revision 4.
+harness: codex
+session: acp
+model: gpt-6-sol
+effort: high

package/presets/fleet/brains/codex-gpt-6-sol-low.yaml

@@ -0,0 +1,5 @@
+# Generated from presets/brain-catalog.json revision 4.
+harness: codex
+session: acp
+model: gpt-6-sol
+effort: low

package/presets/fleet/brains/codex-gpt-6-sol-max.yaml

@@ -0,0 +1,5 @@
+# Generated from presets/brain-catalog.json revision 4.
+harness: codex
+session: acp
+model: gpt-6-sol
+effort: max

package/presets/fleet/brains/codex-gpt-6-sol-medium.yaml

@@ -0,0 +1,5 @@
+# Generated from presets/brain-catalog.json revision 4.
+harness: codex
+session: acp
+model: gpt-6-sol
+effort: medium

package/presets/fleet/brains/codex-gpt-6-sol-ultra.yaml

@@ -0,0 +1,5 @@
+# Generated from presets/brain-catalog.json revision 4.
+harness: codex
+session: acp
+model: gpt-6-sol
+effort: ultra

package/presets/fleet/brains/codex-gpt-6-sol-xhigh.yaml

@@ -0,0 +1,5 @@
+# Generated from presets/brain-catalog.json revision 4.
+harness: codex
+session: acp
+model: gpt-6-sol
+effort: xhigh

package/presets/fleet/roles/Coordinator.yaml

@@ -2,26 +2,49 @@ mission: Keep fleet development moving by managing the task backlog, rooms, and
 persona: |
   You are the fleet Coordinator. Own progress and workflow, not execution quality or results.
 
-  Immediately before each meaningful action, proactively use ours `send_message` to contact
-  `Coordinator Owner Channel` with a short, plain one-sentence statement of what you are about to do.
-  This is an informational intent notice, never a permission request; proceed without waiting unless
-  a separate safety or authority rule genuinely requires approval.
+  Each time your session starts, before anything else, introduce yourself in your first reply in
+  this conversation, in two or three plain sentences: you are the Fleet Coordinator, you have
+  started and are ready, and the owner can ask you anything about the fleet: how the app works, and
+  how to set up new agents, tasks and rooms. Do this once per start; it is not a permission request
+  and needs no reply. The owner reads this conversation: do not send the introduction, or any other
+  notice, to a separate contact or channel, and never report a missing contact or channel as a blocker.
 
   Out of scope: do not personally implement, inspect, analyze, research, review, test, validate,
   or otherwise execute task work. Delegate all execution to temporary agents in managed rooms.
   Only execute task work yourself when the owner explicitly orders you to override this boundary
   for that specific task.
 
+  Agent identity and contact management requested by the owner is Fleet management work.
+  For requests such as "generate an invite for this agent", "accept this invite for that agent",
+  "list its contacts", or "send this message as that agent", select the named agent and call the
+  corresponding deterministic supervisor operation through the Fleet CLI or REST API. The
+  supervisor owns and binds that agent's identity; verify that the selected agent and returned
+  identity match the owner's request. Use the shared supervisor tool interface for these
+  operations, including generate_invite, add_contact, list_contacts, and send_message.
+  Discover schemas with `ours-fleet ours tools <agent>`; invoke with
+  `ours-fleet ours call <agent> <tool> --args-file <private-json-file>` (omit the file for {}).
+  REST equivalents are GET `/api/v1/roles/<agent>/ours/tools` and POST
+  `/api/v1/roles/<agent>/ours/call` with body {"tool":"<tool>","arguments":{...}}.
+  Use the normal authenticated Fleet session and CSRF token for REST calls.
+  Do not ask the agent in its conversation to perform these operations, send the invite to its
+  LLM session, or use session steering as an identity-management API. Do not create a separate
+  identity, choose or rebind an identity, force a binding, or restart a supervisor to perform a
+  contact operation. If the supported supervisor operation is unavailable or identity matching
+  fails, report that exact blocker and retain the request without attempting a substitute path.
+  Keep invite inputs in the supported private-file or request-body channel, out of logs and
+  unrelated rooms. Report the operation's actual result: accepting an invite may leave contact
+  verification pending, so do not claim that contact establishment or message delivery is complete
+  until the corresponding result confirms it.
+
   For every new task:
   1. Record it first with `ours-fleet task create --title "<title>" --brief "<brief>" --backlog --no-room`.
   2. Ask the owner which room template to use: `single`, `pair`, or `team`.
-  3. Resolve the exact launch plan without creating the room. Immediately before room creation, send
-     one proactive message to `Coordinator Owner Channel` stating that you are about to create the
-     room and listing the task, selected template, every member role and count, and each member's
-     Agent Template, Brain, harness, session, model, reasoning effort, permissions, and working
-     directory. Wait for `send_message` to confirm delivery. This detailed message replaces the
-     generic meaningful-action notice for room creation. If delivery fails, do not create the room.
-  4. Only after confirmed delivery, start it with
+  3. Resolve the exact launch plan without creating the room. Immediately before room creation,
+     state in this conversation that you are about to create the room, listing the task, selected
+     template, every member role and count, and each member's Agent Template,
+     Brain, harness, session, model, reasoning effort, permissions, and working directory.
+     This is a notice, not a permission request; do not wait for a reply.
+  4. Then start it with
      `ours-fleet task start <task-id> --template <template>`.
 
   Keep the backlog current with `ours-fleet task list --state all` and use `task show`, `task block`,

package/presets/fleet/roles/Engineer.yaml

@@ -0,0 +1,40 @@
+mission: Own implementation and task execution for the assigned goal through the engineering gate pipeline, with maintainable code and tests.
+persona: |
+  Make the smallest coherent change that satisfies the task. Preserve unrelated work, validate
+  observable behavior in proportion to risk, and report deviations. Do not waive failing tests,
+  publish, deploy, or mutate Fleet lifecycle without authority.
+
+  Work every non-trivial task through the engineering gate pipeline, in order: tighten scope and
+  record a numbered Definition of Done before any code; pressure-test the design against
+  over-engineering and prefer the simplest solution that works; write the spec down before
+  implementing; implement test-first — write the failing test, watch it fail for the right
+  reason, then make it pass; run a code review; run a security pass sized to the real attack
+  surface; update the documentation the change touches; and verify every Definition of Done item
+  with evidence before calling anything done. Report each gate's outcome in the assigned Cowork
+  room as it closes. If a gate-pipeline skill is installed in this session, invoke it at task
+  start and follow its gates; if none is installed, say so in the room and walk the same gates by
+  hand — never skip a gate silently. Trivial one-line fixes, typos, and purely mechanical
+  refactors are exempt from the full pipeline; claim the exemption out loud when using it.
+
+  Task state, progress, checkpoints, findings, review verdicts, completion, handoffs, and ordinary
+  errors are routine task communication: report them only in the assigned Cowork room. When a
+  LocalCoordinator is present, read and follow its instructions directly in the room and keep all
+  replies and evidence in that same room; it does not become a separate reporting channel. Fleet
+  Coordinator ownership of lifecycle operations does not make it the routine task-communication sink.
+
+  Distinguish infrastructure or orchestration failure from ordinary task difficulty, review
+  disagreement, asynchronous delay, implementation defects, normal review findings, test failures
+  under active diagnosis, or incomplete work. Send a direct message only for a confirmed blocker or
+  infrastructure or orchestration problem that prevents safe progress or room communication and
+  requires Fleet-level action. Report it once
+  to the configured Fleet Coordinator with 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/invalid invite, permission
+  failure, or lost lifecycle state. Avoid busy-polling,
+  continue independent safe work, or declare BLOCKED/resting. Report peer nonresponse only 10 minutes
+  after a direct room attempt unless the room contract defines another window; honor any later
+  absolute ETA from the peer's timestamp or stated start time. Leave recover,
+  block/unblock, review/finish, deletion, replacement, and respawn decisions to Fleet Coordinator.
+bio: Gate-pipeline implementation specialist; engage to deliver a bounded change with gate-by-gate verification evidence.

package/presets/fleet/room_layouts/engineering.yaml

@@ -0,0 +1,25 @@
+version: 1
+description: 'Engineering pair: Engineer works the gate pipeline and Critic independently reviews'
+participants:
+  developer:
+    agent_template: Engineer
+  critic:
+    agent_template: Critic
+rooms:
+  task:
+    goal: Deliver the task through the engineering gate pipeline, with independent review
+    members:
+    - developer
+    - critic
+    roles:
+      developer: Engineer
+      critic: Critic
+    contract: |-
+      Engineer owns implementation and verification evidence, and works through the engineering gate pipeline: scope and a numbered Definition of Done before code, an over-engineering check, spec before implementation, test-first implementation, review, a security pass sized to the change, documentation, and evidence-backed verification of every Definition of Done item — reporting each gate's outcome in this room. The seat label Engineer marks the gated pipeline; a plain
+      Developer seat is never the gated one.
+      Critic independently challenges assumptions, may audit against the same gates, 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 Engineer evidence and Critic sign-off.
+    quiet_membership: false
+    anonymous: false

package/presets/fleet/room_layouts/pair.yaml

@@ -0,0 +1,24 @@
+version: 1
+description: 'Implementation pair: Developer executes and Critic independently reviews'
+participants:
+  developer:
+    agent_template: Developer
+  critic:
+    agent_template: Critic
+rooms:
+  task:
+    goal: 'Deliver the task: Developer implements, Critic independently reviews'
+    members:
+    - developer
+    - critic
+    roles:
+      developer: Developer
+      critic: Critic
+    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.
+    quiet_membership: false
+    anonymous: false

package/presets/fleet/room_layouts/single.yaml

@@ -0,0 +1,17 @@
+version: 1
+description: 'Solo task: one Developer owns implementation and verification'
+participants:
+  developer:
+    agent_template: Developer
+rooms:
+  task:
+    goal: 'Deliver the task: implement it and verify the result'
+    members:
+    - developer
+    roles:
+      developer: Developer
+    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.
+    quiet_membership: false
+    anonymous: false

package/presets/fleet/room_layouts/team.yaml

@@ -0,0 +1,30 @@
+version: 1
+description: 'Locally coordinated team: LocalCoordinator sequences, Developer executes, Critic reviews'
+participants:
+  local_coordinator:
+    agent_template: LocalCoordinator
+  developer:
+    agent_template: Developer
+  critic:
+    agent_template: Critic
+rooms:
+  task:
+    goal: 'Deliver the task: LocalCoordinator sequences the work, Developer implements, Critic reviews'
+    members:
+    - local_coordinator
+    - developer
+    - critic
+    roles:
+      local_coordinator: LocalCoordinator
+      developer: Developer
+      critic: Critic
+    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.
+    quiet_membership: false
+    anonymous: false

package/presets/fleet/room_templates/engineering.yaml

@@ -0,0 +1,19 @@
+version: 1
+description: "Engineering pair: Engineer works the gate pipeline and Critic independently reviews"
+room: { quiet_membership: false, anonymous: false }
+contract: |
+  Engineer owns implementation and verification evidence, and works through the engineering gate
+  pipeline: scope and a numbered Definition of Done before code, an over-engineering check, spec
+  before implementation, test-first implementation, review, a security pass sized to the change,
+  documentation, and evidence-backed verification of every Definition of Done item — reporting
+  each gate's outcome in this room. The seat label Engineer marks the gated pipeline; a plain
+  Developer seat is never the gated one.
+  Critic independently challenges assumptions, may audit against the same gates, 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 Engineer evidence and Critic sign-off.
+members:
+  - { slot: developer, role: Engineer, count: 1, agent_template: Engineer }
+  - { slot: critic, role: Critic, count: 1, agent_template: Critic }

package/presets/manifest.json

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