1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
//! User actions issued through `cli_outbound` (ARCH §3.4 / §3.5).
//!
//! This root holds the §8.2 **enablement predicates that cross** — whether a
//! verb is offered for the conversation the boundary is answering about, each
//! refusing exactly what the underlying `litany` verb would. The **short,
//! piped, logged** verbs — message/stop/scan and `bl`
//! close/unclaim/create/update — live in [`verbs`], which appends each outcome
//! to `ops.jsonl` (§8.2, §15 Y16); the **detached** `litany prompt` (the new-root
//! launch, §8.1) is the one
//! [`start::execute_prompt`](crate::start::execute_prompt) path (Y17 moved it
//! onto `spawn_detached`, unifying the composer's new-prompt with the start
//! flow's final prompt — one detached, logged launch, no piped-and-drained
//! variant whose `Stream` drop would SIGTERM the loop on yog's exit).
//!
//! Predicate discipline (§8.2): **Stop** needs a Live/InFlight executor to
//! signal ([`stop_enabled`]); **Nudge** is its complement — the states with no
//! driver holding the lease, less the one shape litany reads as nothing-due
//! ([`nudge_enabled`]); **Message** is the resume gesture and works on *any*
//! selected agent (ARCH §2.9 — no resume verb; its gate's text half is a
//! composer's, so the conjunction is the seat's, bl-7cc8); **Scan** is
//! unconditional (offered for any focused workspace — no predicate). All three
//! ride the §8.5 agent answer as `nudgeable`/`stoppable`/`stop_children`
//! (`boundary::answer::agent`), so a seat is **told** rather than asked to
//! re-derive.
//!
//! **What a seat derives for itself is not held here.** A gate a row already
//! carries the input for is the seat's (REMOTE §9.4: a gate that is *not*
//! derivable from a row goes on the row). Two families left on that rule:
//!
//! - the composer's own RAM (bl-7cc8, deleted with the face it served,
//! bl-7942): the drafts keyed by target (§5.3), the selection they were typed
//! against, and the predicate that decided when a send cleared one.
//! - the form and ball-row rules (bl-33e9): whether a typed goal or ball title
//! is blank, whether a typed work directory exists, and whether a §3.5
//! `JoinState` permits assign / release / close. The first two judge a
//! *seat's form inputs* before a fire, and the executor at the far end
//! already refuses exactly what they predicted — the spawn boundary names a
//! bad work directory ([`crate::cli_outbound::work_dir_fault`]) and `bl`
//! itself refuses a claim of a bound ball — so the refusal at fire is the one
//! home. The third is a one-line fold over `BoundBall::state`, which
//! `Query::WorkspaceBalls` already answers.
//!
//! If a seat ever needs one of these facts stated instead of derived, it files
//! against yog and the reply is designed then.
use crate;
/// True iff `selected_branch` names an agent (by id, §2.3) in `agents`
/// that is **live** — [`AgentState::Live`] or [`AgentState::InFlight`],
/// the two states where a driver holds the executor lock (§2.11). Stop
/// targets a live executor (§2.9), and it is wanted precisely during tool
/// execution (a `Live` agent between model calls), not only mid-model-call
/// — so both live states are stoppable. Returns `false` for `None`, for an
/// id not present, and for a `Quiescent` or `Stopped` agent (no executor
/// to signal).
/// Nudge fires inference on the selected conversation from the state it is
/// already in (§8.2, bl-9bef) — `litany advance`, no text at all. So it is
/// the message gate without the content half, and [`stop_enabled`]'s
/// **complement** on state: a driver already holds the lease of a Live or
/// InFlight agent, and litany's own hop would take the clean no-op branch
/// (ARCH §2.11 Writer/driver totality). Offering it there would be a control
/// that fires and does nothing, which QUALITY H4 calls theater — so the two
/// verbs partition the states between them, Stop for the running ones and this
/// for the rest.
///
/// **One state at rest is exempt, for that same reason** (bl-fb87): a
/// conversation whose latest turn was cut off at the output limit
/// ([`Agent::truncated`], §4.4). Its transcript tail is an assistant turn with
/// no `tool_use`, and linked litany's `advance` derives `Warrant::NothingDue`
/// from exactly that — it releases the lease and exits without creating a
/// step. So the control would fire and do nothing, which is the theater the
/// partition above exists to prevent; the recovery is a Message, which needs
/// no gate because a deposit lands user-side and warrants a call.
/// The §7.3 step wound says so in words at the same moment
/// ([`crate::steps_view::OUTPUT_LIMIT`]).
///
/// Enabled iff an agent is selected, present in `agents`, Quiescent or
/// Stopped, and not truncated. `false` for no selection and for an id absent
/// from the set.
/// **Whether stopping this conversation takes a subtree with it** — true iff
/// `agent_id` has a descendant in the id set (§8.2), another agent whose id
/// extends `<agent_id>-…` (the hyphenated descent, §2.3). Pure over the ids.
///
/// **The fact is the same; what it names changed** (bl-6efc). It used to name
/// a CHOICE — whether to offer `--stop-children` beside Stop — and litany's
/// bl-3114 made `stop` walk every descendant unconditionally, so there is no
/// choice left to offer. The predicate survives because the operator's
/// question survives and got sharper: *does this stop reach further than the
/// conversation I am looking at?* One is a knob, the other is a consequence,
/// and only the consequence is still true. The wire keeps the name
/// `stop_children` until the next `PROTOCOL` bump (REMOTE §8.2).