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
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
//! Parse, validate and render [Constela] documents — the constrained JSON UI
//! language — so an Autumn app can serve an interface a language model wrote.
//!
//! Enable with the Cargo feature `constela`.
//!
//! # The problem this solves
//!
//! Asking a model for a user interface and running what comes back is, in the
//! general case, remote code execution with extra steps: HTML from a model is
//! HTML from a stranger, and JSX or JavaScript from a model is worse. The usual
//! mitigations — sanitize the output, or sandbox an iframe — either throw away
//! the interactivity that made it worth generating or move the whole thing out
//! of the app.
//!
//! Constela takes the other route: the model does not emit code, it emits a
//! *description* in a JSON language with no escape hatch. There is no
//! expression form that calls a function, no attribute that holds script, no
//! way to spell `eval`. What a document can express is exactly what this module
//! can check, and this module checks all of it before anything renders.
//!
//! # Pipeline
//!
//! ```text
//! JSON ──parse──▶ Program ──validate──▶ Document ──render──▶ Markup
//! limits references, escaping,
//! depth allowlists, id prefixing,
//! size shapes render limits
//! ```
//!
//! [`parse`] runs the first two stages. Both constructors of [`Document`] —
//! that one and [`Document::from_program`] — go through
//! [`validate`], and there is no third, so a value of that type is a proof
//! that the checks ran.
//!
//! # Quick start
//!
//! ```
//! use autumn_web::constela::{Document, Limits, RenderContext};
//!
//! let source = r#"{
//! "version": "1.0",
//! "state": { "greeting": { "type": "string", "initial": "Hello, Autumn!" } },
//! "actions": [],
//! "view": {
//! "kind": "element",
//! "tag": "p",
//! "props": { "class": { "expr": "lit", "value": "greeting" } },
//! "children": [{ "kind": "text", "value": { "expr": "state", "name": "greeting" } }]
//! }
//! }"#;
//!
//! let document = Document::parse(source, &Limits::default())?;
//! let mut ctx = RenderContext::default();
//! ctx.state = document.initial_state();
//!
//! let ui = document.render(&ctx)?;
//! assert_eq!(ui.body.0, r#"<p class="greeting">Hello, Autumn!</p>"#);
//! # Ok::<(), autumn_web::constela::ConstelaError>(())
//! ```
//!
//! # Safety
//!
//! The guarantee, and the four independent controls that make it, are stated in
//! [`policy`]. In summary: allowlisted tags, allowlisted attributes with every
//! `on*` handler rejected, allowlisted URL schemes checked both statically and
//! again on every computed value, and every byte of document-derived output
//! routed through one of the renderer's two escape functions — with tag and
//! attribute names written only after passing the allowlists, so they are
//! fixed strings from a fixed set. On top of that, every element
//! id a document writes is rewritten with
//! [`RenderContext::id_prefix`], so a generated fragment cannot collide with —
//! or clobber — an id the host page's own scripts depend on.
//!
//! # Interactivity
//!
//! Autumn ships **no Constela client runtime**, and this module does not
//! generate JavaScript. What it does instead fits the framework it is in:
//!
//! - The view renders on the server, with expressions evaluated against state
//! the *app* owns.
//! - An event binding becomes `data-constela-on-{event}="{action}"` on the
//! element, so the app can wire it — to htmx, most naturally.
//! - [`Document::dispatch`] runs an action's pure state steps (`set`, `update`,
//! `setPath`, `if`) on the server and hands back the browser-side ones as
//! [`Effect`]s rather than performing them.
//!
//! Together those are enough for a working interactive UI over htmx with no
//! client-side interpreter: post the action name, dispatch it, re-render, swap
//! the fragment. `docs/guide/constela.md` has the route.
//!
//! Effects are reported rather than performed on purpose. `fetch` is the clear
//! case: running a model-authored URL from inside the app would give a prompt
//! injection the app's own network position, which is SSRF by construction. The
//! app decides, against its own allowlist, whether any of that should happen.
//!
//! # The supported subset
//!
//! Autumn implements the part of the upstream AST that a *server* can be
//! faithful to. Present: the `lit`, `state`, `var`, `param`, `bin`, `not`,
//! `cond`, `get`, `index`, `concat`, `array`, `obj`, `route` and `style`
//! expressions; all twelve view node kinds; the five state types; and the
//! `set`, `update`, `setPath`, `if`, `fetch`, `storage`, `navigate`, `delay`,
//! `interval` and `focus` steps.
//!
//! Absent, and rejected at parse time with a message naming what *is* supported:
//! `call` and `lambda` (a function registry), `ref` and `validity` (a live
//! DOM), `import` and `data` (a build-time loader), and `local` (component-local
//! state). A document using one fails loudly rather than rendering something
//! subtly different from what it asked for.
//!
//! Evaluation follows upstream's JavaScript semantics exactly — coercion,
//! truthiness, operator behaviour — with one documented divergence for division
//! by zero, which JSON cannot represent. See [`eval`].
//!
//! [Constela]: https://github.com/yuuichieguchi/constela
// autumn-panic-gate: request-path module — it parses, validates and renders a
// document written by a language model, so every panic in it is reachable by
// hostile input and would be a 500 rather than a diagnostic. Production code
// path must be panic-free. See CONTRIBUTING.md "Request-path panic gate".
// Justify exceptions with #[allow(clippy::<lint>, reason = "…")] at the
// narrowest scope.
use ;
pub use Program;
pub use ;
pub use ;
pub use RouteValues;
pub use ;
pub use ;
pub use ;
/// A Constela program that has passed [`validate`].
///
/// The type exists to make the check unforgeable: there is no constructor that
/// skips validation, so a function taking a `Document` never has to ask whether
/// the names in it resolve or whether its tags are on the allowlist. They do,
/// and they are.
/// Parse and validate a Constela document.
///
/// Shorthand for [`Document::parse`].
///
/// # Errors
///
/// As [`Document::parse`].