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
//! **The fleet pane between frames** (bl-a43a): the three words its five acts
//! are composed from, the last receipt in the op's own name, and the two reads
//! that stand while it is open.
//!
//! # It is the tuning pane's shape, and every one of its seven ops names a wall
//!
//! `fleet`, `disband`, `arm`, `disarm`, `scan`, `science` and `work-diff` all
//! carry a workspace, so the pane's subject is the **aimed wall**: it opens on
//! a row, its reads are asked of that wall while it stands, and it is retired
//! when the aim moves (`super::tuning`, and `Model::aim_at`). Nothing about it
//! is the queue's shape, which is what tells it from the ball pane next door —
//! that one is two widths and this one is one.
//!
//! # It holds three words because three of its acts carry one
//!
//! A cap is a number, a project is a name and a model is a name; none of the
//! three is derivable from anything on the glass, so each is a box, and the
//! control that spends one stands down until it has something to spend
//! (§4.20's enablement rule: the parameter is missing, not the subject).
//!
//! **The boxes are bound to these fields and never to a copy** (`crate::ui::
//! fleet`, and the tuning editor before it): a draft is what the pane holds,
//! so an edit is a write to it and there is no second value for the two to
//! disagree about.
//!
//! # The receipt is read by the OP and never by the reply
//!
//! `fleet`, `disband`, `arm` and `disarm` answer with the same `armed` kind,
//! and the two families it spans are the fleet loop and the alignment monitor.
//! So [`Armed`] carries the op the poster stamped the frame with
//! (`crate::state::Said::Receipt`) and the flag the engine sent, and the pane
//! says both. A seat that read *which family* off the reply would be guessing
//! between two settings on two carriers.
//!
//! **Nothing here holds the loop's STATE**, and that is deliberate: whether a
//! loop is running is on the `board` answer, in the ball pane (DESIGN §4.31).
//! A second copy of it here would be a second authority, and the receipt below
//! is an event rather than a state — what happened when the operator pressed
//! the control, said once.
use ;
use crateDiff;
use crateAttempt;
/// **The fleet pane, while it is open**: the words its acts are composed from,
/// and the last thing an act answered.
/// **One receipt, in the op's own name.** The op is the poster's stamp and the
/// flag is the engine's; this seat joins them and classifies neither.