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
//! **The yog server** — the standalone engine of the four-component split
//! (REMOTE §12): holder of the world, the balls and the conversations, with no
//! UI and no local execution.
//!
//! One world, one engine. The binary boots [`engine::Engine`], which derives
//! every workspace from disk, answers the §8.5 control [`boundary`] over the
//! REMOTE §9.5 [`wire`], and drives `litany`/`bl`/`bz` as children of the
//! nested [`world`]. Every seat — the `lernie` window, an android client, a
//! `yog gesture` from an agent's own bash — is a client of that boundary and
//! of nothing else; **yog paints nothing** (bl-7942 severed the egui face into
//! its own crate, REMOTE §8).
//!
//! **`docs/DESIGN.md` is the authority** for the state inventory, the attention
//! model, and the module map; the module docs below stay terse and defer to it.
//! The shape in brief: [`app`] holds the [`AppModel`] and its per-tick
//! derivation over the pure view-model modules — [`git_tree`], the [`nav`]
//! roster, [`attention`], [`projects`]/[`binding`], [`start`], [`ui_state`],
//! and the inspector projections ([`transcript`], [`steps_view`],
//! [`inboxview`], [`budgets`]) — and [`boundary`] is the one surface every act
//! and every read crosses, serialized by each module's own `wire`.
//! [`cli_outbound`] execs the binaries; [`actions`] holds the
//! message/stop/scan/close/unclaim/create/update verb surface; [`delete`] the
//! §3.6 unmaking; [`badge`] is what is left of the palette — the words a
//! derived row says, never a colour.
/// What a derived row **says** about a fact — the badge vocabulary that is
/// all a server keeps of the §11 palette (bl-7942).
/// The embedded brazen host (§16.7 W10) — internal, not library surface.
pub
/// How full a conversation's context is (§5.1 #35) — the latest step's prompt
/// against the window its own usage lines state. Fullness, not spend.
/// The capability control (§8.6, VISION §4.11) — the adjudicator litany's
/// tool-control seam consults before every granted tool invocation.
/// The REMOTE §13.2 DHT rendezvous client (bl-df31) — bencode, KRPC walks and
/// BEP 44 signed items, a pure client of the commons and never a node.
/// The one assembly a bare `yog` boots (VISION §5 V5) — model, worker, bridge,
/// gesture consumer, monitor sentry, fleet pilot and the wire listener.
/// **Is this box wired up?** (bl-28f4) — the one read that asks every question
/// a first conversation depends on at once, and names the act that fixes each.
/// Where to cut a string that will not fit (QUALITY G1, L4) — one rule, cut
/// where the information is not. Machine strings only; prose keeps its head.
pub
/// The VISION §4.10 mutating fan — N isolated candidate attempts over one
/// delivery obligation, materialized through balls' attempt capability.
/// Named deterministic world states a client harness can dial and render
/// (bl-8741) — the fixture roster, its writer and the `yog fixture` verb.
/// The VISION §4.3 armed loop — off until the operator arms it per workspace.
/// **Whether this box can author a commit at all** (§8.1, bl-c28c): the named
/// prerequisite the two start doors hold, asked of `git` itself.
pub
/// **The learning loop's operator half** (bl-dd88): the staged proposals a
/// reviewer left, one of them whole, and the settle that accepts or rejects one.
/// The REMOTE §4 client registry (bl-8bbc): who participates in which
/// workspace, and each client's own per-seat home.
/// The §3.9 attempt science projection (VISION §4.10 item 7): one derived row
/// per delivery attempt, joining frozen inputs, refs, usage and outcome.
/// I3's scratch temp (§2, §5.2): its one naming, and the startup sweep of
/// leftovers — internal, not library surface.
pub
/// yog's litany tool injection (REMOTE §5, bl-c907) — the `clients` tool, the
/// agent's durable loaded set, and the router the executor consults.
/// The client/server wire (REMOTE §9.5, bl-b6fa) — the engine's mTLS listener,
/// a seat's transport, and the framing between them.
pub use ;
pub