factoryhub 0.0.0-stage → 0.1.0

package/factories/index.json

@@ -0,0 +1,356 @@
+{
+  "format": "factoryhub.index/v1",
+  "note": "Generated by scripts/generate.mjs from factories/. Do not edit.",
+  "factories": [
+    {
+      "id": "client-file-readiness",
+      "title": "Client-file readiness",
+      "description": "Compares what a client sent against your checklist, reports what is missing, from the wrong period or unclear, and drafts the message asking for it. Use before starting bookkeeping, tax, audit, onboarding or any work that depends on a client's documents.",
+      "version": "1.1.0",
+      "license": "MIT",
+      "author": "Mindburn Labs",
+      "tags": [
+        "operations",
+        "accounting"
+      ],
+      "time": "about 2 minutes",
+      "path": "factories/client-file-readiness",
+      "sha256": "28d5c6dde74137686fd2a77a73b1f7b1947604e009f3f17359d6032072ff133c",
+      "runnable": true,
+      "inputs": [
+        {
+          "key": "checklist",
+          "type": "longtext",
+          "required": true
+        },
+        {
+          "key": "received",
+          "type": "longtext",
+          "required": true
+        },
+        {
+          "key": "client_and_period",
+          "type": "text",
+          "required": true
+        },
+        {
+          "key": "deadline",
+          "type": "text",
+          "required": false
+        }
+      ],
+      "steps": 3,
+      "decision": false,
+      "agents": [
+        "analyst",
+        "reviewer",
+        "writer"
+      ],
+      "tools": []
+    },
+    {
+      "id": "competitor-teardown",
+      "title": "Competitor teardown",
+      "description": "Reads your website and up to three competitors, then writes a decision-ready brief showing where you win, where you lose and what to change this week. Use before a pricing change, a homepage rewrite or a sales call.",
+      "version": "1.1.0",
+      "license": "MIT",
+      "author": "Mindburn Labs",
+      "tags": [
+        "marketing",
+        "research"
+      ],
+      "time": "about 4 minutes",
+      "path": "factories/competitor-teardown",
+      "sha256": "b46c7fa922a24b4ed144643be1d792d22f2a7b94374be705bd96b5818f9b6fae",
+      "runnable": true,
+      "inputs": [
+        {
+          "key": "your_site",
+          "type": "url",
+          "required": true
+        },
+        {
+          "key": "competitors",
+          "type": "longtext",
+          "required": true
+        },
+        {
+          "key": "focus",
+          "type": "text",
+          "required": false
+        }
+      ],
+      "steps": 5,
+      "decision": false,
+      "agents": [
+        "analyst",
+        "researcher",
+        "reviewer",
+        "writer"
+      ],
+      "tools": [
+        "web_fetch",
+        "web_search"
+      ]
+    },
+    {
+      "id": "homepage-audit",
+      "title": "Homepage audit with fixes",
+      "description": "Reads your home page the way a first-time visitor does and returns a prioritised list of fixes with the exact new wording. Use when signups or enquiries are lower than the traffic deserves.",
+      "version": "1.2.0",
+      "license": "MIT",
+      "author": "Mindburn Labs",
+      "tags": [
+        "marketing",
+        "website"
+      ],
+      "time": "about 3 minutes",
+      "path": "factories/homepage-audit",
+      "sha256": "1b882f4e96758d6e15dac308d3f517bc927150d0d8f8b988cedefd616e1413c8",
+      "runnable": true,
+      "inputs": [
+        {
+          "key": "site",
+          "type": "url",
+          "required": true
+        },
+        {
+          "key": "goal",
+          "type": "text",
+          "required": false
+        },
+        {
+          "key": "audience",
+          "type": "text",
+          "required": false
+        }
+      ],
+      "steps": 4,
+      "decision": false,
+      "agents": [
+        "analyst",
+        "researcher",
+        "reviewer",
+        "writer"
+      ],
+      "tools": [
+        "web_fetch"
+      ]
+    },
+    {
+      "id": "inbox-triage",
+      "title": "Support inbox triage",
+      "description": "Sorts a batch of customer messages by urgency and type, drafts a reply to each in your tone, and lists what needs a human decision. Use on a support or shared inbox that has piled up.",
+      "version": "1.1.0",
+      "license": "MIT",
+      "author": "Mindburn Labs",
+      "tags": [
+        "support",
+        "operations"
+      ],
+      "time": "about 2 minutes",
+      "path": "factories/inbox-triage",
+      "sha256": "5b5f8ae0e022ca2b4cd53afef8dd0b40f936f0d95be23f872891e624818104b4",
+      "runnable": true,
+      "inputs": [
+        {
+          "key": "messages",
+          "type": "longtext",
+          "required": true
+        },
+        {
+          "key": "policies",
+          "type": "longtext",
+          "required": true
+        },
+        {
+          "key": "tone",
+          "type": "text",
+          "required": false
+        }
+      ],
+      "steps": 4,
+      "decision": false,
+      "agents": [
+        "analyst",
+        "reviewer",
+        "writer"
+      ],
+      "tools": []
+    },
+    {
+      "id": "launch-kit",
+      "title": "Launch kit",
+      "description": "Turns a product description into a launch kit with positioning, a landing page draft, a launch email, three follow-ups and posts for social channels, all in one voice. Use when you have something to launch and no time to write.",
+      "version": "1.2.0",
+      "license": "MIT",
+      "author": "Mindburn Labs",
+      "tags": [
+        "marketing",
+        "launch"
+      ],
+      "time": "about 4 minutes",
+      "path": "factories/launch-kit",
+      "sha256": "80c4b2afad0bbd4a21bda4af3bb98ab29b429aaa03551d1af3fe92f7645f1c10",
+      "runnable": true,
+      "inputs": [
+        {
+          "key": "product",
+          "type": "longtext",
+          "required": true
+        },
+        {
+          "key": "audience",
+          "type": "text",
+          "required": true
+        },
+        {
+          "key": "site",
+          "type": "url",
+          "required": false
+        },
+        {
+          "key": "launch_offer",
+          "type": "text",
+          "required": false
+        },
+        {
+          "key": "market_research",
+          "type": "longtext",
+          "required": false
+        }
+      ],
+      "steps": 6,
+      "decision": true,
+      "agents": [
+        "reviewer",
+        "strategist",
+        "writer"
+      ],
+      "tools": [
+        "web_fetch"
+      ]
+    },
+    {
+      "id": "meeting-to-actions",
+      "title": "Meeting to actions",
+      "description": "Turns rough meeting notes or a transcript into decisions, owned actions with dates, open questions and a follow-up message ready to send. Use right after any meeting where things were agreed.",
+      "version": "1.1.1",
+      "license": "MIT",
+      "author": "Mindburn Labs",
+      "tags": [
+        "operations",
+        "productivity"
+      ],
+      "time": "about 1 minute",
+      "path": "factories/meeting-to-actions",
+      "sha256": "7da2afff80e089d1d7ca1bab70907cc85d4d88454e62744d252d87441ed3d34f",
+      "runnable": true,
+      "inputs": [
+        {
+          "key": "notes",
+          "type": "longtext",
+          "required": true
+        },
+        {
+          "key": "context",
+          "type": "text",
+          "required": false
+        }
+      ],
+      "steps": 3,
+      "decision": false,
+      "agents": [
+        "analyst",
+        "reviewer",
+        "writer"
+      ],
+      "tools": []
+    },
+    {
+      "id": "outreach-pack",
+      "title": "Outreach pack",
+      "description": "Turns checked market research and launch materials into an outreach pack. Use when the positioning is approved and you need messages to review and send yourself.",
+      "version": "1.0.0",
+      "license": "MIT",
+      "author": "Mindburn Labs",
+      "tags": [
+        "sales",
+        "launch"
+      ],
+      "time": "",
+      "path": "factories/outreach-pack",
+      "sha256": "a1ffe3ae4ef85477f378680a6b983bf92f22bd40790372a5cb84c26d73254a2f",
+      "runnable": true,
+      "inputs": [
+        {
+          "key": "research",
+          "type": "longtext",
+          "required": true
+        },
+        {
+          "key": "launch_materials",
+          "type": "longtext",
+          "required": true
+        },
+        {
+          "key": "contact_role",
+          "type": "text",
+          "required": false
+        }
+      ],
+      "steps": 3,
+      "decision": false,
+      "agents": [
+        "reviewer",
+        "writer"
+      ],
+      "tools": []
+    },
+    {
+      "id": "prospect-brief",
+      "title": "Prospect brief and first email",
+      "description": "Researches one company you want to sell to and writes a one-page brief plus a first email and follow-up that mention real, checkable facts about them. Use before reaching out to an account that matters.",
+      "version": "1.1.0",
+      "license": "MIT",
+      "author": "Mindburn Labs",
+      "tags": [
+        "sales",
+        "research"
+      ],
+      "time": "about 4 minutes",
+      "path": "factories/prospect-brief",
+      "sha256": "77c1ee37106eca696283235ce81ff9dd7328a1ee26f37f877d4bc9c6506b5e3a",
+      "runnable": true,
+      "inputs": [
+        {
+          "key": "prospect",
+          "type": "url",
+          "required": true
+        },
+        {
+          "key": "what_you_sell",
+          "type": "longtext",
+          "required": true
+        },
+        {
+          "key": "contact_role",
+          "type": "text",
+          "required": false
+        }
+      ],
+      "steps": 7,
+      "decision": true,
+      "agents": [
+        "researcher",
+        "reviewer",
+        "strategist",
+        "writer"
+      ],
+      "tools": [
+        "web_fetch",
+        "web_search"
+      ]
+    }
+  ]
+}

package/factories/launch-kit/README.md

@@ -0,0 +1,3 @@
+# Launch kit
+
+Describe what you are launching and who it is for. You agree the positioning once, then get every piece of launch writing built on it: the page, the emails and the posts. It only uses facts you gave, so nothing needs to be un-promised later.

package/factories/launch-kit/agents/reviewer/agent.md

@@ -0,0 +1,10 @@
+---
+description: Checks work against stated criteria and sends weak work back.
+agentType: REVIEW
+---
+
+You are the reviewer. You hold one piece of work against the criteria you are given and decide whether it passes.
+
+- You judge only what is on the page and only against the stated criteria.
+- You fail work for a clear, specific breach you can point to. You never fail it for taste, or for something nobody asked for.
+- When you send work back, each reason is one concrete sentence the author can act on.

package/factories/launch-kit/agents/strategist/agent.md

@@ -0,0 +1,10 @@
+---
+description: Chooses the angle: what to say, to whom, and why it should work.
+agentType: CUSTOM
+---
+
+You are the strategist. From the facts in hand you choose the angle: who this is for, what to promise, and which facts make it believable.
+
+- You offer a clear first choice and real alternatives, and you say which facts you are least sure of.
+- You use only facts from the inputs and earlier steps. A stronger claim that the facts do not support is not an option.
+- The person decides. You make their decision easy to take.

package/factories/launch-kit/agents/writer/agent.md

@@ -0,0 +1,11 @@
+---
+description: Writes the finished words the person will use or send.
+agentType: CUSTOM
+---
+
+You are the writer. You write the finished thing the person will use: the brief, the message, the page, the report.
+
+- Plain words, short sentences, the reader's own vocabulary. No filler and no hype.
+- You keep to the sections, word limits and order the step asks for.
+- You add no fact that is not in the inputs or earlier results. Where a real asset or decision is missing, you mark the gap clearly instead of inventing it.
+- What you write should be usable as it stands.

package/factories/launch-kit/factory.yaml

@@ -0,0 +1,12 @@
+schemaVersion: v1alpha1
+name: launch-kit
+description: |
+  Turns a product description into a launch kit with positioning, a landing
+  page draft, a launch email, three follow-ups and posts for social channels,
+  all in one voice. Use when you have something to launch and no time to
+  write.
+repositories: []
+agentDefaults:
+  harness:
+    type: claude
+    model: sonnet

package/factories/launch-kit/flow.yaml

@@ -0,0 +1,75 @@
+flow: mindburn.flow/v1
+title: Launch kit
+author: Mindburn Labs
+version: "1.2.0"
+license: MIT
+tags: [marketing, launch]
+time: about 4 minutes
+inputs:
+  product:
+    type: longtext
+    help: "What you are launching, what it does, the price and anything true you can say about results or customers."
+  audience:
+    type: text
+    help: "Who it is for, as specifically as you can, for example \"freelance bookkeepers with 10 to 40 clients\"."
+  site:
+    type: url
+    optional: true
+    help: "Your current website, to match the voice."
+  launch_offer:
+    type: text
+    optional: true
+    help: "Any launch offer and its end condition, for example \"20% off for the first 50 customers\"."
+  market_research:
+    type: longtext
+    optional: true
+    help: "Source-linked market research to inform positioning. Keep product claims grounded in the product facts."
+steps:
+  positioning:
+    title: Find the positioning
+    agent: strategist
+    kind: work
+    tools: [web_fetch]
+    task: |
+      If market_research was given, use its sourced comparisons to explain differentiation without treating competitor facts as facts about this product. If a site was given, read its home page to learn the voice and existing claims. Then write the positioning: the audience and the moment they need this, the problem in their words, the promise in one sentence of under 15 words, three reasons to believe it (each tied to a fact from the product input), what it replaces, and the one objection most likely to stop a purchase with an honest answer. Offer two alternative promise sentences below the main one. Describe the voice in one line. Use no fact that is not in the inputs or on the site.
+  approve_positioning:
+    title: Agree the positioning
+    kind: approve
+    needs: [positioning]
+    shows: positioning
+    task: |
+      Everything else is written from this. Approve it, pick one of the alternative promises, or correct anything that is wrong about your product or audience.
+  landing_page:
+    title: Write the landing page
+    agent: writer
+    kind: work
+    needs: [approve_positioning]
+    task: |
+      Write the landing page from the approved positioning: headline (the promise), a line under it, the main button text, a "how it works" section with three steps, the three reasons to believe as short sections, the objection and its answer, the price and the launch offer if one was given, and a closing call to action. Mark every place where a real testimonial, screenshot or number should go as "[ADD: what belongs here]" instead of inventing one.
+  messages:
+    title: Write the emails and posts
+    agent: writer
+    kind: work
+    needs: [approve_positioning]
+    task: |
+      In the same voice write: a launch email under 180 words with two subject lines; three follow-up emails under 100 words each for days 2, 4 and 6, each making one new point (a reason to believe, the objection answered, the offer ending); and five short posts for social channels, each standing alone and each opening differently. State the launch offer exactly as given, with its end condition.
+  kit:
+    title: Package the kit
+    agent: writer
+    kind: deliver
+    needs: [landing_page, messages]
+    task: |
+      Assemble the kit in this order: **Positioning** (the approved version, one short block), **Landing page** (full draft), **Launch email**, **Follow-up emails** (with the day for each), **Posts**, and **Before you publish**: a checklist of every "[ADD: ...]" placeholder and any claim you should double-check, plus the order to publish the pieces in.
+  check_messages:
+    title: Check the kit
+    agent: reviewer
+    kind: check
+    needs: [kit]
+    checks: kit
+    task: |
+      Review every piece of the assembled kit, including the landing page. Every factual product, price, result, customer or offer claim is supported by the inputs or positioning. Every piece uses the approved promise and voice. No invented testimonial, number, customer name or deadline appears. The offer and end condition match the input. Requested word limits and section counts are met, and every missing asset remains marked and appears in the checklist.
+
+done:
+  - "Every piece uses the approved promise and the same voice."
+  - "No claim appears that the inputs do not support."
+  - "Every gap that needs a real asset is marked, not filled in."

package/factories/meeting-to-actions/CHANGELOG.md

@@ -0,0 +1,7 @@
+# Changes
+
+## 1.1.1
+
+Adds an executable example covering agreed actions, unanswered questions and
+missing owners or deadlines. Includes a model recommendation and a bounded
+short-input cost estimate. The workflow and its six output sections are unchanged.

package/factories/meeting-to-actions/README.md

@@ -0,0 +1,15 @@
+# Meeting to actions
+
+Paste the notes or transcript. You get what was decided, who does what by when, what is still open, and the follow-up message for everyone who was there. It only reports what the notes support, and it tells you where an owner or a date was never agreed.
+
+The included example uses invented notes with an agreed action, an unowned task
+and an undecided question. The result must keep those distinctions; drafting a
+follow-up does not send it. Read the result before sending it.
+
+Run the example on the Hub or with
+`node run.mjs --test --provider anthropic --model claude-haiku-5-5`. Passing text checks are
+a repeatable regression signal, not proof that every transcript will be handled
+correctly. The package includes the model recommendation and the basis of its
+short-input cost estimate; no minimum model has been established. Hosted trials
+used Haiku for writing and Sonnet for review. The local command uses Haiku for
+both, so its quality and cost must be checked separately.

package/factories/meeting-to-actions/agents/analyst/agent.md

@@ -0,0 +1,10 @@
+---
+description: Turns raw material into structured findings that can be checked.
+agentType: CUSTOM
+---
+
+You are the analyst. You take what the person gave and what earlier steps found, and turn it into structured findings: tables, ranked lists, statuses.
+
+- Every finding points at the exact words, file or fact it rests on.
+- You never assume what the material does not show. Where something cannot be told, you say what is missing.
+- You rank by what matters most to the person's goal, and you keep to the counts and shapes the step asks for.

package/factories/meeting-to-actions/agents/reviewer/agent.md

@@ -0,0 +1,10 @@
+---
+description: Checks work against stated criteria and sends weak work back.
+agentType: REVIEW
+---
+
+You are the reviewer. You hold one piece of work against the criteria you are given and decide whether it passes.
+
+- You judge only what is on the page and only against the stated criteria.
+- You fail work for a clear, specific breach you can point to. You never fail it for taste, or for something nobody asked for.
+- When you send work back, each reason is one concrete sentence the author can act on.

package/factories/meeting-to-actions/agents/writer/agent.md

@@ -0,0 +1,11 @@
+---
+description: Writes the finished words the person will use or send.
+agentType: CUSTOM
+---
+
+You are the writer. You write the finished thing the person will use: the brief, the message, the page, the report.
+
+- Plain words, short sentences, the reader's own vocabulary. No filler and no hype.
+- You keep to the sections, word limits and order the step asks for.
+- You add no fact that is not in the inputs or earlier results. Where a real asset or decision is missing, you mark the gap clearly instead of inventing it.
+- What you write should be usable as it stands.

package/factories/meeting-to-actions/factory.yaml

@@ -0,0 +1,11 @@
+schemaVersion: v1alpha1
+name: meeting-to-actions
+description: |
+  Turns rough meeting notes or a transcript into decisions, owned actions with
+  dates, open questions and a follow-up message ready to send. Use right after
+  any meeting where things were agreed.
+repositories: []
+agentDefaults:
+  harness:
+    type: claude
+    model: claude-haiku-5-5

package/factories/meeting-to-actions/flow.yaml

@@ -0,0 +1,53 @@
+flow: mindburn.flow/v1
+title: Meeting to actions
+author: Mindburn Labs
+version: "1.1.1"
+license: MIT
+tags: [operations, productivity]
+time: about 1 minute
+inputs:
+  notes:
+    type: longtext
+    help: "The meeting notes or transcript, as rough as they are."
+  context:
+    type: text
+    optional: true
+    help: "Who met and why, for example \"weekly call with the Halden client about the website launch\"."
+steps:
+  extraction:
+    title: Extract what was agreed
+    agent: analyst
+    kind: work
+    task: |
+      Read the notes and pull out four lists. Decisions: what was decided, in one sentence each. Actions: the task, the owner as named in the notes, and the due date as stated. Open questions: things raised and not settled. Risks: anything someone flagged as a worry.
+
+      Where an action has no owner or no date in the notes, write "owner not agreed" or "date not agreed": never assign one yourself. After each item put a short quote from the notes that supports it. Leave out small talk and anything said but not agreed.
+  followup:
+    title: Write the follow-up
+    agent: writer
+    kind: deliver
+    needs: [extraction]
+    task: |
+      Write the follow-up. Sections, in this order:
+
+      1. **Summary**: two sentences on what the meeting settled.
+      2. **Decisions**: a numbered list.
+      3. **Actions**: a table with columns Action, Owner, Due. Keep "not agreed" where it applies.
+      4. **Still open**: the open questions, and for each the person best placed to answer, if the notes say.
+      5. **To confirm**: every missing owner or date as a direct question.
+      6. **Message to send**: a follow-up message to the attendees under 150 words, covering decisions, actions and the questions to confirm, ready to paste into email or chat.
+
+      Do not include the supporting quotes in the follow-up.
+  check_extraction:
+    title: Check against the notes
+    agent: reviewer
+    kind: check
+    needs: [followup]
+    checks: followup
+    task: |
+      Compare the entire follow-up with the original notes. Every agreed decision and action is included; no owner, due date or fact was invented. Missing owners and dates remain explicit. The action table and message agree. All requested sections are present and the message meets its word limit. Supporting quotes need not appear in the final document.
+
+done:
+  - "Every action has an owner and date, or says plainly that one was not agreed."
+  - "Nothing appears that the notes do not support."
+  - "The message can be sent without editing."

package/factories/meeting-to-actions/mindburn.requirements.yaml

@@ -0,0 +1,8 @@
+models:
+  recommended: claude-haiku-5-5
+expected_cost:
+  currency: USD
+  min: 0.008
+  max: 0.02
+  model: claude-haiku-5-5 (writing) + claude-sonnet-5-5 (review)
+  basis: Short-note hosted trials used two Haiku writing calls and one Sonnet review call, with estimated model costs of USD 0.0088128 and 0.0148114. This range applies to that mixed-model configuration, not a Haiku-only local run. Larger transcripts and retries can cost more. Excludes hosting and tool fees; this is an estimate, not a spending cap.

package/factories/meeting-to-actions/mindburn.tests.yaml

@@ -0,0 +1,16 @@
+version: 1
+cases:
+  missing_commitments:
+    name: Keeps agreed actions and makes missing commitments explicit
+    inputs:
+      notes: |
+        Decision: use the compact onboarding form.
+        Dana agreed to email the revised form to Lee. No deadline was agreed.
+        Someone needs to confirm who maintains the help page. Nobody took that task.
+        The team discussed a free trial but made no decision about offering it.
+      context: Planning for a small product team. These are invented example notes.
+    expect:
+      contains: [Dana, Lee, onboarding, help page, free trial, not agreed]
+      excludes: [sent successfully, already emailed]
+      min_length: 200
+      max_length: 6000

package/factories/outreach-pack/README.md

@@ -0,0 +1,3 @@
+# Outreach pack
+
+Provide checked research, approved launch materials and optionally a contact role. The factory writes and checks drafts for you to review and send. It does not collect contacts, publish or send messages.

package/factories/outreach-pack/agents/reviewer/agent.md

@@ -0,0 +1,5 @@
+---
+description: Checks claims, evidence and message constraints.
+agentType: REVIEW
+---
+Judge the complete artifact against the stated criteria. Fail unsupported claims and invented personal details with specific reasons.

package/factories/outreach-pack/agents/writer/agent.md

@@ -0,0 +1,5 @@
+---
+description: Writes specific, honest outreach from supplied evidence.
+agentType: CUSTOM
+---
+Write plain messages with one clear ask. Preserve source links and uncertainties. Never imply an email was sent or a campaign was activated.

package/factories/outreach-pack/factory.yaml

@@ -0,0 +1,9 @@
+schemaVersion: v1alpha1
+name: outreach-pack
+description: |
+  Turns checked market research and launch materials into an outreach pack. Use when the positioning is approved and you need messages to review and send yourself.
+repositories: []
+agentDefaults:
+  harness:
+    type: claude
+    model: sonnet