--- status: draft-for-review type: chapter-template edition: 2026 vertical: # real-estate | financial-advisors | fractional-c-suite | higher-ed | communities | technology title: "" authors: [] recipe_ids: [XX-01, XX-02] last_updated: 2026-08-31 --- # Chapter structure (for review) This is the blank chapter, matching PRD §5.4 (locked 2026-08-31). Review the shape before anyone writes a real vertical. **How to use it.** Copy this file to `workflows/[vertical-slug].md` (example: `workflows/real-estate.md`). Replace `XX` with the vertical prefix. Leave this file as the blank. **What a chapter is.** A substantial essay for one vertical. Full workflows sit inside the argument, at the point they earn, not in an appendix and not as a stack of cards. **What a workflow is.** The unit of practice. Read it, run the Try-it (~15 min), share the result. That Try-it is what counts as activation. **Rules that do not move.** - Skip-to-Try-it at the top. Activation does not wait for the essay. - Safeguards before Method. Data handling is read before anyone pastes a client list. - Method shows real tool output, not a description of it. - Nested recipes stay open. Do not hide Method behind "click to reveal." - Every recipe has a stable ID and a heading it can link to. - Every recipe names its kit (who runs it, tools, files, model, time, cost, artifact). The chapter page shows the union at the top and the kit on each nested recipe. - No chatbot on the page. No crypto or Web3 language. - PDF must match this stack: essay + in-place recipes. **Vertical prefixes** | Vertical | Slug | ID prefix | |:--|:--|:--| | Real Estate | `real-estate` | `RE` | | Financial Advisors | `financial-advisors` | `FA` | | Fractional C-Suite | `fractional-c-suite` | `CS` | | Higher Ed | `higher-ed` | `HE` | | Communities | `communities` | `CM` | | Technology | `technology` | `TE` | Fill every `[bracket]`. Two nested recipes are shown so the essay-wraps-workflow pattern is obvious. Add more at the points in the argument they belong. Delete the unused slot rather than leaving a hollow block. --- # [Chapter title] [Vertical] · 2026 edition · [Author names] ## What this chapter is for [One short promise. The job this vertical's reader is trying to get done this week, and what they will be able to run by the end of the chapter.] **Skip to a Try-it:** [XX-01](#xx-01) · [XX-02](#xx-02) ## What you need The chapter page shows this before the essay. Union of the nested workflows. Named tools, sample files, Try-it time, sample-run cost. No live client data. - Tools: [named] - Files: [named samples we ship] - Model: [named, or "the model you already use"] - Time: [each Try-it] - Cost: [sample-run total, or "unknown"] ## [Essay: the stakes] [Why this work is hard here. Specific to the vertical, not a generic AI preamble. Name the actual failure: a listing that stalls, a client file that leaks, a committee that will not move.] ## [Essay: constraints] [What you cannot ignore in this vertical. Tools people already use. Compliance, clients, time. What "done" looks like for them.] ## [Essay: how we work here] [The practice this chapter argues for. Then the first workflow, at the moment the argument needs proof.] --- ### [Job title. This is the workflow title, written as the job.] **XX-01** · v0.1 · ~[N] min · ~$[cost or "free with tools you already have"] #### Kit Shown at the top of the nested recipe. Inventory, not instructions. Setup below still explains how to use these. - You run: [role] - Tools: [named tools, versions if it matters] - Files: [sample files we ship] - Model: [named, or "the model you already use"] - Time: ~[N] min - Cost: [amount or "free with tools you already have"] - You produce: [artifact] #### Problem [The real task. One job, not a category.] #### Actors - Who runs it: [role] - Who is affected: [client, student, team] - What the model is allowed to do: [draft / classify / retrieve]. What a human must still do: [send / approve / file] #### Setup - Tools: [named tools, versions if it matters] - Sample files: [what we ship with this recipe, or "use the anonymized packet below"] - Cost: [model/tool cost if known. If unknown, say so.] #### Safeguards Read this before the steps. - Data handling: [what never goes into the prompt. What is ok if stripped.] - Human oversight: [the checkpoint before anything leaves the building] - Failure modes: [how this goes wrong in this vertical] - Escalation: [who you call, and when you stop] #### Method Ordered steps. Paste the actual tool output inside the step that produced it. A screenshot or a quoted block beats a paraphrase. 1. [Step] ``` [real output] ``` 2. [Step] 3. [Step] #### Evidence [What "it worked" looks like. An artifact, a number, a before/after. Not "the user felt more confident."] #### Try it (~15 min) - Sample data: [what they use so they do not need a live client] - What to produce: [the artifact] - Done when: [a check they can mark. Completing this is activation.] #### Share the result [What they post: the outcome, not the workflow text. Point at the community template when it exists. Events, not content.] **Author:** [name] · **Sources:** [links or citations] · **Last updated:** [date] --- ## [Essay continues] [The argument picks back up. What the first recipe proved, what it did not. Then the next workflow, when the next claim needs proof.] --- ### [Second job title] **XX-02** · v0.1 · ~[N] min · ~$[cost] #### Kit Shown at the top of the nested recipe. Inventory, not instructions. Setup below still explains how to use these. - You run: [role] - Tools: [named tools, versions if it matters] - Files: [sample files we ship] - Model: [named, or "the model you already use"] - Time: ~[N] min - Cost: [amount or "free with tools you already have"] - You produce: [artifact] #### Problem [ ] #### Actors [ ] #### Setup [ ] #### Safeguards [ ] #### Method 1. [ ] 2. [ ] #### Evidence [ ] #### Try it (~15 min) [ ] #### Share the result [ ] **Author:** [name] · **Sources:** [ ] · **Last updated:** [date] --- ## Further workflows in this vertical - [XX-01](#xx-01) — [job title] - [XX-02](#xx-02) — [job title] - [Later IDs, once assigned] ## Sources [Chapter-level sources. Recipe-level citations stay on the recipe.] **Last updated:** 2026-08-31