Builder Docs — write RFI responses, impact reports, and proposals

Builder Docs is the rich-text document editor inside Builder, alongside Sites and Slide Decks. It's where you write the things that don't belong as a webpage or a slide — federal RFI responses, nonprofit impact reports, capability statements, B2B proposals, internal memos, SOPs, anything long-form.

Where it lives:
Open Builder and click the "Docs" tab (next to Sites, Decks, Design, Signatures, Domains). Click "+ New Doc" to start one. Pick a kind from the dropdown — the choice drives both the starter template and the AI rewrite system prompt.

Doc kinds:
• Generic document — no special prompt; matches surrounding tone
• Federal RFI response — Section L compliance, capability + evidence, federal acquisition tone
• Nonprofit impact report — outcomes-led, donor-friendly, no platitudes
• Capability statement — NAICS, certs, contract vehicles, scannable
• Proposal — benefits-first, action-oriented, no hedging
• Memo — concise, action-clear, no preamble
• Standard operating procedure — imperative voice, one action per step

What the editor gives you:
• Headings (H1/H2/H3), bold, italic, underline, strikethrough, code, code blocks, blockquotes
• Bulleted and numbered lists
• Horizontal rules and inline images (drag onto the canvas or paste from clipboard)
• Left/center/right text alignment
• Undo/redo history
• Auto-save on a ~1.2-second debounce — the title bar shows "Saving…" → "Saved {timestamp}" so you know where things stand

AI rewrite (right rail):
Highlight any passage and the right-side panel becomes interactive. Pick a preset instruction tuned for the doc kind (e.g. "Make Section L compliant" on RFI responses; "Lead with outcomes" on impact reports) or type your own. Wally returns a rewritten version that replaces the selection. See "Rewriting a Doc passage with Wally" for the full walkthrough.

Whole-doc review (right rail, below the rewrite panel):
For end-to-end editorial passes, click "Ask Wally to review" and Wally reads the whole document. You get back 3–8 itemized suggestions — each one a short title, why it helps, and a before/after diff. Apply or skip them individually, or hit "Apply all". See "Reviewing a Builder artifact with Wally" for the full walkthrough.

Status:
Docs default to status='draft' so they don't surface in search until you flip them to 'published'. Use 'in-review' as an intermediate state when a doc is circulating for sign-off.

Where docs go:
Each doc is private to your org — only members can read or edit. Membership and ACL follow the same model as the rest of the platform; nothing leaves the org without an explicit share or export.

What's coming:
• Export to .docx — server-side generation for Word handoff
• Export to Google Docs — uses your existing Google OAuth connection
• Marketplace templates — share an RFI or impact-report skeleton between orgs
• Version history snapshots — restore a previous save
• Anchored comments — discuss a passage in-place
• Wally doc tools — "draft an impact report from our 2025 outcomes" without leaving chat