Fields: What is the work? · Who is it for? · What does "done" look like? (optionally a fourth: Any constraints?), each with a short worked placeholder.
Reasoning. A prospect who fills these in has met the seed's spine before they ever sign up — the input teaches the model the prospect should be holding. A single box is simpler but throws that away. Keep it to three or four fields; a teaser, not an induction.
Override: single free-text box for the lightest surface.
The seven: a legal matter, a clinical-trial protocol, a research synthesis, a product specification, a regulatory filing, a documentary, and an architecture decision record (ADR). Each chip pre-fills the D1 fields with a short worked seed.
Reasoning. The chips carry the glossary's anti-narrowing discipline: a chip set all of one kind teaches the prospect Loomworks is for that. The ADR is the deliberate software-domain chip — chosen over API docs, runbook, or design system because those read as "a nicer docs tool" a developer already half-has, whereas the ADR names a pain with no off-the-shelf substitute: why did we decide this? Its seed leads on that hook, showcasing the parts of Loomworks with no competitor — provenance, considerations kept not just verdicts, corrections preserved alongside the decision, relationships between decisions. It is the chip that shows recall, the real product. The documentary stays as the chip proving Loomworks reaches creative/non-technical work.
The prompt carries the four rooms, the lifecycle vocabulary (engagement, assertion, held/committed, consideration, cadence, provenance), the authority posture (the Operator approves; the system surfaces and signals), and the plain-terms discipline — drawn from the glossary.
Reasoning. FORAY's whole technique is a vocabulary-grounding prompt; we have its content. Embedding rather than fetching the glossary at runtime is simpler with no live dependency; the prompt carries a distilled grounding, revised deliberately when the vocabulary settles.
Note. The glossary earns a second job — human definition and AI grounding text. When its Shaping/Rendering entries leave provisional (batches 7–8), the prompt's room descriptions get a matching pass.
<h3>-sectioned HTML.Reasoning. Mirrors the Business Analyzer's sectioned-HTML contract, mapped to the four rooms plus a benefits close where the prospect's "why care" is answered in their own domain.
Override: add/drop/rename sections.
loomworks-marketing (Cloudflare Pages).Reasoning. A public marketing surface must be always-on. The FORAY tools run a server on the M4 behind a tunnel — fine for a demo, but it makes the page's headline feature depend on a local machine being awake and connected. The marketing page is Cloudflare Pages (always-on, global); a Worker keeps the generator's uptime identical to the page's, with no machine behind it. It is genuinely same-origin (no proxy hop, no CORS dance), holds the key as an edge secret, scales to zero when idle and to spikes under load, and brings edge rate-limiting and bot protection — exactly what an unauthenticated public AI endpoint spending API credits needs. The one cost is a new deploy shape for CC versus the FORAY Flask server: a one-time setup tax against a permanent always-on win. The M4-tunnel pattern stays right for internal/demo tools — but this is the shop window, and the shop window cannot depend on the laptop being awake.
Output retention is client-side only: copy, download, print-to-PDF.
Reasoning. A sales aid, not a corpus. The protocol's auto-capture pattern exists if harvesting is ever wanted, but that carries privacy weight (retaining descriptions of strangers' businesses) and is a separate, later decision.
Override: opt into harvesting now — but that pulls in a storage decision and a privacy posture, expanding scope.
Reasoning. The two-step chain is the technique that makes the output bespoke rather than templated — the whole reason to copy the Business Analyzer over a one-shot generator. Analyze-only first would launch the weaker half; the second call is little more build (same server, same grounding, a second prompt).
Override: analyze-only at launch, illustration as a fast follow, for the smallest first cut.
After an example has been generated, the prospect may trigger a separate action to see a draft toward the engagement's Foundation Document: the four answers they gave, written into the shape an engagement starts from. It renders as plain text in a read-only text area with a Copy control; the prospect lifts their own words to their own clipboard. The page persists nothing and creates nothing.
Reasoning. The lowest-friction take-away: no carry-the-answers plumbing between the static page and the authenticated flow, no sign-up funnel, and "nothing is saved" in its cleanest form — the person copies their own words. It is labeled a draft toward the Foundation Document — not "seed" (a methodology noun a public page should not speak; "Foundation Document" is the plain-English name for what the seed is) and not a finished Foundation Document (the finished one is made the proper way through the create-engagement conversation, where induction runs). The one creation path (create-engagement → induction) is untouched; D8 produces reusable text, not a second seed-making route.
Paths set aside (preserved). A literal engine seed-commit from the marketing page — rejected: seed creation is a three-step authenticated Operator flow with induction; a save-nothing page cannot perform the most save-everything action. Handoff-with-plumbing — dropped: the text-area-with-Copy delivers the same reusable-answers value with zero plumbing. A downloadable file labeled "seed" — rejected: a fabrication surface that teaches the wrong model, with seed-format conformance enforced by prompt rather than apparatus. A bare "seed" label — rejected: methodology-noun collision and plain-terms violation on a prospect-facing surface, at once.
Reconciliation with the seven. D8 extends, and does not contradict, the settled decisions. It honors D6 (ephemeral — nothing saved): a client-side copy action, no server-side artifact. It is distinct from D4 (output section structure): a separate prospect-triggered action, not a sixth section of the analyze→illustrate output. It leaves D7 untouched. No prior decision had settled the take-away question; D8 settles it.
The honesty guard (the one invariant). The output is a draft toward a Foundation Document, never the finished document; every surface that presents it carries that qualifier, which is not optional.
Residual (Operator): the qualifier wording is held as "a draft toward the engagement's Foundation Document." A shorter label ("Foundation Document draft") is fine; the bare "Foundation Document" with no qualifier is not. The qualifier is fixed; its phrasing is tunable.
A page on loomworks-marketing with three-to-four seed-spine input fields and seven cross-domain example chips; a same-origin server making two chained Anthropic calls (analyze → illustrate) grounded in a glossary-derived system prompt; five-section HTML output rendered in-page with copy/download/print; an opt-in Foundation Document draft (a save-nothing text-area-with-Copy the prospect triggers after the example, D8); the API key held as an edge secret in the Cloudflare Worker (never in the browser, per D5); nothing persisted.