feat: cross-conversation context for a seat, and collapse private asides

companies/retail_co/README.md

@@ -80,7 +80,9 @@ console's Inference card or over the API:
 ```bash
 curl -X PUT localhost:8099/api/v1/companies/retail-co/inference \
   -H 'content-type: application/json' \
-  -d "{\"provider\":\"openrouter\",\"base_url\":\"https://openrouter.ai/api/v1\",\"key\":\"$OPENROUTER_API_KEY\"}"
+  -d "{\"provider\":\"openrouter\",\"base_url\":\"https://openrouter.ai/api/v1\",\"key\":\"$OPENROUTER_API_KEY\",
+       \"models\":{\"chat-v1\":\"deepseek/deepseek-v4-flash\",\"reasoning-v1\":\"deepseek/deepseek-v4-flash\",
+       \"agentic-v1\":\"deepseek/deepseek-v4-flash\",\"vision-v1\":\"deepseek/deepseek-v4-flash\"}}"
 ```
 
 **Send the `models` table with the key.** `PUT …/inference` stores the whole

companies/retail_co/agents/amendments.toml

@@ -114,22 +114,27 @@ You share the **order_ops** desk with `cancellations`. A case arriving here is d
 floor and let the room settle which remedy applies. You hold different tools
 and neither of you can reach the other's, so it has to be argued for.
 
-- **@returns** — delivered orders. Seats: `exchanges`, `refunds`
+- **@#returns** — delivered orders. Seats: `exchanges`, `refunds`
 
 ## Handing work on
 
 Two ways out of this turn, and they do different things.
 
 **To a desk — when the choice between its remedies is the question.** Write that
-desk's mention in your reply, on its own line: `@returns …`. The mention IS the
-hand-off. It puts the case on that desk's channel, its seats deliberate it
-between them, and what the room settles on comes back to you as their answer.
-Reach for this whenever you do not know which remedy applies — deciding that is
-what the room is for.
-
-Write it as `@returns`, exactly. A desk named in passing — "returns can do this",
-or the name in bold — resolves to nothing and reaches nobody: the hand-off is
-dropped silently and the work never happens.
+desk's mention in your reply, on its own line: `@#returns …`. The mention IS the
+hand-off, and it is smaller than it sounds: ONE teammate on that desk takes ONE
+turn and answers. That desk does not deliberate your question between its seats
+and no room settles it — what comes back is one colleague's reading, on the
+record, for you to weigh.
+
+Ask when that desk holds a fact yours does not, and ask EARLY. The answer is
+information and not a vote: it supports nothing here until you or a teammate
+spends a line acting on it.
+
+Write it as `@#returns`, exactly. The `@#` form addresses a desk and cannot be
+shadowed by a teammate who happens to share the name. A desk named in passing —
+"returns can do this", or the name in bold — resolves to nothing and reaches
+nobody: the hand-off is dropped silently and the work never happens.
 
 **To one named person — when you already know who owns it.** Call
 `delegate_to_teammate` with their roster id. One turn from that person, no room.

companies/retail_co/agents/cancellations.toml

@@ -100,22 +100,27 @@ You share the **order_ops** desk with `amendments`. A case arriving here is deli
 floor and let the room settle which remedy applies. You hold different tools
 and neither of you can reach the other's, so it has to be argued for.
 
-- **@returns** — delivered orders. Seats: `exchanges`, `refunds`
+- **@#returns** — delivered orders. Seats: `exchanges`, `refunds`
 
 ## Handing work on
 
 Two ways out of this turn, and they do different things.
 
 **To a desk — when the choice between its remedies is the question.** Write that
-desk's mention in your reply, on its own line: `@returns …`. The mention IS the
-hand-off. It puts the case on that desk's channel, its seats deliberate it
-between them, and what the room settles on comes back to you as their answer.
-Reach for this whenever you do not know which remedy applies — deciding that is
-what the room is for.
-
-Write it as `@returns`, exactly. A desk named in passing — "returns can do this",
-or the name in bold — resolves to nothing and reaches nobody: the hand-off is
-dropped silently and the work never happens.
+desk's mention in your reply, on its own line: `@#returns …`. The mention IS the
+hand-off, and it is smaller than it sounds: ONE teammate on that desk takes ONE
+turn and answers. That desk does not deliberate your question between its seats
+and no room settles it — what comes back is one colleague's reading, on the
+record, for you to weigh.
+
+Ask when that desk holds a fact yours does not, and ask EARLY. The answer is
+information and not a vote: it supports nothing here until you or a teammate
+spends a line acting on it.
+
+Write it as `@#returns`, exactly. The `@#` form addresses a desk and cannot be
+shadowed by a teammate who happens to share the name. A desk named in passing —
+"returns can do this", or the name in bold — resolves to nothing and reaches
+nobody: the hand-off is dropped silently and the work never happens.
 
 **To one named person — when you already know who owns it.** Call
 `delegate_to_teammate` with their roster id. One turn from that person, no room.

companies/retail_co/agents/exchanges.toml

@@ -102,22 +102,27 @@ You share the **returns** desk with `refunds`. A case arriving here is deliberat
 floor and let the room settle which remedy applies. You hold different tools
 and neither of you can reach the other's, so it has to be argued for.
 
-- **@order_ops** — pending orders, not yet shipped. Seats: `cancellations`, `amendments`
+- **@#order_ops** — pending orders, not yet shipped. Seats: `cancellations`, `amendments`
 
 ## Handing work on
 
 Two ways out of this turn, and they do different things.
 
 **To a desk — when the choice between its remedies is the question.** Write that
-desk's mention in your reply, on its own line: `@returns …`. The mention IS the
-hand-off. It puts the case on that desk's channel, its seats deliberate it
-between them, and what the room settles on comes back to you as their answer.
-Reach for this whenever you do not know which remedy applies — deciding that is
-what the room is for.
-
-Write it as `@returns`, exactly. A desk named in passing — "returns can do this",
-or the name in bold — resolves to nothing and reaches nobody: the hand-off is
-dropped silently and the work never happens.
+desk's mention in your reply, on its own line: `@#order_ops …`. The mention IS the
+hand-off, and it is smaller than it sounds: ONE teammate on that desk takes ONE
+turn and answers. That desk does not deliberate your question between its seats
+and no room settles it — what comes back is one colleague's reading, on the
+record, for you to weigh.
+
+Ask when that desk holds a fact yours does not, and ask EARLY. The answer is
+information and not a vote: it supports nothing here until you or a teammate
+spends a line acting on it.
+
+Write it as `@#order_ops`, exactly. The `@#` form addresses a desk and cannot be
+shadowed by a teammate who happens to share the name. A desk named in passing —
+"order_ops can do this", or the name in bold — resolves to nothing and reaches
+nobody: the hand-off is dropped silently and the work never happens.
 
 **To one named person — when you already know who owns it.** Call
 `delegate_to_teammate` with their roster id. One turn from that person, no room.

companies/retail_co/agents/refunds.toml

@@ -104,22 +104,27 @@ You share the **returns** desk with `exchanges`. A case arriving here is deliber
 floor and let the room settle which remedy applies. You hold different tools
 and neither of you can reach the other's, so it has to be argued for.
 
-- **@order_ops** — pending orders, not yet shipped. Seats: `cancellations`, `amendments`
+- **@#order_ops** — pending orders, not yet shipped. Seats: `cancellations`, `amendments`
 
 ## Handing work on
 
 Two ways out of this turn, and they do different things.
 
 **To a desk — when the choice between its remedies is the question.** Write that
-desk's mention in your reply, on its own line: `@returns …`. The mention IS the
-hand-off. It puts the case on that desk's channel, its seats deliberate it
-between them, and what the room settles on comes back to you as their answer.
-Reach for this whenever you do not know which remedy applies — deciding that is
-what the room is for.
-
-Write it as `@returns`, exactly. A desk named in passing — "returns can do this",
-or the name in bold — resolves to nothing and reaches nobody: the hand-off is
-dropped silently and the work never happens.
+desk's mention in your reply, on its own line: `@#order_ops …`. The mention IS the
+hand-off, and it is smaller than it sounds: ONE teammate on that desk takes ONE
+turn and answers. That desk does not deliberate your question between its seats
+and no room settles it — what comes back is one colleague's reading, on the
+record, for you to weigh.
+
+Ask when that desk holds a fact yours does not, and ask EARLY. The answer is
+information and not a vote: it supports nothing here until you or a teammate
+spends a line acting on it.
+
+Write it as `@#order_ops`, exactly. The `@#` form addresses a desk and cannot be
+shadowed by a teammate who happens to share the name. A desk named in passing —
+"order_ops can do this", or the name in bold — resolves to nothing and reaches
+nobody: the hand-off is dropped silently and the work never happens.
 
 **To one named person — when you already know who owns it.** Call
 `delegate_to_teammate` with their roster id. One turn from that person, no room.

companies/retail_co/agents/triage.toml

@@ -93,23 +93,28 @@ You are `triage` on the **triage** desk.
 You are the only seat on your desk, so nothing is deliberated here — you
 answer in one turn.
 
-- **@order_ops** — pending orders, not yet shipped. Seats: `cancellations`, `amendments`
-- **@returns** — delivered orders. Seats: `exchanges`, `refunds`
+- **@#order_ops** — pending orders, not yet shipped. Seats: `cancellations`, `amendments`
+- **@#returns** — delivered orders. Seats: `exchanges`, `refunds`
 
 ## Handing work on
 
 Two ways out of this turn, and they do different things.
 
 **To a desk — when the choice between its remedies is the question.** Write that
-desk's mention in your reply, on its own line: `@returns …`. The mention IS the
-hand-off. It puts the case on that desk's channel, its seats deliberate it
-between them, and what the room settles on comes back to you as their answer.
-Reach for this whenever you do not know which remedy applies — deciding that is
-what the room is for.
-
-Write it as `@returns`, exactly. A desk named in passing — "returns can do this",
-or the name in bold — resolves to nothing and reaches nobody: the hand-off is
-dropped silently and the work never happens.
+desk's mention in your reply, on its own line — `@#order_ops …` for an order
+still pending, `@#returns …` for one already delivered. That choice is the whole
+of your job, so make it on the order's status and nothing else.
+
+The mention IS the hand-off, and it is smaller than it sounds: ONE teammate on
+that desk takes ONE turn and answers. That desk does not deliberate your question
+between its seats and no room settles it — what comes back is one colleague's
+reading, on the record, for you to weigh. The answer is information and not a
+vote: it supports nothing until somebody spends a line acting on it.
+
+Write it as `@#order_ops` or `@#returns`, exactly. The `@#` form addresses a desk
+and cannot be shadowed by a teammate who happens to share the name. A desk named
+in passing — "returns can do this", or the name in bold — resolves to nothing and
+reaches nobody: the hand-off is dropped silently and the work never happens.
 
 **To one named person — when you already know who owns it.** Call
 `delegate_to_teammate` with their roster id. One turn from that person, no room.

companies/retail_co/company.toml

@@ -148,6 +148,21 @@ turn_budget = 12
 quorum = 2
 blind_round = true
 
+[group_chat.hive.aside]
+# The private agent-to-agent line: a seat may add ONE `!aside @peer` line under
+# its move. Off unless a desk asks — `AsidePolicy::DEFAULT` permits nothing,
+# deliberately, because the mechanism does not get the benefit of the doubt.
+#
+# Every person and the operator still read every row in full. This is a
+# deliberation device, never a security boundary: an exchange no human could
+# audit is the covert channel the design exists to avoid. A peer outside the
+# aside still sees that it happened, who was in it, and where it settled.
+#
+# Defaults left alone: a pair (`max_members = 1`, excluding the author), two
+# rows (`max_messages = 2` — a question and an answer), and `must_surface`,
+# which makes a pair deposit one desk-visible line before opening another.
+enabled = true
+
 [group_chat.hive.referral]
 enabled = true
 reach = "desks"
@@ -185,6 +200,21 @@ turn_budget = 12
 quorum = 2
 blind_round = true
 
+[group_chat.hive.aside]
+# The private agent-to-agent line: a seat may add ONE `!aside @peer` line under
+# its move. Off unless a desk asks — `AsidePolicy::DEFAULT` permits nothing,
+# deliberately, because the mechanism does not get the benefit of the doubt.
+#
+# Every person and the operator still read every row in full. This is a
+# deliberation device, never a security boundary: an exchange no human could
+# audit is the covert channel the design exists to avoid. A peer outside the
+# aside still sees that it happened, who was in it, and where it settled.
+#
+# Defaults left alone: a pair (`max_members = 1`, excluding the author), two
+# rows (`max_messages = 2` — a question and an answer), and `must_surface`,
+# which makes a pair deposit one desk-visible line before opening another.
+enabled = true
+
 [group_chat.hive.referral]
 enabled = true
 reach = "desks"
@@ -210,6 +240,21 @@ turn_budget = 12
 quorum = 2
 blind_round = true
 
+[group_chat.hive.aside]
+# The private agent-to-agent line: a seat may add ONE `!aside @peer` line under
+# its move. Off unless a desk asks — `AsidePolicy::DEFAULT` permits nothing,
+# deliberately, because the mechanism does not get the benefit of the doubt.
+#
+# Every person and the operator still read every row in full. This is a
+# deliberation device, never a security boundary: an exchange no human could
+# audit is the covert channel the design exists to avoid. A peer outside the
+# aside still sees that it happened, who was in it, and where it settled.
+#
+# Defaults left alone: a pair (`max_members = 1`, excluding the author), two
+# rows (`max_messages = 2` — a question and an answer), and `must_surface`,
+# which makes a pair deposit one desk-visible line before opening another.
+enabled = true
+
 [group_chat.hive.referral]
 enabled = true
 reach = "desks"