factoryhub 0.0.0-stage → 0.1.1

package/factories/video-to-posts/README.md

@@ -0,0 +1,35 @@
+# One video, a week of posts
+
+Paste the transcript of a video, podcast or talk. You get a week of posts for X, LinkedIn, a short video and a newsletter, each built on something you actually said, with the timestamp it came from. A checker holds every number and quote against the transcript and sends back any line it does not support. Nothing is final until you approve it, and nothing is posted for you: you copy what you approve.
+
+## Try it on the example
+
+The example is invented: Maya, her flat and her video do not exist. Her figures are easy to round up, such as "two weekends. Maybe three" and "about four, no, three pounds", so the check has something real to hold the posts against. Paste the transcript below, and the line under "About you" if you want it.
+
+Transcript:
+
+```text
+[0:00] So this is the story of how a frying pan made me build an app.
+[0:06] Our flat group chat had 212 messages in one month. I counted. Most of them were about one frying pan that nobody would wash.
+[0:18] There are five of us in the flat. Everyone thought they did the most dishes. Everyone was wrong, including me.
+[0:31] I'm not a programmer. I did one coding course at school and forgot most of it. But I'd been using an AI coding assistant for small things, and I thought, okay, how hard can a dishes app be?
+[0:47] It took me two weekends. Maybe three, if you count the weekend I spent on the logo.
+[0:55] And that's my first lesson. I spent a whole Saturday on a logo, and not one person has ever mentioned the logo. Not one.
+[1:06] Here's how it works, and honestly the trick is how little it does. When something needs washing, you tap one button. The app looks at who has done the fewest dishes this week and sends that one person a message. That's it. No points, no leaderboard, no badges.
+[1:27] I tried points first. Points made it worse. One flatmate started washing single teaspoons to collect points.
+[1:38] So here's my hot take: most chore apps fail because they turn chores into a game. Nobody in my flat wanted a game. We wanted the arguing to stop.
+[1:50] Did it work? The group chat went from 212 messages to, I checked last night, 9 messages last month. And three of those were about pizza.
+[2:04] Then a friend posted about it, and people from other flats started asking for it. 38 people signed up in the first week. Mostly friends of friends, to be fair. 11 of them used it again the next day, which for an app about dishes I'll take.
+[2:22] It costs me about four, no, three pounds a month to run. Three.
+[2:28] What I'd do differently: skip the logo, and ask my flatmates what annoyed them before writing a single line. I guessed it was fairness. It was the frying pan. It's always one frying pan.
+[2:42] If you build something like this, start with the one message the app sends. Write that message first. Everything else is decoration.
+[2:51] Anyway. The pan is clean. For now.
+```
+
+About you:
+
+```text
+I'm Maya. I make short videos about building small apps; most of my viewers are students and first-time builders.
+```
+
+The same example is in `mindburn.tests.yaml`. With the downloaded folder, `node run.mjs --test` runs it and checks that the posts keep the sections and none of the easy roundings. Passing checks are a repeatable regression signal, not proof that every transcript will be handled correctly. Read the posts against your transcript before you copy them.

package/factories/video-to-posts/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/video-to-posts/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/video-to-posts/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/video-to-posts/factory.yaml

@@ -0,0 +1,12 @@
+schemaVersion: v1alpha1
+name: video-to-posts
+description: |
+  Turns the transcript of one video, podcast or talk into a week of posts for
+  X, LinkedIn, a short video and a newsletter, using only what the speaker
+  said. Use after you put out a video on YouTube or TikTok, or a podcast
+  episode, and want posts that say nothing you did not say.
+repositories: []
+agentDefaults:
+  harness:
+    type: claude
+    model: sonnet

package/factories/video-to-posts/flow.yaml

@@ -0,0 +1,62 @@
+flow: mindburn.flow/v1
+title: One video, a week of posts
+author: Mindburn Labs
+version: "1.0.0"
+license: MIT
+tags: [social, marketing]
+time: about 3 minutes
+inputs:
+  transcript:
+    type: longtext
+    help: "The transcript of your video, podcast or talk, pasted as it is. Keep the timestamps if it has them: each post then points back to the moment it came from."
+  about_you:
+    type: text
+    optional: true
+    help: "Who you are and who watches, for example \"I make short videos about building small apps; most of my viewers are students\". It sets the voice, not the facts."
+steps:
+  moments:
+    title: Find the moments worth posting
+    agent: analyst
+    kind: work
+    task: |
+      Read the whole transcript. First write a fact sheet: every number, name, date, result and claim the speaker states, each with the speaker's exact words and its timestamp, if the transcript has timestamps. Keep every qualifier the speaker attaches to a fact, such as "maybe", "about" or "mostly". Where the speaker corrects themselves, the corrected figure is the fact; note the correction. Where the transcript is garbled, or a figure is said two ways without a correction, mark it "unclear" instead of choosing.
+
+      Then pick the five moments most worth posting: a surprising number or result, a short story with a turn, a strong opinion, a how-to someone could copy, a mistake and its lesson. For each give a one-line title, the exact quote (under 40 words), its timestamp, and why a stranger would stop scrolling for it. Rank them, strongest first. Do not pick a moment whose point the transcript does not make. If the transcript supports fewer than five honest moments, give fewer.
+  posts:
+    title: Write the week of posts
+    agent: writer
+    kind: deliver
+    needs: [moments]
+    task: |
+      Write a week of posts from the moments, in the speaker's voice and, wherever you can, in the speaker's own words. Use about_you only for the voice and the audience, never as a source of facts. Sections, in this order:
+
+      1. **The week at a glance**: a table with columns Day (1 to 7), Channel, Moment, First line.
+      2. **X**: one thread of 4 to 6 posts built on the strongest moment, and two single posts on other moments. No post is longer than 280 characters.
+      3. **LinkedIn**: one post under 200 words whose first line works on its own.
+      4. **Short video**: a 30-second script for TikTok, Reels or Shorts: the hook to say in the first two seconds, three beats and a closing line. For each beat, give the timestamp of the original clip to cut in or, if the transcript has no timestamps, the clip's first words.
+      5. **Newsletter**: a note under 120 words that points readers to the full video, with "[ADD: link to the video]" where the link goes.
+      6. **Before you post**: every factual claim the posts make, each with the quote and timestamp it rests on; every person or company the posts name other than the speaker, so you can check they are happy to be named; and anything the speaker should double-check.
+
+      Every fact comes from the transcript, as the fact sheet records it. Never round a number, shorten a time span, make a result bigger or more certain, drop a qualifier that keeps a claim modest, name a person or quote words the speaker did not say. Where a post would be stronger with a real asset, such as a screenshot or a link, write "[ADD: what belongs here]" instead of inventing it. Add no hype the speaker did not use, and no exclamation marks or emojis unless the transcript has them. Use at most two hashtags a post.
+  check_posts:
+    title: Check every line against the transcript
+    agent: reviewer
+    kind: check
+    needs: [posts]
+    checks: posts
+    task: |
+      Compare every line of every post with the transcript and the fact sheet. Each number, time span, name, result and quote appears in the transcript with the same meaning. Nothing is rounded, shortened, made bigger or more certain, or moved to a different context, and quotes are word for word. A qualifier the speaker attached stays wherever leaving it out would make the claim sound bigger or more certain. A self-corrected figure uses the corrected value; an unclear one is not stated as fact. Send back any line the transcript does not support.
+
+      Then check the shape: all six sections are present and in order, no X post is longer than 280 characters, the LinkedIn post and the newsletter note keep to their word limits, each beat of the short-video script points to a timestamp or to the first words of a clip, and every factual claim appears in "Before you post". When you send work back, quote the post's words and the transcript's words side by side so the writer can correct them.
+  approve_posts:
+    title: Approve the posts
+    kind: approve
+    needs: [check_posts]
+    shows: posts
+    task: |
+      These go out under your name. Approve them, or say what to change: a moment to drop, a line that does not sound like you, a fact that is wrong. Nothing is posted for you: you copy what you approve.
+
+done:
+  - "Every number, time span, name and quote in the posts is in the transcript, with the same meaning."
+  - "Every post can be copied as it stands, or marks plainly what to add."
+  - "Every factual claim is listed under \"Before you post\" with the words it rests on."

package/factories/video-to-posts/mindburn.tests.yaml

@@ -0,0 +1,34 @@
+version: 1
+cases:
+  frying_pan_app:
+    name: Keeps every figure exactly as the speaker said it
+    inputs:
+      transcript: |
+        [0:00] So this is the story of how a frying pan made me build an app.
+        [0:06] Our flat group chat had 212 messages in one month. I counted. Most of them were about one frying pan that nobody would wash.
+        [0:18] There are five of us in the flat. Everyone thought they did the most dishes. Everyone was wrong, including me.
+        [0:31] I'm not a programmer. I did one coding course at school and forgot most of it. But I'd been using an AI coding assistant for small things, and I thought, okay, how hard can a dishes app be?
+        [0:47] It took me two weekends. Maybe three, if you count the weekend I spent on the logo.
+        [0:55] And that's my first lesson. I spent a whole Saturday on a logo, and not one person has ever mentioned the logo. Not one.
+        [1:06] Here's how it works, and honestly the trick is how little it does. When something needs washing, you tap one button. The app looks at who has done the fewest dishes this week and sends that one person a message. That's it. No points, no leaderboard, no badges.
+        [1:27] I tried points first. Points made it worse. One flatmate started washing single teaspoons to collect points.
+        [1:38] So here's my hot take: most chore apps fail because they turn chores into a game. Nobody in my flat wanted a game. We wanted the arguing to stop.
+        [1:50] Did it work? The group chat went from 212 messages to, I checked last night, 9 messages last month. And three of those were about pizza.
+        [2:04] Then a friend posted about it, and people from other flats started asking for it. 38 people signed up in the first week. Mostly friends of friends, to be fair. 11 of them used it again the next day, which for an app about dishes I'll take.
+        [2:22] It costs me about four, no, three pounds a month to run. Three.
+        [2:28] What I'd do differently: skip the logo, and ask my flatmates what annoyed them before writing a single line. I guessed it was fairness. It was the frying pan. It's always one frying pan.
+        [2:42] If you build something like this, start with the one message the app sends. Write that message first. Everything else is decoration.
+        [2:51] Anyway. The pan is clean. For now.
+      # Invented sample: Maya, her flat and this video do not exist. The
+      # disclosure stays out of the inputs so it does not leak into the posts;
+      # the README carries it.
+      about_you: "I'm Maya. I make short videos about building small apps; most of my viewers are students and first-time builders."
+    # Contains: the sections the flow asks for and the subject of the video.
+    # Excludes: the easy roundings of what Maya said (two weekends, maybe
+    # three; one coding course; 38 sign-ups; three pounds after a correction)
+    # and a result she never claims.
+    expect:
+      contains: ["LinkedIn", "Short video", "Newsletter", "Before you post", "frying pan"]
+      excludes: ["went viral", "in one weekend", "in a weekend", "40 people", "nearly 40", "almost 40", "never coded", "£4", "four pounds a month"]
+      min_length: 1500
+      max_length: 16000

package/factories/week-of-posts/README.md

@@ -0,0 +1,11 @@
+# X and LinkedIn posts from the facts
+
+Paste the facts sheet of a video, podcast or talk, and the transcript if you have it. You get an X thread of 4 to 6 posts, two single posts and a LinkedIn post, in your voice and wherever possible in your own words, with a list of every fact they use and the words it rests on. A checker holds every line against the facts sheet and sends back anything stronger than what you said: a rounded number, a dropped "maybe", a result made bigger. Nothing is posted for you.
+
+The facts sheet can come from "Facts from a video", or you can write your own: one fact a line, each with its timestamp or the first words of the line. "Release desk" puts these posts together with the other pieces for one approval.
+
+## Try it on the example
+
+The example is invented: Maya, her flat and her video do not exist. Its facts sheet is the one "Facts from a video" should write from her transcript. On the factory page, "Fill in the example" pastes it for you.
+
+The example is in `mindburn.tests.yaml`. With the downloaded folder, `node run.mjs --test` runs it and checks that the posts keep the sections and none of the easy roundings. Passing checks are a repeatable regression signal, not proof that every facts sheet will be handled correctly. Read the posts against your facts before you copy them.

package/factories/week-of-posts/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/week-of-posts/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/week-of-posts/factory.yaml

@@ -0,0 +1,12 @@
+schemaVersion: v1alpha1
+name: week-of-posts
+description: |
+  Writes an X thread, two single posts and a LinkedIn post from the facts
+  sheet of one video, podcast or talk, in the speaker's voice, saying nothing
+  the facts sheet does not say. Use after "Facts from a video", or with your
+  own list of what you said, when you want posts you can put your name to.
+repositories: []
+agentDefaults:
+  harness:
+    type: claude
+    model: sonnet

package/factories/week-of-posts/flow.yaml

@@ -0,0 +1,46 @@
+flow: mindburn.flow/v1
+title: X and LinkedIn posts from the facts
+author: Mindburn Labs
+version: "1.0.0"
+license: MIT
+tags: [social, marketing]
+time: about 2 minutes
+inputs:
+  facts:
+    type: longtext
+    help: "The facts sheet from \"Facts from a video\", or your own list of what you said: one fact a line, each with its timestamp or the first words of the line."
+  transcript:
+    type: longtext
+    optional: true
+    help: "The transcript the facts came from. With it, the posts can use your exact wording and the checker can quote it when it sends a line back."
+  about_you:
+    type: text
+    optional: true
+    help: "Who you are and who watches, for example \"I make short videos about building small apps; most of my viewers are students\". It sets the voice, not the facts."
+steps:
+  posts:
+    title: Write the X thread and the LinkedIn post
+    agent: writer
+    kind: deliver
+    task: |
+      Write posts from the facts sheet, in the speaker's voice and, wherever you can, in the speaker's own words as the sheet quotes them. Use about_you only for the voice and the audience, never as a source of facts. Sections, in this order:
+
+      1. **X**: one thread of 4 to 6 numbered posts built on the strongest fact or story on the sheet, then two single posts on other facts. No post is longer than 280 characters.
+      2. **LinkedIn**: one post under 200 words whose first line works on its own.
+      3. **Facts used**: every factual claim the posts make, each with the facts-sheet ID if the sheet has IDs, its timestamp or first words, and the exact words it rests on.
+
+      Every fact comes from the facts sheet. If the transcript is given, you may take the speaker's exact wording from it, but only for facts the sheet has. Never round a number, shorten or lengthen a time span, make a result bigger or more certain, drop a qualifier that keeps a claim modest, state an opinion as a fact, work out a figure the sheet does not state, such as a percentage, or name a person the sheet does not name. A fact the sheet marks "unclear" is not stated as settled. Where a post would be stronger with a real asset, such as a screenshot or a link, write "[ADD: what belongs here]" instead of inventing it. Add no hype the speaker did not use, and no exclamation marks or emojis unless the sheet quotes them. Use at most two hashtags a post.
+  check_posts:
+    title: Check every line against the facts sheet
+    agent: reviewer
+    kind: check
+    needs: [posts]
+    checks: posts
+    task: |
+      Compare every line of every post with the facts sheet, and with the transcript if it is given. Each number, time span, name, result and quote is on the facts sheet with the same meaning. Send back any line that says more than the source: a rounded or worked-out figure, a shorter or longer time span, a result made bigger or more certain, a dropped qualifier such as "maybe", "about" or "mostly", an opinion stated as fact, a fact marked "unclear" stated as settled, or a quote that is not word for word. Send back any fact the sheet does not have, even one that sounds harmless.
+
+      Then check the shape: the three sections are present and in order, the thread has 4 to 6 numbered posts and there are two single posts, no X post is longer than 280 characters, the LinkedIn post is under 200 words, and every factual claim appears under "Facts used". When you send work back, quote the post's words and the source's words side by side so the writer can correct them.
+done:
+  - "Every number, time span, name and quote in the posts is on the facts sheet, with the same meaning."
+  - "No post says more than the source: nothing rounded, worked out or made more certain, and no qualifier dropped."
+  - "Every factual claim is listed under \"Facts used\" with the words it rests on."

package/factories/week-of-posts/mindburn.tests.yaml

@@ -0,0 +1,80 @@
+version: 1
+cases:
+  frying_pan_posts:
+    name: Writes posts that say no more than the facts sheet
+    inputs:
+      facts: |
+        ## Facts
+
+        | ID | Where | Fact | Exact words |
+        | --- | --- | --- | --- |
+        | F1 | [0:00] | The video is the story of how a frying pan made the speaker build an app. | "So this is the story of how a frying pan made me build an app." |
+        | F2 | [0:06] | The flat's group chat had 212 messages in one month; the speaker counted them. | "Our flat group chat had 212 messages in one month. I counted." |
+        | F3 | [0:06] | Most of those messages were about one frying pan that nobody would wash. | "Most of them were about one frying pan that nobody would wash." |
+        | F4 | [0:18] | Five people live in the flat. | "There are five of us in the flat." |
+        | F5 | [0:18] | Everyone thought they did the most dishes, and everyone was wrong, the speaker included. | "Everyone thought they did the most dishes. Everyone was wrong, including me." |
+        | F6 | [0:31] | The speaker is not a programmer: one coding course at school, most of it forgotten. | "I'm not a programmer. I did one coding course at school and forgot most of it." |
+        | F7 | [0:31] | The speaker had been using an AI coding assistant for small things. | "But I'd been using an AI coding assistant for small things" |
+        | F8 | [0:47] | The app took two weekends, maybe three counting the weekend spent on the logo. | "It took me two weekends. Maybe three, if you count the weekend I spent on the logo." |
+        | F9 | [0:55] | The speaker's first lesson: a whole Saturday went on a logo, and nobody has ever mentioned it. | "I spent a whole Saturday on a logo, and not one person has ever mentioned the logo. Not one." |
+        | F10 | [1:06] | When something needs washing, you tap one button, and the app messages the one person who has done the fewest dishes this week. | "When something needs washing, you tap one button. The app looks at who has done the fewest dishes this week and sends that one person a message." |
+        | F11 | [1:06] | The app has no points, no leaderboard and no badges. | "No points, no leaderboard, no badges." |
+        | F12 | [1:27] | Points came first and made it worse: one flatmate washed single teaspoons to collect points. | "I tried points first. Points made it worse. One flatmate started washing single teaspoons to collect points." |
+        | F13 | [1:38] | The speaker's opinion, called a hot take: most chore apps fail because they turn chores into a game. | "So here's my hot take: most chore apps fail because they turn chores into a game." |
+        | F14 | [1:38] | Nobody in the flat wanted a game; they wanted the arguing to stop. | "Nobody in my flat wanted a game. We wanted the arguing to stop." |
+        | F15 | [1:50] | The group chat went from 212 messages to 9 messages last month, and three of those were about pizza. | "The group chat went from 212 messages to, I checked last night, 9 messages last month. And three of those were about pizza." |
+        | F16 | [2:04] | After a friend posted about it, people from other flats started asking for it. | "Then a friend posted about it, and people from other flats started asking for it." |
+        | F17 | [2:04] | 38 people signed up in the first week, mostly friends of friends. | "38 people signed up in the first week. Mostly friends of friends, to be fair." |
+        | F18 | [2:04] | 11 of them used it again the next day. | "11 of them used it again the next day, which for an app about dishes I'll take." |
+        | F19 | [2:22] | Running it costs three pounds a month, after a correction. | "It costs me about four, no, three pounds a month to run. Three." |
+        | F20 | [2:28] | What the speaker would do differently: skip the logo, and ask the flatmates what annoyed them before writing a single line. They guessed fairness; it was the frying pan. | "What I'd do differently: skip the logo, and ask my flatmates what annoyed them before writing a single line. I guessed it was fairness. It was the frying pan." |
+        | F21 | [2:42] | The speaker's advice: start with the one message the app sends, and write that message first. | "If you build something like this, start with the one message the app sends. Write that message first. Everything else is decoration." |
+        | F22 | [2:51] | The pan is clean, for now. | "The pan is clean. For now." |
+
+        ## Quotes worth using
+
+        - [0:06] "Our flat group chat had 212 messages in one month. I counted." (F2)
+        - [0:55] "not one person has ever mentioned the logo. Not one." (F9)
+        - [1:06] "No points, no leaderboard, no badges." (F11)
+        - [1:27] "One flatmate started washing single teaspoons to collect points." (F12)
+        - [1:38] "We wanted the arguing to stop." (F14)
+        - [2:28] "I guessed it was fairness. It was the frying pan." (F20)
+        - [2:42] "Write that message first. Everything else is decoration." (F21)
+        - [2:51] "The pan is clean. For now." (F22)
+
+        ## Corrections and unclear
+
+        - [2:22] The running cost: the speaker says "about four, no, three pounds a month", then "Three." The corrected figure, three pounds a month, is the fact (F19).
+        - [0:47] and [0:55] The time on the logo is said two ways: "the weekend I spent on the logo" and "a whole Saturday on a logo". Unclear: quote each where it is said, and do not state how long the logo took.
+
+        ## Names
+
+        No one other than the speaker is named.
+      transcript: |
+        [0:00] So this is the story of how a frying pan made me build an app.
+        [0:06] Our flat group chat had 212 messages in one month. I counted. Most of them were about one frying pan that nobody would wash.
+        [0:18] There are five of us in the flat. Everyone thought they did the most dishes. Everyone was wrong, including me.
+        [0:31] I'm not a programmer. I did one coding course at school and forgot most of it. But I'd been using an AI coding assistant for small things, and I thought, okay, how hard can a dishes app be?
+        [0:47] It took me two weekends. Maybe three, if you count the weekend I spent on the logo.
+        [0:55] And that's my first lesson. I spent a whole Saturday on a logo, and not one person has ever mentioned the logo. Not one.
+        [1:06] Here's how it works, and honestly the trick is how little it does. When something needs washing, you tap one button. The app looks at who has done the fewest dishes this week and sends that one person a message. That's it. No points, no leaderboard, no badges.
+        [1:27] I tried points first. Points made it worse. One flatmate started washing single teaspoons to collect points.
+        [1:38] So here's my hot take: most chore apps fail because they turn chores into a game. Nobody in my flat wanted a game. We wanted the arguing to stop.
+        [1:50] Did it work? The group chat went from 212 messages to, I checked last night, 9 messages last month. And three of those were about pizza.
+        [2:04] Then a friend posted about it, and people from other flats started asking for it. 38 people signed up in the first week. Mostly friends of friends, to be fair. 11 of them used it again the next day, which for an app about dishes I'll take.
+        [2:22] It costs me about four, no, three pounds a month to run. Three.
+        [2:28] What I'd do differently: skip the logo, and ask my flatmates what annoyed them before writing a single line. I guessed it was fairness. It was the frying pan. It's always one frying pan.
+        [2:42] If you build something like this, start with the one message the app sends. Write that message first. Everything else is decoration.
+        [2:51] Anyway. The pan is clean. For now.
+      # Invented sample: Maya, her flat and this video do not exist. The
+      # disclosure stays out of the inputs so it does not leak into the result;
+      # the README carries it.
+      about_you: "I'm Maya. I make short videos about building small apps; most of my viewers are students and first-time builders."
+    # The facts sheet is the reference result of "Facts from a video" on the
+    # same transcript. Excludes: the roundings it invites, the running cost before
+    # the correction, a result she never claims and percentages she never said.
+    expect:
+      contains: ["LinkedIn", "Facts used", "frying pan"]
+      excludes: ["went viral", "in one weekend", "in a weekend", "40 people", "nearly 40", "almost 40", "never coded", "£4", "four pounds a month", "96%", "29%"]
+      min_length: 900
+      max_length: 9000

package/package.json

@@ -1,6 +1,94 @@
 {
   "name": "factoryhub",
-  "version": "0.0.0-stage",
-  "stub": true,
-  "description": "Temporary package placeholder for staged publishing"
-}
+  "version": "0.1.1",
+  "description": "AI factories, shared: the open factory format, its engine, a CLI and a local MCP server, with the house factories.",
+  "keywords": [
+    "factoryhub",
+    "ai-factories",
+    "ai-agents",
+    "agent-skills",
+    "human-in-the-loop",
+    "mcp",
+    "mcp-server",
+    "model-context-protocol",
+    "cli",
+    "anthropic",
+    "openai",
+    "openrouter",
+    "ollama"
+  ],
+  "license": "Apache-2.0",
+  "author": "Mindburn Labs (https://mindburn.org)",
+  "type": "module",
+  "homepage": "https://github.com/Mindburn-Labs/factoryhub#readme",
+  "bugs": "https://github.com/Mindburn-Labs/factoryhub/issues",
+  "repository": {
+    "type": "git",
+    "url": "git+https://github.com/Mindburn-Labs/factoryhub.git"
+  },
+  "mcpName": "io.github.Mindburn-Labs/factoryhub",
+  "exports": {
+    ".": {
+      "types": "./packages/sdk/src/index.d.ts",
+      "default": "./packages/sdk/src/index.mjs"
+    },
+    "./engine": "./packages/engine/src/index.mjs",
+    "./package.json": "./package.json",
+    "./*": "./*"
+  },
+  "types": "./packages/sdk/src/index.d.ts",
+  "engines": {
+    "node": ">=22"
+  },
+  "workspaces": [
+    "packages/engine",
+    "packages/cli",
+    "packages/mcp"
+  ],
+  "bin": {
+    "factoryhub": "packages/cli/bin/factoryhub.mjs",
+    "factoryhub-mcp": "packages/mcp/bin/factoryhub-mcp.mjs"
+  },
+  "files": [
+    "packages/engine/package.json",
+    "packages/engine/src",
+    "packages/engine/lib",
+    "packages/cli/package.json",
+    "packages/cli/bin",
+    "packages/cli/src",
+    "packages/mcp/package.json",
+    "packages/mcp/bin",
+    "packages/mcp/src",
+    "packages/sdk/package.json",
+    "packages/sdk/src",
+    "factories",
+    "NOTICE",
+    "spec/*.md",
+    "spec/schema"
+  ],
+  "scripts": {
+    "test": "node --test \"packages/*/test/*.test.mjs\" \"spec/test/*.test.mjs\" \"test/*.test.mjs\"",
+    "lint": "eslint . && node scripts/check-links.mjs",
+    "validate": "node packages/cli/bin/factoryhub.mjs validate factories/*/",
+    "generate": "node scripts/generate.mjs",
+    "check": "npm run lint && npm test && npm run validate && node scripts/generate.mjs --check && npm run check:rust",
+    "check:rust": "cargo fmt --all --check && cargo clippy --all-targets --locked -- -D warnings && cargo test --locked && cargo build --locked --target wasm32-unknown-unknown -p factoryhub-core"
+  },
+  "dependencies": {
+    "@modelcontextprotocol/server": "2.4.0",
+    "zod": "4.6.7"
+  },
+  "devDependencies": {
+    "@eslint/js": "10.0.1",
+    "@modelcontextprotocol/client": "2.4.0",
+    "ajv": "8.20.0",
+    "eslint": "10.15.0",
+    "globals": "17.14.0",
+    "yaml": "2.9.1"
+  },
+  "publishConfig": {
+    "access": "public",
+    "provenance": true,
+    "registry": "https://registry.npmjs.org/"
+  }
+}

package/packages/cli/bin/factoryhub.mjs

@@ -0,0 +1,8 @@
+#!/usr/bin/env node
+import process from 'node:process';
+import { main } from '../src/main.mjs';
+
+// A reader that stops early, such as `| head`, is not an error.
+process.stdout.on('error', (error) => { if (error.code === 'EPIPE') process.exit(0); throw error; });
+
+process.exitCode = await main(process.argv.slice(2));

package/packages/cli/package.json

@@ -0,0 +1,29 @@
+{
+  "name": "@factoryhub/cli",
+  "version": "0.1.1",
+  "description": "The factoryhub command line: validate, inspect, scaffold, pack, run and export AI factories, and find them on factoryhub.",
+  "license": "Apache-2.0",
+  "type": "module",
+  "private": true,
+  "engines": {
+    "node": ">=22"
+  },
+  "repository": {
+    "type": "git",
+    "url": "git+https://github.com/Mindburn-Labs/factoryhub.git",
+    "directory": "packages/cli"
+  },
+  "bin": {
+    "factoryhub": "bin/factoryhub.mjs"
+  },
+  "exports": {
+    ".": "./src/main.mjs"
+  },
+  "files": [
+    "bin",
+    "src"
+  ],
+  "scripts": {
+    "test": "node --test \"test/*.test.mjs\""
+  }
+}

package/packages/cli/src/args.mjs

@@ -0,0 +1,47 @@
+// A small argument parser: positional words, --name value, --name=value,
+// boolean switches and repeatable options. Unknown options are an error, so a
+// misspelt option never silently changes what a command does.
+
+/**
+ * @param {string[]} argv
+ * @param {{ boolean?: string[], string?: string[], repeat?: string[], alias?: Record<string,string> }} spec
+ */
+export function parseArgs(argv, spec = {}) {
+  const booleans = new Set(['help', ...(spec.boolean || [])]);
+  const strings = new Set(spec.string || []);
+  const repeats = new Set(spec.repeat || []);
+  const alias = { h: 'help', ...(spec.alias || {}) };
+  const flags = {};
+  const positional = [];
+  for (const name of repeats) flags[name] = [];
+  for (let i = 0; i < argv.length; i += 1) {
+    const arg = argv[i];
+    if (arg === '--') { positional.push(...argv.slice(i + 1)); break; }
+    if (!arg.startsWith('-') || arg === '-') { positional.push(arg); continue; }
+    let name;
+    let value;
+    if (arg.startsWith('--')) {
+      const eq = arg.indexOf('=');
+      name = eq > 0 ? arg.slice(2, eq) : arg.slice(2);
+      if (eq > 0) value = arg.slice(eq + 1);
+    } else {
+      name = alias[arg.slice(1)];
+      if (!name) throw new Error(`Unknown option ${arg}.`);
+    }
+    name = alias[name] || name;
+    if (booleans.has(name)) {
+      if (value !== undefined) throw new Error(`--${name} takes no value.`);
+      flags[name] = true;
+      continue;
+    }
+    if (name.startsWith('no-') && booleans.has(name.slice(3))) { flags[name.slice(3)] = false; continue; }
+    if (!strings.has(name) && !repeats.has(name)) throw new Error(`Unknown option --${name}.`);
+    if (value === undefined) {
+      if (i + 1 >= argv.length) throw new Error(`--${name} needs a value.`);
+      value = argv[i += 1];
+    }
+    if (repeats.has(name)) flags[name].push(value);
+    else flags[name] = value;
+  }
+  return { flags, positional };
+}

package/packages/cli/src/commands/export.mjs

@@ -0,0 +1,54 @@
+import { existsSync } from 'node:fs';
+import { rm } from 'node:fs/promises';
+import { resolve, relative, join } from 'node:path';
+import { readFactory, writeFiles, out, err, styles, usage } from '../util.mjs';
+import { exportSkill, checkSkill } from '../../../engine/lib/skill.mjs';
+import { DEFAULT_HUB } from '../../../engine/lib/hub.mjs';
+
+export default {
+  name: 'export',
+  usage: `Usage: factoryhub export <factory> --as skill [--out dir] [--id id] [--force]
+
+Writes <dir>/<id>/SKILL.md and <dir>/<id>/factory/, following
+spec/skill-export.md. SKILL.md tells an agent what the factory produces, which
+inputs to collect, every step in order with who does it, where to stop and
+ask the person to approve, and how to run it with this CLI or by hand.
+factory/ holds the factory's files unchanged, plus the foreman written from
+the flow when the author wrote none.
+
+Copy the folder into your agent's skills directory, for example
+~/.claude/skills/ for Claude Code.
+
+Options:
+  --as     the export format; "skill" is the only one
+  --out    the parent folder (default: the current folder)
+  --id     the skill name and factoryhub id (default: the factory's name)
+  --hub    the factoryhub address used for the source link (default: ${DEFAULT_HUB})
+  --force  replace an earlier export of the same factory`,
+  options: { boolean: ['force'], string: ['as', 'out', 'id', 'hub'] },
+  async run({ positional, flags }, io) {
+    const [target] = positional;
+    if (!target) throw usage('Name a factory to export.');
+    if (flags.as !== 'skill') throw usage('Choose the export format: --as skill');
+    const read = await readFactory(target, { cwd: io.cwd, fetchImpl: io.fetch });
+    const skill = await exportSkill(read.files, { id: flags.id, hub: flags.hub || DEFAULT_HUB });
+    const folder = resolve(io.cwd, flags.out || '.', skill.id);
+    const s = styles(io);
+    // Checked before anything is written: a failing export leaves no files.
+    const problems = await checkSkill(skill.files, { folder: skill.id, hub: flags.hub || DEFAULT_HUB });
+    if (problems.length) {
+      err(io, `${s.red('not exported')}  ${skill.id}: the export fails its checks`);
+      for (const problem of problems) err(io, `  - ${problem}`);
+      return 1;
+    }
+    if (existsSync(folder)) {
+      if (!flags.force) throw usage(`${folder} already exists. Pass --force to replace it.`);
+      // Replace an earlier export as a whole, so no stale file stays behind.
+      if (!existsSync(join(folder, 'SKILL.md'))) throw usage(`${folder} is not an earlier skill export, so it was left alone.`);
+      await rm(folder, { recursive: true, force: true });
+    }
+    await writeFiles(folder, skill.files, { allow: (path) => path === 'SKILL.md' || path.startsWith('factory/') });
+    out(io, `${s.green('exported')}  ${relative(io.cwd, folder) || folder}/SKILL.md and factory/ (${Object.keys(skill.files).length - 1} files), sha256 ${skill.sha256}`);
+    return 0;
+  },
+};