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
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
//! Workspace deletion — the §3.6 unmaking (DESIGN §3.6, the §8.1 planner idiom,
//! the §8.2 verb row).
//!
//! Deletion is the raise's inverse at the raise's altitude: raising is `mkdir -p`
//! the names root + `litany new` under the operator's chosen name (§3.1, §3.4),
//! so unmaking is the release of the
//! sphere's live claims followed by removal of the workspace directory — a write
//! to yog's **own** names root, never inside a workspace (I2 stands untouched).
//! Because the dir's existence *is* the registration (§3.1), the removal is the
//! de-registration; there is no registry to update.
//!
//! Two pure halves live here and one effectful one in [`exec`]:
//!
//! - [`Confirmation`] — what the §3.6 dialog states and what the plan is built
//! from: the conversations that die (by display name), the bound balls it
//! releases (by id), and the **gate** — the live conversations, the §10 "?"
//! uncertainty counting as live (fail closed). One derived object drives the
//! dialog, the refusal and the plan, so the operator confirms exactly what
//! runs.
//! - [`plan`] — the ordered [`Step`] sequence. Releases first, removal last, so
//! a crash anywhere leaves a live workspace with some claims released
//! (benign, re-runnable), never a removed workspace with steps unfinished.
//! Convergent on re-run: the released balls have left the join, so a re-plan
//! is the shorter remainder.
//!
//! **Arming is by naming the object** (§3.6's confirmation doctrine, normative
//! for every future destructive verb): [`Confirmation::armed`] is true only when
//! the operator has typed the workspace's own name. Obscurity is not the safety
//! mechanism; the typed name is — and the verb takes **no keyboard binding,
//! ever**, so no reflex can reach it.
use crateConversation;
use ;
pub use ;
/// One live bound ball the unmaking releases (§3.6 step 1) — the ball's id and
/// the §5.1 #1 **name** of the project whose store holds it.
///
/// A name rather than the `bl` cwd since bl-b4b5, for the reason the join row
/// it is copied off carries one (REMOTE §8.1): a confirmation is what a *seat*
/// states, and a seat holding an answer must be able to build the same object
/// the engine gates on. [`plan`] resolves it back to the clone the verb runs
/// in, at the one seam that owns the round trip.
/// What the §3.6 dialog states and the plan runs — derived, never stored: the
/// workspace's name, every conversation that dies (by display name), the live
/// ones (the gate), and the claims the unmaking releases.
///
/// **It no longer carries the workspace's path** (bl-b4b5). The path was the
/// address the gesture had already named, spelled a second time as an
/// engine-side directory — §8.1's own test — and it made the object
/// unbuildable by a seat that reads over a wire. [`plan`] takes the path from
/// the caller that resolved the address, which is where it already was.
/// **The same object off answers alone** (REMOTE §9.7, bl-b4b5) — what the §3.6
/// dialog derives at a seat that holds no world: the workspace's own name, the
/// landed `Query::Conversations` forest, and the landed `Query::WorkspaceBalls`
/// listing.
///
/// It is [`confirmation`] with its two inputs read from the other end, and it
/// answers the *same type*: one `armed`, one `refused`, one `ball_ids`,
/// whichever side asks. The engine's own re-derivation at fire is unmoved and
/// stays authoritative (§9.8, bl-1747) — this is the painted affordance, which
/// may land an ask period late and may never be the thing that decides.
/// Derive the §3.6 confirmation for a workspace from its conversations
/// ([`crate::nav::convs::liveness`]) and the claims the §3.5 join binds to it.
/// One step of the unmaking plan (§3.6), in the §8.1 planner idiom: pure data,
/// order load-bearing, each step individually convergent on re-run.
/// The §3.6 plan for a confirmed unmaking: every release, then the prune, then the
/// removal. The gate is **not** re-checked here — [`plan`] is pure, and the one
/// place a delete is armed is [`Confirmation::armed`] at the entry point.
/// `workspace` is the path the caller already resolved the gesture's address
/// to, and `projects` the §5.1 #1 naming set each claim's project resolves
/// against — the same enumeration the name was minted over, so a claim always
/// resolves and one that somehow does not releases nothing rather than running
/// `bl` in a directory nobody named.