From efc859b339e3abd8f2f99f90e825dfa14764e2a3 Mon Sep 17 00:00:00 2001 From: pat Date: Mon, 31 Aug 2026 07:21:18 +0000 Subject: [PATCH] =?UTF-8?q?docs:=20add=20workflows/=20chapter=20blank=20fo?= =?UTF-8?q?r=20review=20(PRD=20=C2=A75.4)?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- workflows/chapter-structure.md | 189 +++++++++++++++++++++++++++++++++ 1 file changed, 189 insertions(+) create mode 100644 workflows/chapter-structure.md diff --git a/workflows/chapter-structure.md b/workflows/chapter-structure.md new file mode 100644 index 0000000..bb619a4 --- /dev/null +++ b/workflows/chapter-structure.md @@ -0,0 +1,189 @@ +--- +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. +- 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) + +## [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"] + +#### 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] + +#### 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