naive-framework 0.0.0-stage → 0.2.0

package/purpose/frameworks/business-discovery-framework.md

@@ -0,0 +1,326 @@
+---
+type: framework
+ai-model: none
+source: human
+created: 2026-05-19T05:11:51Z
+tags: [methodology, consultancy, discovery, intake, framework, conversation, business-understanding]
+related-entities:
+  - "a project note"
+  - "[[everything-ecosystem]]"
+related-checklists:
+  - "[[vault-and-tooling-consultancy-setup]]"
+status: living-document
+---
+
+# Business Discovery Framework
+
+A conversation framework for understanding another operator's business comprehensively enough to build their vault and systems on top of it. Industry-agnostic structure with industry-specific addenda.
+
+This is the tool the consultant opens during a discovery / intake session. It is *not a script*. It's a structure that ensures the conversation surfaces what needs to be surfaced.
+
+---
+
+## When to use this
+
+- First in-depth session with a new operator
+- Re-engagement with an existing operator after a major business change
+- Diagnostic when an existing operator feels stuck and isn't sure why
+
+## How to use it
+
+- **Open this doc and the checklist** (`vault-and-tooling-consultancy-setup.md`) side-by-side at the start of the session
+- **Run the layers in order** for a first session; you can jump between layers in later sessions
+- **Take notes directly in the operator's vault** — they see capture happening; this enacts the data sovereignty principle
+- **Use their own words** wherever possible; don't translate to methodology vocabulary in real-time
+- **Don't fill silences too quickly** — operators often surface the most useful answers when given thinking room
+
+Expect 60-120 minutes for a first session covering all 7 layers. If you have less time, prioritize Layers 1, 3, 4, and 7.
+
+---
+
+## The seven layers
+
+### Layer 1 — The Vivid Present
+
+**Purpose**: get the operator talking comfortably; surface ops, customers, tools, time-use, energy, frustrations, and joys in one pass.
+
+**Magic prompt**: *"Walk me through what a typical Tuesday looks like — from when you wake up until you stop working."*
+
+**Follow-on prompts**:
+- "Walk me through what happens when a new client first contacts you — from their first message to their first visit."
+- "What's the most recent thing you did for the business, in the last 24 hours?"
+- "What did this week look like? Last week?"
+
+**What to listen for**: tools mentioned in passing, time of day they work, energy peaks/valleys, who else is involved, recurring frustrations they don't even name as frustrations.
+
+### Layer 2 — The Full Surface
+
+**Purpose**: factual picture of the business — what, who, when, where, how much, with whom.
+
+**Prompts**:
+
+- **What** — "What services do you offer, and what does each one cost?"
+- **Who** — "How many active clients do you have right now? How many are recurring?"
+- **When** — "What does your schedule look like? Are there busy days/seasons?"
+- **Where** — "What geography do you serve? How far do you travel? Do you have a physical location?"
+- **How much** — "Roughly, what's a good month vs. a tough month?" (only if comfortable — calibrate to relationship)
+- **With whom** — "Are you the only person doing this, or do you have help? Contractors? Partners?"
+
+**Optional deeper cuts**:
+- "What's your client mix — long-term recurring, one-time, mix?"
+- "How do new clients usually find you?"
+- "What's your booking lead time — same-day, week ahead, month ahead?"
+
+**What to listen for**: revenue model (recurring vs. transactional), capacity constraints (solo vs. team), geographic scope, customer acquisition channels.
+
+### Layer 3 — The Pain & Friction
+
+**Purpose**: surface where the vault + methodology will deliver immediate value. Pain points point to where to build first.
+
+**Prompts**:
+
+- "What part of the business takes way more time than it should?"
+- "What's something that keeps slipping through the cracks?"
+- "If you could wave a wand and eliminate one part of your job, what would it be?"
+- "Tell me about the last time something went wrong — a missed visit, a billing issue, a lost client. What happened?"
+- "What's the Sunday-night feeling about the week ahead?" *(emotional temperature check)*
+- "What part of running the business do you dread?"
+
+**What to listen for**: repeated manual tasks (automation candidates), forgotten/dropped things (capture-system candidates), high-stakes errors (process candidates), emotional weight (coaching candidates).
+
+### Layer 4 — The Dreams (apply BASED)
+
+**Purpose**: surface the operator's actual ambition, uncensored. This is the Phase 0C work — refuse premature narrowing.
+
+**Prompts** (deploy progressively):
+
+- "If you could design the business of your dreams, with zero constraints on money, time, or possibility — what does it look like in five years?"
+- "What would make you say 'I made it'?"
+- "What's the most ambitious version of this you've ever imagined, even if you've never said it out loud?"
+- "If a customer wrote you a review you'd love to receive — what does it say?"
+- "What would you build if you knew you couldn't fail?"
+
+**Watch for self-censorship cues**:
+
+| Cue | What it usually means | Gentle redirect |
+|---|---|---|
+| "I just want to..." | Pre-narrowed | "What if 'just' wasn't a limit — what would you actually want?" |
+| "Realistically..." | Pre-narrowing | "Set realism aside for a sec — what's the dream?" |
+| "I don't know if I could..." | Premature humility | "If you could, what would it be?" |
+| "That's probably too..." | Premature dismissal | "Say it anyway — let's see what it sounds like." |
+| "But the market is..." | Pre-defensiveness | "Forget the market for a moment — what's the version of this you'd build for yourself?" |
+
+**Apply each BASED letter as a check on what you hear**:
+
+- **Broad** — is the aperture as wide as it could be?
+- **Audacious** — would they be willing to say this in public?
+- **Silly** — is there a playful / Willy-Wonka-tier vivid version of this?
+- **Egotistical** — are they willing to put themselves at the center?
+- **Delusional** — are they refusing current evidence long enough to imagine what isn't yet?
+
+**Note**: don't say "BASED" or explain the framework to the operator. You're applying it as the consultant; the operator just sees you asking thoughtful, generative questions.
+
+### Layer 5 — The Gap
+
+**Purpose**: surface what's between today (Layer 1-2) and the dream (Layer 4).
+
+**Prompts**:
+
+- "What's standing between you and that dream version of the business?"
+- "What's one thing that, if solved, would make the biggest difference?"
+- "Is the bottleneck time, money, knowledge, energy, people, or something else?"
+- "What have you tried that didn't work?"
+- "What do you wish you knew that you don't?"
+
+**What to listen for**: the *specific* shape of the bottleneck. "I need more clients" is vague; "I lose every Friday to billing reconciliation" is specific. Specificity is the substrate of action.
+
+### Layer 6 — The Next Step
+
+**Purpose**: identify the smallest immediate action that moves the needle, so the operator walks away with momentum, not just structure.
+
+**Prompts**:
+
+- "If we did ONE thing today that would make this week better, what would it be?"
+- "What's a small win that would feel disproportionately good?"
+- "What's something you've been meaning to do but haven't gotten around to?"
+- "What's the smallest version of the dream we could start on today?"
+
+This conversation produces **the first planned session** for the operator's vault — concrete, scoped, actionable.
+
+### Layer 7 — Tooling Inventory
+
+**Purpose**: groundwork for connector setup; understand what already exists vs. what needs to be built.
+
+**Prompts**:
+
+- "Walk me through every tool, app, or piece of software you use for the business."
+- "Where do client records live? Schedules? Payments? Photos? Communications?"
+- "Phone setup — separate business line, or personal?"
+- "How do you take payment?"
+- "Business email? Social accounts? Website?"
+- "What tools do you wish you used but haven't set up?"
+
+**Categories to walk through systematically**:
+- Scheduling / calendar
+- Client intake / forms
+- Client database / CRM
+- Payment processing
+- Accounting / bookkeeping
+- Tax preparation
+- Communications (email, SMS, social DMs)
+- Photo / file storage
+- Marketing (social, email lists, ads)
+- Supplier portals / inventory
+- Insurance / licensing portals
+- Banking
+- Domain / website / hosting
+
+For each tool, capture: what's used, who else has access, what data lives there, whether they're happy with it. This feeds Phase 5 of the consultancy checklist (external tool connections).
+
+---
+
+## Capture protocol
+
+During the session:
+
+1. **Open her vault. Create a new file**: `_sessions/raw/<date>-discovery-session.md`
+2. **Take notes there in real time**, in her own words
+3. **Don't pre-categorize** — capture raw; organize later
+4. **Use timestamps** for major shifts in topic (helpful when reviewing)
+5. **Don't try to be comprehensive in-line** — flag for follow-up rather than chasing every thread
+
+After the conversation, take a 10-15 minute break and synthesize:
+
+- Pull observations into the entity-profile draft
+- Pull ideas into `_ideas/`
+- Pull next-steps into `_sessions/planned/`
+- Pull dreams into a draft VISION_SPEC
+
+---
+
+## Output artifacts by end of session
+
+By the time the operator leaves the first session, her vault should contain:
+
+- [ ] **`entity-profile.md`** for the business (concept or scoped stage)
+- [ ] **3-5 idea notes** in `_ideas/` (captured from Layers 3, 4, 5)
+- [ ] **1-2 planned sessions** in `_sessions/planned/` (from Layer 6)
+- [ ] **Session-log entry** for today's discovery session
+- [ ] **VISION_SPEC draft** (rough — Phase 0C output from Layer 4)
+- [ ] **Tooling inventory note** at `_meta/tooling-inventory.md`
+- [ ] **Pain points / friction note** for prioritization
+- [ ] **`code-pointer.md` placeholder** if any tech work will follow
+
+The vault should feel *populated*, not empty. She should be able to open it and see her business reflected back.
+
+---
+
+## Industry-specific addenda
+
+### Pet-care / pet-sitting (tomorrow's friend)
+
+Specific questions to surface pet-care nuance:
+
+- **Pet types served** — dogs only? Cats? Exotic (reptiles, birds, fish)? Special needs?
+- **Service types** — boarding, drop-in visits, dog walks, overnight stays, transport, training, grooming?
+- **Visit cadence** — daily for some clients? Weekly? Ad-hoc?
+- **Key handoff protocol** — does she hold keys, use lockboxes, smart locks?
+- **Insurance + bonding** — Pet Sitters International? Local liability? Bonded for key-holding?
+- **Vet partnerships** — does she have go-to vets for emergencies? Referral relationships?
+- **Emergency protocols** — what happens when a pet gets injured / loose / sick during her visit?
+- **Vehicle / travel** — does she travel between clients? Mileage tracked? Vehicle insured commercially?
+- **Equipment owned** — leashes, treats, first aid, transport carriers, cleanup supplies?
+- **Background check / certifications** — pet CPR? Pet first aid? Background check for client trust?
+- **Pet info storage** — where do allergy / medication / behavior / vet info live today?
+- **Photo / update protocol** — does she send daily photos? Update clients in real-time?
+- **Pricing structure** — per-visit, per-day, monthly package, sliding by service?
+- **Geographic radius** — how far does she travel? Strict limits?
+- **Seasonal patterns** — summer/holiday peaks? Slow seasons?
+
+### Restaurant / food-service (future)
+
+- Menu and recipe versioning
+- Vendor / supplier relationships
+- Health code / food safety
+- Shift scheduling
+- POS integration
+- Liquor license / age verification
+
+### Solo consulting (future)
+
+- Service offerings / packaging
+- Client intake / contracts
+- Time tracking / invoicing
+- Knowledge management *is* the product
+
+### E-commerce / D2C (future)
+
+- Product catalog
+- Inventory
+- Fulfillment
+- Customer support
+
+### Software / SaaS (future)
+
+- Existing SAD applies directly
+- Code repo, CI/CD, deploy
+- Customer onboarding flows
+
+---
+
+## Anti-patterns
+
+Things to avoid during the discovery session:
+
+- **Don't lead with the methodology.** Lead with her business. The methodology is invisible scaffolding.
+- **Don't translate her vocabulary to yours.** Capture in her language; harmonize later.
+- **Don't fill silences too quickly.** The best answers come after a pause.
+- **Don't make it feel like an interview or audit.** This is a generative conversation.
+- **Don't commit to building anything mid-session.** Capture, decide between sessions.
+- **Don't pre-narrow her BASED ambition** with "well, realistically..."
+- **Don't pretend you have answers you don't have.** "I don't know — let's figure it out" is a strong consultant move.
+- **Don't try to cover all 7 layers if it's killing the energy.** A great Layer 1-4 + Layer 7 is better than a forced full pass.
+- **Don't tell her the Wonka story today.** The brand isn't ready; the methodology is doing the work.
+
+---
+
+## Variations by operator type
+
+| Operator type | Adjustments |
+|---|---|
+| **Solo founder** | All layers as-is |
+| **Team-based** | Add: "Walk me through your team — roles, who does what, who you trust with what." |
+| **Service business** | Standard framework applies |
+| **Product business** | Layer 2 emphasis on inventory / catalog / fulfillment |
+| **Pre-launch** | Layer 1 → "what does a typical week look like *now*, even though the business isn't started yet?" |
+| **Running business** | Standard framework |
+| **Local** | Layer 2: emphasis on geographic constraints and community |
+| **Online / national** | Layer 2: emphasis on channel mix and customer acquisition |
+
+---
+
+## Pre-session prep (30 minutes before)
+
+A quick prep ritual before the session:
+
+- [ ] Open this framework + the consultancy checklist
+- [ ] Confirm her machine has Obsidian (or be ready to install)
+- [ ] Confirm Claude Code / Cowork is reachable
+- [ ] Have a notebook ready (in case her vault isn't accessible at start)
+- [ ] Hydrate; restroom
+- [ ] Set time expectation with her ("This will probably take 2-3 hours; let me know when you need breaks")
+- [ ] Note your own energy — discovery work is dense; pace matters
+- [ ] Make sure no other Claude session has heavy state competing for your attention
+
+---
+
+## After-session protocol
+
+Within 24 hours of the discovery session:
+
+- [ ] Synthesize the raw session notes into the artifacts listed in *Output artifacts*
+- [ ] Send her the entity-profile draft + VISION_SPEC draft for review
+- [ ] Schedule the follow-up session (this is when actual setup work happens)
+- [ ] Add your own retrospective notes to `a consulting practice/_ideas/`: what worked, what didn't, what's missing from this framework
+
+The framework gets better every time you use it. Refine.

package/purpose/frameworks/idea-map/README.md

@@ -0,0 +1,74 @@
+---
+type: framework
+source: hybrid
+created: 2026-10-28T19:44:02Z
+ai-model: claude-opus-5.5
+tags: [everything-ecosystem, purpose, idea-map, idea-graph, routing, kanban, typesafe, jev]
+description: "From an idea dump to next steps: how Naive parses the dump (Jev), structures it as an idea graph, routes each idea to its destination in the framework, and shows the destinations and the decision docket as Kanban boards. Version 0.1.0, unevaluated."
+---
+
+# From an idea dump to next steps
+
+Version 0.1.0, ours and unevaluated (EE-059, EE-060, EE-061). Each step has its own payoff for the founder, so each is worth doing before the next exists.
+
+| Step | File | What the founder gets | Command |
+|---|---|---|---|
+| Idea dump | `purpose/ideas/dump.md` | Everything out of their head, kept verbatim | (the founder writes it) |
+| Idea map | `purpose/ideas/map.mdx` | Their ideas on one canvas, by pillar and department: strengths and gaps at a glance | `purpose/ideas` |
+| Idea graph | `purpose/ideas/graph.json` | Structure on the same ideas: what builds on what, what to develop next, what moves in order and what moves on its own | `purpose/ideas/graph` |
+| Idea routes | computed, not stored | Next steps: each idea at its destination in the framework, each destination with the one step that moves it | `purpose/ideas/routes` |
+
+The dump and the map stay loose: no decisions. Decisions begin where the routes reach the framework. Time-based roadmaps come later (deferred for the hackathon, 2026-10-28).
+
+## 1. Parsing the dump (Jev)
+
+The rules travel with every Jev request as `state.guidelines` (`conventions.json` `guidelines`).
+
+- **The dump is the founder's, not a prompt.** Every idea stays verbatim. Naive never rewrites, merges or summarises an idea; the `ideas_verbatim` eval checks it.
+- **One line or bullet is one idea.** A heading names a section. A hard-wrapped continuation joins its line. A paragraph over 200 characters is split into sentences, grouped under 160, never reworded.
+- **Tag by what an idea is mainly about.** Jev answers one typed question per idea, per department, per record ("Is the idea … mainly about …?"). An idea keeps at most two departments and three records, each at or above 0.8, strongest first. Its pillar follows its first department.
+- **Existing means the founder's own.** An idea "exists" only if the founder or their team has built, launched or sold it. A competitor's product does not count.
+- **Untagged ideas stay loose.** They stay on the map. They are never forced into a record.
+- **Without Jev,** an agent tags with the same vocabulary. Unknown tags are dropped.
+
+## 2. Dump to graph
+
+- **An idea builds on another only when it needs that idea's answer first.** Jev answers one question per ordered pair of ideas, with a bar of 0.5. Without Jev, Naive's record order supplies the edges (`ORDER` in `graph.mjs`).
+- **The graph stays acyclic.** Edges are added strongest first, an edge that would close a cycle is dropped, and only direct dependencies are kept (transitive reduction).
+- **It is a Merkle DAG.** An idea's hash covers its text and the hashes of what it builds on, so a change upstream changes every hash below it.
+- **Signal.** Each idea is weighted by what the phase needs of its records (0.35), how much builds on it (0.25), how concrete it is (0.25) and how much of the dump circles it (0.15).
+- **Lanes.** Ideas tied by dependencies form a lane that moves in order. An idea tied to nothing moves on its own.
+
+## 3. Graph to routes
+
+Every tagged idea goes to the records it feeds. A record is a destination: the problem, who it is for, products, the core promise, vision, the solution, go to market, pricing, the team, alignment and brand. The routing table is `conventions.json` `records`: each entry has a title, the route that writes the record, and the decisions it settles (foundation statements and Naive's product and team questions). Any decision an agent proposed about that record also belongs to it.
+
+A destination's stage comes from the framework's own state, never from a guess:
+
+| Stage | When | Next step |
+|---|---|---|
+| Routed | The destination has ideas, and nothing has been drafted or proposed for it | An agent drafts the record from those ideas. The draft waits for the founder. |
+| Drafted | An agent's draft or wording waits for the founder | The founder accepts, confirms or approves it (about a minute) |
+| Your decision | A decision only a person can make, with no draft | The founder decides, in their own words |
+| Waiting | Another decision holds it, or its phase has not come | Nothing until the holder settles |
+| Done | The record is written and nothing about it is open | None |
+
+A destination moves **in order** when it sits on the fail-closed path or its ideas share a lane that builds in order. Its number is its place in Naive's record order. It moves **on its own** when its decisions fail open (the team question) or its ideas stand alone.
+
+## 4. Routes to the decision docket
+
+The docket is every open decision, staged the same way and ranked as before (EE-057).
+
+- **Traced to ideas.** Each decision traces back to the ideas it comes from: its own `ideas` field (decision records, EE-061), the `i-NN` ids its question and answer cite, or else its destination's ideas.
+- **Agent proposals must carry `ideas`.** The `decisions_traced` eval checks that every agent proposal cites ideas that exist.
+
+## The boards
+
+`node interface/demo/board.mjs` serves four pages:
+
+- `/map`: the idea map;
+- `/graph`: the idea graph;
+- `/kanban`: the destinations and the docket as Kanban boards;
+- `/`: the decision board.
+
+The map and the graph use React Flow, because their value is structure on a canvas. The Kanban boards are plain columns: a board is a list per stage, and dragging a card would bypass the framework, since cards move only when the founder or an agent does the step.

package/purpose/frameworks/idea-map/conventions.json

@@ -0,0 +1,146 @@
+{
+  "version": "0.1.0",
+  "note": "The tags an idea map uses (EE-059): Naive's own conventions, never free-form labels. Each idea in a founder's idea dump is tagged with the departments it bears on (operations/departments.json, APQC with Porter's value chain), the records it feeds (schema/data-model.json), and whether it describes something that already exists. Its pillar follows from its first department. Each idea keeps at most max.departments departments and max.records records, strongest first, at or above the threshold. Version 0.x, ours and unevaluated.",
+  "threshold": 0.8,
+  "pillars": {
+    "product": [
+      "products",
+      "it",
+      "service-delivery",
+      "supply-chain"
+    ],
+    "brand": [
+      "marketing-and-sales",
+      "customer-service",
+      "external-relationships"
+    ],
+    "business": [
+      "strategy",
+      "finance",
+      "human-capital",
+      "assets",
+      "risk-and-compliance",
+      "capabilities"
+    ]
+  },
+  "departments": {
+    "strategy": "the venture's direction, vision, positioning against competitors, or what to do first",
+    "products": "designing, building or improving a product, feature or service the venture offers",
+    "marketing-and-sales": "reaching, persuading or selling to customers: channels, content, campaigns, launches, sales",
+    "supply-chain": "sourcing, making or moving physical goods",
+    "service-delivery": "delivering a service to customers day to day",
+    "customer-service": "supporting, onboarding or keeping customers after they buy",
+    "human-capital": "people: cofounders, hiring, roles, culture, the founder's own development",
+    "it": "the technology, data, infrastructure, integrations or AI the venture runs on",
+    "finance": "money: pricing, revenue, costs, funding, investors",
+    "assets": "property, equipment or other assets the venture buys or owns",
+    "risk-and-compliance": "legal, regulatory, privacy, security or other risks",
+    "external-relationships": "partners, community, investors relations, the public or government",
+    "capabilities": "how the venture improves itself: processes, knowledge, quality, measurement"
+  },
+  "records": {
+    "validation-problem": {
+      "title": "The problem",
+      "route": "purpose/validation/problem",
+      "about": "a problem or pain that people have",
+      "decisions": [
+        "foundation-problem"
+      ]
+    },
+    "icp": {
+      "title": "Who it is for",
+      "route": "purpose/icp",
+      "about": "who the customer, user or audience is",
+      "decisions": [
+        "foundation-icp"
+      ]
+    },
+    "product": {
+      "title": "Products",
+      "route": "purpose/product",
+      "about": "a specific product, feature or offering",
+      "decisions": [
+        "foundation-products",
+        "product-exists",
+        "flagship",
+        "foundation-business-models",
+        "foundation-markets"
+      ]
+    },
+    "venture-core": {
+      "title": "The core promise",
+      "route": "venture.json core",
+      "about": "the venture's core promise, who it is promised to, or the competence that makes it deliverable",
+      "decisions": [
+        "core-product",
+        "foundation-mission",
+        "foundation-promised-to",
+        "foundation-competence"
+      ]
+    },
+    "telos": {
+      "title": "Vision",
+      "route": "purpose/telos",
+      "about": "the long-run vision, end state, ambition or exit",
+      "decisions": [
+        "foundation-vision",
+        "foundation-exit-criteria"
+      ]
+    },
+    "validation-solution": {
+      "title": "The solution",
+      "route": "purpose/validation/solution",
+      "about": "how a problem would be solved",
+      "decisions": []
+    },
+    "validation-go-to-market": {
+      "title": "Go to market",
+      "route": "purpose/validation/go-to-market",
+      "about": "how the venture would reach and win its first customers",
+      "decisions": [
+        "foundation-channels"
+      ]
+    },
+    "validation-pricing": {
+      "title": "Pricing",
+      "route": "purpose/validation/pricing",
+      "about": "a price, a business model or how the venture makes money",
+      "decisions": []
+    },
+    "validation-team": {
+      "title": "The team",
+      "route": "purpose/validation/team",
+      "about": "who would build or run the venture",
+      "decisions": [
+        "founding-team"
+      ]
+    },
+    "alignment": {
+      "title": "Alignment",
+      "route": "purpose/alignment",
+      "about": "principles, values, or what the venture must never do",
+      "decisions": [
+        "foundation-alignment"
+      ]
+    },
+    "brand": {
+      "title": "Brand",
+      "route": "venture.json brand",
+      "about": "the venture's name, tagline, story or look",
+      "decisions": [
+        "foundation-tagline"
+      ]
+    }
+  },
+  "exists": "the founder (or their team) has already built, launched or sold this product, prototype or pilot themselves; a competitor's product does not count",
+  "max": {
+    "departments": 2,
+    "records": 3
+  },
+  "guidelines": {
+    "dump": "The idea dump is the founder's, not a prompt: every idea stays verbatim. One line or bullet is one idea; a heading names a section; a long paragraph is split into sentences, never rewritten.",
+    "tags": "Tag an idea with what it is mainly about, not everything it touches: at most two departments and three records, each at or above the threshold. An idea about a competitor is not an existing product. An idea with no tag stays on the map, loose; it is never forced into a record.",
+    "graph": "An idea builds on another only when it needs that idea's answer first. Dependencies are kept acyclic, strongest first, and reduced to the direct ones. Ideas tied by dependencies form a lane that moves in order; an idea with no tie moves on its own.",
+    "routes": "Each tagged idea is routed to the records it feeds, the framework's destinations. A destination's stage comes from the framework's own state: routed (ideas, nothing drafted), drafted (an agent's draft awaits the founder), yours (a decision only a person can make), waiting (held by another decision), done. The next step is the framework's, never invented."
+  }
+}