@forwardimpact/outpost 3.12.0 → 3.13.0

package/templates/.claude/skills/deck-review/assets/slide-annotator.js

@@ -7,20 +7,21 @@
  *             data-slide-selector=".slide"
  *             data-label-selector=".slide-num"></script>
  *
- * Click the “✎ Review” button (bottom-left), select text on a slide, optionally
- * add a note, and Add. Annotations autosave to localStorage immediately. Click
- * “Connect folder” once to (a) write a real sidecar JSON next to the page and
- * (b) resolve each highlight to its SOURCE line/column + context lines by
- * reading the page’s own source file. No build step, no server, no deps.
+ * Click the “✎ Review” button (bottom-left). Select text on a slide. Add an
+ * optional note. Then click Add. Annotations autosave to localStorage
+ * immediately. Click “Connect folder” once. The tool then writes a real
+ * sidecar JSON next to the page. It also reads the page’s own source file, so
+ * it resolves each highlight to its SOURCE line/column + context lines. The
+ * tool needs no build step, no server, and no dependencies.
  *
- * The connected folder is remembered across reloads (the directory handle is
- * stored in IndexedDB). On reload it reconnects silently if the browser still
- * grants permission; otherwise the button reads “Reconnect folder” and one
- * click re-grants access without re-picking the folder.
+ * The tool remembers the connected folder across reloads. It stores the
+ * directory handle in IndexedDB. On reload it reconnects silently if the
+ * browser still grants permission. If not, the button reads “Reconnect
+ * folder”. One click then re-grants access without a new folder pick.
  *
- * Optional host hook: if the page defines `window.deckGoto(index)` the panel’s
- * “Go” buttons will navigate to the right slide. Without it, the tool still
- * works (it falls back to scrollIntoView).
+ * Optional host hook. If the page defines `window.deckGoto(index)`, the
+ * panel’s “Go” buttons navigate to the right slide. Without it, the tool
+ * still works (it falls back to scrollIntoView).
  *
  * SIDECAR JSON SCHEMA (what an agent reads to act on the feedback):
  * {
@@ -120,7 +121,8 @@
 ::highlight(sa-all){background:rgba(255,221,0,.45);text-decoration:underline;text-decoration-color:#caا}\
 ::highlight(sa-active){background:rgba(255,0,110,.35)}\
 @media print{.sa-ui{display:none!important}}";
-  // (one stray glyph above is harmless inside a CSS comment-free value; replaced below)
+  // The stray glyph above is harmless in a comment-free CSS value.
+  // The next line replaces it.
   css = css.replace("#caا", "#b38f00");
   var styleEl = document.createElement("style");
   styleEl.textContent = css;
@@ -160,13 +162,14 @@
   ui.note = ui.pop.querySelector("textarea");
   var onlyThisSlide = false;
 
-  // Keep the tool's own keystrokes from leaking to the host page (e.g. a deck's
-  // Space / arrow-key slide navigation) while typing a note or using a panel
-  // button. We stop propagation in the BUBBLE phase, so: (a) our capture-phase
-  // Esc handler has already run, and (b) the default action — typing the
-  // character, moving the caret — still happens. Scoped to the tool's own UI,
-  // so arrow/Space navigation still works when focus is on the page itself.
-  // Independent of any host: we never touch the host's handlers, just our own.
+  // Keep the tool's own keystrokes away from the host page. One example is a
+  // deck's Space and arrow-key slide navigation. This applies while the user
+  // types a note or uses a panel button. We stop propagation in the BUBBLE
+  // phase. So our capture-phase Esc handler already ran. The default action
+  // also still happens. The character appears and the caret moves. We scope
+  // this to the tool's own UI. Arrow and Space navigation still works when
+  // focus is on the page itself. This works with any host. We never touch
+  // the host's handlers, only our own.
   [ui.fab, ui.banner, ui.panel, ui.pop].forEach(function (node) {
     ["keydown", "keyup", "keypress"].forEach(function (type) {
       node.addEventListener(type, function (e) { e.stopPropagation(); });
@@ -210,10 +213,11 @@
     else if (review) { toggle(false); e.stopPropagation(); }
   }, true);
 
-  // In review mode, swallow ONLY the click that ends a text-selection drag, so a
-  // host with click-to-advance can't navigate out from under the highlight. Plain
-  // clicks (with no active selection) pass through untouched — footer dots, links
-  // and buttons keep working. Non-invasive and host-agnostic.
+  // In review mode, swallow ONLY the click that ends a text-selection drag.
+  // A host with click-to-advance then cannot navigate out from under the
+  // highlight. Plain clicks (with no active selection) pass through
+  // untouched. Footer dots, links and buttons keep working. The tool does
+  // not intrude, and it works with any host.
   function clickSuppressor(e) {
     if (e.target.closest(".sa-ui")) return;
     var sel = window.getSelection();
@@ -252,9 +256,10 @@
     var off = offsets(slide, range);
     var text = slide.textContent;
     var slides = allSlides();
-    // Anchor on the underlying DOM text (text.slice), NOT Selection.toString():
-    // the latter applies text-transform (e.g. uppercase headings) and would no
-    // longer match the source or the slide's textContent.
+    // Anchor on the underlying DOM text (text.slice). Do NOT use
+    // Selection.toString(). It applies text-transform (e.g. uppercase
+    // headings). The result would no longer match the source or the slide's
+    // textContent.
     var storedQuote = text.slice(off.start, off.end) || quote;
 
     pending = {
@@ -394,7 +399,7 @@
     if (!list.length) {
       ui.list.innerHTML = '<div class="sa-empty">' +
         (onlyThisSlide ? "No annotations on this slide." :
-        "No annotations yet.<br><br>Select text on a slide to highlight it. Highlights autosave locally; click <b>Connect folder</b> to write the sidecar JSON and capture source line numbers.") +
+        "No annotations yet.<br><br>Select text on a slide to highlight it. Highlights autosave locally. Click <b>Connect folder</b> to write the sidecar JSON and capture source line numbers.") +
         '</div>';
       return;
     }
@@ -417,7 +422,7 @@
   function currentSlideIndex() {
     var slides = allSlides();
     for (var i = 0; i < slides.length; i++) if (slides[i].classList.contains("active")) return i;
-    // else the slide most centered in viewport
+    // else the slide most centered in the viewport
     var best = 0, bestD = Infinity, cx = window.innerWidth / 2, cy = window.innerHeight / 2;
     slides.forEach(function (s, i) {
       var r = s.getBoundingClientRect();
@@ -442,12 +447,13 @@
     if (ui.count) ui.count.textContent = state.annotations.length;
   }
 
-  /* Persist the connected directory handle across reloads. FileSystemHandles are
-   * structured-cloneable, so they live in IndexedDB (localStorage is strings
-   * only). Re-granting read/write permission after a reload needs a user
-   * gesture, so a remembered folder reconnects with one click via the same
-   * "Connect folder" button rather than the full directory picker. Keyed by
-   * cfg.target so distinct decks in a folder don't clobber each other. */
+  /* Persist the connected directory handle across reloads. FileSystemHandles
+   * are structured-cloneable, so they live in IndexedDB (localStorage holds
+   * strings only). A re-grant of read/write permission after a reload needs
+   * a user gesture. So a remembered folder reconnects with one click through
+   * the same "Connect folder" button. It does not open the full directory
+   * picker. The key is cfg.target, so distinct decks in a folder do not
+   * clobber each other. */
   var IDB_NAME = "slide-annotator", IDB_STORE = "handles";
   function idbOpen() {
     return new Promise(function (resolve, reject) {
@@ -484,16 +490,17 @@
       : rememberedHandle ? "Reconnect folder" : "Connect folder";
   }
 
-  // Adopt a (freshly picked or re-granted) handle: link source, load any
-  // sidecar, and remember it for next time. Shared by connect and restore.
+  // Adopt a freshly picked or re-granted handle. Link the source, load any
+  // sidecar, and remember the handle for next time. Both connect and restore
+  // call this.
   async function adoptFolder(handle) {
     dirHandle = handle;
-    // read page source → enables source line/column resolution
+    // read the page source → the tool can then resolve source line/column
     try {
       var fh = await dirHandle.getFileHandle(cfg.target);
       sourceText = await (await fh.getFile()).text();
       state.annotations.forEach(function (a) { a.source = locateInSource(a); });
-    } catch (e) { sourceText = null; setStatus("Connected, but '" + cfg.target + "' not found in folder — line numbers unavailable."); }
+    } catch (e) { sourceText = null; setStatus("Connected, but the folder has no '" + cfg.target + "'. Line numbers are unavailable."); }
     // load an existing sidecar if present
     try {
       var sh = await dirHandle.getFileHandle(SIDECAR);
@@ -503,12 +510,13 @@
     rememberedHandle = null;
     updateConnectLabel();
     persistLocal(); renderPanel(); renderHighlights();
-    setStatus("Connected. Saving to " + SIDECAR + (sourceText ? " · source linked" : ""));
+    setStatus("Connected. Saves to " + SIDECAR + (sourceText ? " · source linked" : ""));
   }
 
   async function connectFolder() {
-    // Prefer a folder remembered from a prior session: re-granting permission is
-    // a single click (this click IS the required user gesture), no picker.
+    // Prefer a folder remembered from a prior session. A permission re-grant
+    // takes a single click (this click IS the required user gesture). The
+    // picker does not open.
     if (rememberedHandle) {
       try {
         var perm = await rememberedHandle.requestPermission({ mode: "readwrite" });
@@ -524,10 +532,11 @@
     }
   }
 
-  // On load, try to restore a previously connected folder. queryPermission needs
-  // no gesture; if it's still "granted" we reconnect silently. If it's "prompt",
-  // we keep the handle so the next "Connect folder" click reconnects with one
-  // grant dialog (no picker). Handles cleared/denied storage are ignored.
+  // On load, try to restore a previously connected folder. queryPermission
+  // needs no gesture. If it is still "granted", we reconnect silently. If it
+  // is "prompt", we keep the handle. The next "Connect folder" click then
+  // reconnects with one grant dialog (no picker). We ignore a handle from
+  // cleared or denied storage.
   function restoreFolder() {
     idbGet(cfg.target).then(function (handle) {
       if (!handle || typeof handle.queryPermission !== "function") return;
@@ -535,7 +544,7 @@
         if (perm === "granted") { adoptFolder(handle); }
         else {
           rememberedHandle = handle; updateConnectLabel();
-          if (review) setStatus("Folder '" + cfg.target + "' remembered — click Reconnect folder.");
+          if (review) setStatus("Folder '" + cfg.target + "' remembered. Click Reconnect folder.");
         }
       }).catch(function () {});
     });
@@ -553,7 +562,7 @@
       } catch (e) { setStatus("Disk write failed (" + e.name + "). Downloaded instead."); }
     }
     download(SIDECAR, json);
-    setStatus("Downloaded " + SIDECAR + " — move it next to the deck.");
+    setStatus("Downloaded " + SIDECAR + ". Move it next to the deck.");
   }
 
   async function loadDisk() {
@@ -669,7 +678,7 @@
     // Supply page source to resolve source line/column without the folder picker.
     setSource: function (text) { sourceText = text; state.annotations.forEach(function (a) { a.source = locateInSource(a); }); persistLocal(); renderPanel(); },
     get state() { return state; },
-    // for automation/testing:
+    // for automation and tests:
     _capture: captureSelection,
     _confirm: function (note) { if (pending) { ui.note.value = note || ""; confirmPending(); } }
   };

package/templates/.claude/skills/deck-summarize/SKILL.md

@@ -1,21 +1,25 @@
 ---
 name: deck-summarize
-description: Synthesize PowerPoint decks into engineer-friendly markdown briefs covering Jobs-To-Be-Done, dependencies, and synthetic data needs. Use when the user asks to break down, summarize, or make sense of a slide deck (.pptx) for engineering work.
+description: Synthesize PowerPoint decks into engineer-friendly markdown briefs. Each brief covers Jobs-To-Be-Done, dependencies, and synthetic data needs. Use when the user asks to break down, summarize, or make sense of a slide deck (.pptx) for engineering work.
 compatibility: Node.js only — no external dependencies.
 ---
 
 # Synthesize Deck
 
+Write tier: `0-Draft` (promotion is a human act)
+Frontmatter: none
+
 Turn messy PowerPoint specification decks into clear, actionable markdown briefs
-that forward deployed engineers can build from. Strip business jargon and focus
-on what matters: what needs to be built, what blocks progress, what data is
-needed to start prototyping.
+that forward deployed engineers can build from. Strip business jargon. Focus on
+what matters: what the team must build, what blocks progress, and what data you
+need to start a prototype.
 
 ## Trigger
 
-The user asks to summarize, synthesize, or break down a `.pptx` deck; make sense
-of a specification or proposal deck for engineering; create an engineering brief
-from a slide deck; or understand what a project deck is actually asking for.
+Run when the user asks to summarize, synthesize, or break down a `.pptx` deck.
+Run when the user wants to make sense of a specification or proposal deck for
+engineering. Run when the user asks for an engineering brief from a slide deck.
+Run when the user wants to understand what a project deck really asks for.
 
 ## Prerequisites
 
@@ -30,21 +34,23 @@ from a slide deck; or understand what a project deck is actually asking for.
 ## Outputs
 
 - One markdown file per deck (or one combined file for related decks) written to
-  `Knowledge/Projects/{Project Name} - Engineering Brief.md`.
+  `0-Draft/{Project Name} - Engineering Brief.md`. The human promotes a
+  finished brief into `3-Team/Projects/`.
 
 <do_confirm_checklist goal="Verify the brief is engineer-actionable before
 delivering">
 
-- [ ] No invented requirements — every claim traces to the deck.
-- [ ] Plain language; no marketing jargon (no "synergize", "orchestrate",
+- [ ] No invented requirements. Every claim traces to the deck.
+- [ ] Plain language, with no marketing jargon (no "synergize", "orchestrate",
       "leverage", "intelligent \_\_\_ hub").
-- [ ] JTBDs describe the user's goal, not the proposed solution; one job per
-      statement; each includes the "so that".
-- [ ] Data dependencies table flags blockers (missing, locked, compliance).
+- [ ] JTBDs describe the user's goal. They do not describe the proposed
+      solution. One job per statement. Each job includes the "so that".
+- [ ] The data-dependencies table flags blockers (missing, locked, compliance).
 - [ ] Synthetic data needs name fields, ranges, edge cases, and volume.
 - [ ] Gaps and open questions list what an engineer would notice missing.
-- [ ] Brief is under 2,000 lines — a summary, not a transcription.
-- [ ] Knowledge base looked up for mentioned people, orgs, and projects.
+- [ ] The brief is under 2,000 lines. It summarizes the deck. It does not
+      transcribe it.
+- [ ] You looked up mentioned people, orgs, and projects in the knowledge base.
 
 </do_confirm_checklist>
 
@@ -65,20 +71,21 @@ For multiple decks, pass all files at once. To save the extracted text:
 node .claude/skills/deck-summarize/scripts/extract-pptx.mjs "$FILE_PATH" -o /tmp/deck_extract.txt
 ```
 
-Read all extracted text before continuing.
+Read all extracted text before you continue.
 
 ### 2. Identify the core problem
 
-Plain-language answers to: what process exists today; what's broken, slow, or
-painful; who suffers. Don't restate the deck's framing.
+Give plain-language answers. Name the process that exists today. Name what is
+broken, slow, or painful. Name who suffers. Don't restate how the deck frames
+the problem.
 
 ### 3. Extract Jobs-To-Be-Done
 
 Format: `When [situation], I need to [action], so that [outcome].`
 
-Group by user role/persona. One job per statement. Use the user's goal, not the
-proposed solution. A job should still make sense if you discard the deck's
-solution. Don't restate the deck's feature list as jobs and don't reuse its
+Group by user role/persona. One job per statement. Use the user's goal. Do not
+use the proposed solution. A job should still make sense if you discard the
+deck's solution. Don't restate the deck's feature list as jobs. Don't reuse its
 jargon.
 
 ### 4. Map dependencies
@@ -87,53 +94,56 @@ jargon.
 [references/brief-template.md](references/brief-template.md#data-dependencies-table).
 Flag blockers (missing, locked, unstructured, compliance).
 
-**4b. Systems & integrations** — every external system/API/platform: what the
-integration does, read-only vs read-write, API vs manual/scraping, access
-confirmed?
+**4b. Systems & integrations** — list every external system, API, and platform.
+For each one, say what the integration does. Say whether it is read-only or
+read-write. Say whether access runs through an API or through manual work or
+scraping. Say whether someone confirmed access.
 
-**4c. People & approvals** — approvals, reviews, or co-creation needed before
-engineering can proceed. Flag long lead-time items (legal, compliance, vendor
-contracts).
+**4c. People & approvals** — list the approvals, reviews, or co-creation that
+must happen before engineering can proceed. Flag long lead-time items (legal,
+compliance, vendor contracts).
 
 ### 5. Define synthetic-data needs
 
 For each core feature/use case:
 
 - **Generate:** entity, key fields and types, realistic value ranges and
-  distributions, edge cases that matter, volume for meaningful testing.
+  distributions, edge cases that matter, volume for a meaningful test.
 - **Simulate:** workflows and state transitions, time-series patterns,
   multi-actor interactions, error/failure modes.
-- **Format:** prefer CSV/JSON; PII-shaped fake data only — never real PII;
-  include happy-path _and_ adversarial examples; consider ML training/eval data.
+- **Format:** prefer CSV/JSON. Use PII-shaped fake data only. Never use real
+  PII. Include happy-path _and_ adversarial examples. Consider ML training and
+  eval data.
 
 ### 6. Translate the proposed solution
 
-Describe the build in engineering terms: components, what each does in plain
-terms, how they connect, end-to-end data flow, AI/ML capabilities and what
-they're actually doing. Translate branded names — e.g. "Intelligent Intake Hub"
-→ "OCR + NLP pipeline that extracts structured fields from scanned enrollment
-forms"; "Copay Guardian" → "Anomaly detection on weekly claims data".
+Describe the build in engineering terms. Cover the components and what each does
+in plain terms. Cover how they connect and the end-to-end data flow. Cover the
+AI/ML capabilities and what they actually do. Translate branded names. For
+example, "Intelligent Intake Hub" →
+"OCR + NLP pipeline that extracts structured fields from scanned enrollment
+forms". "Copay Guardian" → "Anomaly detection on weekly claims data".
 
 ### 7. Identify what's missing
 
-Call out: features without clear data sources; AI capabilities without a
-training-data strategy; assumed integrations; user workflows that skip edge
-cases; metrics promised without measurement infrastructure; timeline–scope
-mismatches.
+Call out features without clear data sources. Call out AI capabilities without a
+training-data strategy. Call out assumed integrations. Call out user workflows
+that skip edge cases. Call out metrics promised without measurement
+infrastructure. Call out timeline–scope mismatches.
 
 ### 8. Assemble the brief
 
 Use the structure in
 [references/brief-template.md](references/brief-template.md). Save to
-`Knowledge/Projects/{Project Name} - Engineering Brief.md`. For multiple related
+`0-Draft/{Project Name} - Engineering Brief.md`. For multiple related
 decks, write one combined brief with shared dependencies.
 
 ### 9. Save and report
 
-Tell the user the file path and give a 3-sentence project summary.
+Tell the user the file path. Give a 3-sentence project summary.
 
-## Writing style
+## Style
 
-Plain language, concrete over abstract, honest about uncertainty, opinionated
-when helpful (flag dependency or timeline risks), short sentences. Engineers
-scan, they don't read essays.
+Use plain language. Choose the concrete over the abstract. Be honest about
+uncertainty. Be opinionated when it helps, and flag dependency or timeline
+risks. Keep sentences short. Engineers scan. They don't read essays.

package/templates/.claude/skills/deck-summarize/references/brief-template.md

@@ -1,7 +1,7 @@
 # Engineering Brief Template
 
 Reference template for `deck-summarize` Step 8. Save the assembled brief to
-`Knowledge/Projects/{Project Name} - Engineering Brief.md`.
+`0-Draft/{Project Name} - Engineering Brief.md`.
 
 ```markdown
 ---
@@ -76,9 +76,10 @@ what's realistic and what depends on what}
 
 ## Data dependencies table
 
-For Step 4a, fill in this table. Flag any data that doesn't seem to exist yet,
-is locked behind inaccessible systems, is unstructured and would need heavy
-preprocessing, or carries compliance/privacy constraints.
+For Step 4a, fill in this table. Flag any data that doesn't seem to exist yet.
+Flag data that is locked behind inaccessible systems. Flag unstructured data
+that would need heavy preprocessing. Flag data that carries compliance or
+privacy constraints.
 
 | Data        | Where It Lives             | Format                             | Access                          | Blocker?       |
 | ----------- | -------------------------- | ---------------------------------- | ------------------------------- | -------------- |

package/templates/.claude/skills/deck-summarize/scripts/extract-pptx.mjs

@@ -2,9 +2,9 @@
 /**
  * Extract text from PowerPoint (.pptx) slides.
  *
- * PPTX files are ZIP archives containing XML. This script extracts all text
- * from each slide and outputs it as structured markdown with slide headings.
- * Handles multiple files and outputs to stdout or a file.
+ * A PPTX file is a ZIP archive that holds XML. This script extracts all text
+ * from each slide. It outputs the text as structured markdown with slide
+ * headings. It handles multiple files. It writes to stdout or to a file.
  *
  * Usage:
  *   node scripts/extract-pptx.mjs <path-to-pptx>
@@ -12,7 +12,8 @@
  *   node scripts/extract-pptx.mjs file1.pptx file2.pptx
  *   node scripts/extract-pptx.mjs -h|--help
  *
- * No external dependencies — uses Node.js built-in modules only.
+ * The script needs no external dependencies. It uses Node.js built-in
+ * modules only.
  */
 
 import { readFileSync, writeFileSync } from "node:fs";
@@ -26,7 +27,7 @@ Usage:
   node scripts/extract-pptx.mjs -h|--help
 
 Options:
-  -o <path>   Write output to file instead of stdout
+  -o <path>   Write output to a file instead of stdout
   -h, --help  Show this help
 
 Output: Markdown-formatted text with ## Slide N headings per slide.
@@ -136,8 +137,8 @@ function readEntry(buf, entry) {
 }
 
 /**
- * Extract all text content from slide XML using the DrawingML namespace.
- * Matches <a:t>text</a:t> elements used by PowerPoint.
+ * Extract all text content from slide XML with the DrawingML namespace.
+ * The pattern matches the <a:t>text</a:t> elements that PowerPoint uses.
  * @param {string} xml
  * @returns {string[]}
  */

package/templates/.claude/skills/doc-collab/SKILL.md

@@ -1,13 +1,17 @@
 ---
 name: doc-collab
-description: Help the user create, edit, and refine documents in the knowledge base. Use when the user asks to create, edit, review, or collaborate on a document. Supports direct editing and approval-based workflows with knowledge base context for entity references.
+description: Help the user create, edit, and refine documents in the knowledge base. Use when the user asks to create, edit, review, or collaborate on a document. Supports direct edits and approval-based workflows, with context from the knowledge base for entity references.
 ---
 
 # Document Collaboration
 
-Help the user create, edit, and refine documents in the knowledge base. Supports
-direct editing and approval-based workflows. Always uses knowledge base context
-for entity references.
+Write tier: `0-Draft` (working copies; the human promotes)
+Frontmatter: none
+
+Help the user create, edit, and refine documents in the knowledge base. This
+skill supports direct edits and approval-based workflows. It always uses context
+from the knowledge base for entity references. New documents start in
+`0-Draft/`. The human promotes a finished document into its tier.
 
 ## Trigger
 
@@ -15,62 +19,63 @@ Run when the user asks to create, edit, review, or collaborate on a document.
 
 ## Prerequisites
 
-- Knowledge base directory exists
+- The KB root exists with its tier directories
 
 ## Inputs
 
-- User's editing instructions
-- `Knowledge/` — existing notes and documents
+- The user's edit instructions
+- The tier directories — existing notes and documents
 - Document to edit (user-specified or searched)
 
 ## Outputs
 
-- Created or modified documents in `Knowledge/` or user-specified location
+- New documents in `0-Draft/` (or a user-specified location)
+- Modified documents in the tier where the user points
 
 ---
 
 ## First: Ask About Edit Mode
 
-**Before doing anything, ask:** "Should I make edits directly, or show you
+**Ask before you do anything:** "Should I make edits directly, or show you
 changes first for approval?"
 
-- **Direct mode:** Make edits immediately, confirm after
-- **Approval mode:** Show proposed changes, wait for approval
+- **Direct mode:** Make edits immediately, then confirm
+- **Approval mode:** Show proposed changes, then wait for approval
 
 Follow their choice for the entire session.
 
 ## Core Principles
 
-- **Re-read before every response** — the user may have edited the file manually
+- **Re-read before every response** — the user may edit the file manually
 - **Be concise** — don't propose outlines unless asked
-- **Don't assume** — if unclear, ask ONE simple question
-- **Use knowledge context** — search knowledge base for mentioned entities, use
-  `[[wiki-links]]`
+- **Don't assume** — if something is unclear, ask ONE simple question
+- **Use knowledge context** — search the knowledge base for mentioned entities,
+  then use `[[wiki-links]]`
 
-## Processing Flow
+## Process Flow
 
 ### Step 1: Find the Document
 
-Search thoroughly before saying a document doesn't exist:
+Search thoroughly before you say a document doesn't exist:
 
 ```bash
-rg -l -i "roadmap" Knowledge/
-find Knowledge/ -iname "*roadmap*" 2>/dev/null
+rg -l -i "roadmap" [0-9]-*/
+find [0-9]-*/ -iname "*roadmap*" 2>/dev/null
 ```
 
-**If found:** Read it and proceed. **If NOT found:** Ask "I couldn't find
+**If found:** Read it. Then proceed. **If NOT found:** Ask "I couldn't find
 [name]. Shall I create it?"
 
-**Creating new documents:**
+**Create a new document:**
 
-1. Ask: "Shall I create Knowledge/[name].md?"
-2. Create with just a title — don't pre-populate with structure
+1. Ask: "Shall I create 0-Draft/[name].md?"
+2. Create it with just a title. Don't pre-populate it with structure
 3. Ask: "What would you like in this?"
 
 ### Step 2: Understand the Request
 
-**NEVER make unsolicited edits.** If the user hasn't specified what to change,
-ask: "What would you like to change?"
+**NEVER make unsolicited edits.** If the user did not say what to change, ask:
+"What would you like to change?"
 
 Types of requests:
 
@@ -83,8 +88,8 @@ Types of requests:
 
 ### Step 3: Execute Changes
 
-Make targeted edits — change only what's needed. Preserve the user's voice and
-don't reorganize unless asked.
+Make targeted edits. Change only what's needed. Preserve the user's voice. Don't
+reorganize unless the user asks.
 
 ### Step 4: Confirm and Continue
 
@@ -92,14 +97,14 @@ don't reorganize unless asked.
 - Ask: "What's next?"
 - Don't read back the entire document unless asked
 
-## Searching Knowledge for Context
+## Search the Graph for Context
 
 When the user mentions people, companies, or projects:
 
 ```bash
-rg -l "Name" Knowledge/
-cat "Knowledge/People/Person.md"
-cat "Knowledge/Organizations/Company.md"
+rg -l "Name" [0-9]-*/
+cat "3-Team/People/Person.md"
+cat "3-Team/Organizations/Company.md"
 ```
 
 Use `[[wiki-links]]` to connect to other notes. Only link to notes that exist.
@@ -107,6 +112,6 @@ Use `[[wiki-links]]` to connect to other notes. Only link to notes that exist.
 ## Constraints
 
 - Match the user's tone and style
-- Make surgical edits — change only what's needed
-- Preserve the user's voice — don't reorganize unless asked
-- Only link to notes that exist — use `[[Person Name]]` for existing notes
+- Make surgical edits that change only what's needed
+- Preserve the user's voice, and don't reorganize unless the user asks
+- Only link to notes that exist, and use `[[Person Name]]` for existing notes