max / makenotwork

Serve /policy from a residual derived at build time The first screen on the seam (quasicoherent `793d99dd`), and the screen phase 2's sharp test was set against: **`/policy` compiles to a single `&'static str`**, 4879 bytes of it, asserted in `quasi::residuals::tests::the_policy_page_is_one_literal`. What made that reachable was two things landing together. The page's copy left Rust for `content/policy.toml`, so the five section bodies are literals rather than reads of a `const`. And `own_prose` is `#[constant]`, so each of the six prose includes is evaluated once while the residual is derived instead of building a `Node` and running docengine on every request. The closing paragraph went into the content file too: a `const` is a path and not a literal, so leaving it in Rust would have cost the fold for one sentence. `export-residuals` writes `src/quasi/residuals/compiled.rs`. A residual is produced by rendering, so this crate's own build script cannot make one; a binary that links the crate can. What it writes is Rust source the next build compiles. The staleness check is a test rather than a hook, because a residual goes stale for two reasons and a hook catches one. A screen changing shows up in the diff beside it. quasi-webview changing does not: under the tree's `[patch]` block a renderer edit in another repo leaves every committed residual a version behind with no file here modified. `cargo test` re-derives against the renderer actually linked, so it sees both. `/policy` mounts itself rather than going through the adapter, whose job is to call a handler that answers a `Screen` and render it. There is no `Screen` to answer with here, and an `Outcome` carrying markup would put an opaque string in the vocabulary for every screen to reach for. The other six public documents are mounted the old way, unchanged, which is the coexistence the transition said it would have.