Story Factory

Self-containment note (R20): external documents referenced herein are vendored under canon/ as of 2026-07-05. Citations below are the historical record of what this report read at authoring time and are left verbatim; to follow one as a live pointer, resolve the doc under canon/.

1. What it is (the one-paragraph truth)

Story Factory is the structured-document-generation primitive of the Looikos ecosystem, and a self-standing brand that produces business documents at industrial scale. The plain version: it holds hundreds of report, document, and form templates, and agentic systems fill them dozens at a time, while the human stays in control by driving through questionnaires and approval checkpoints rather than writing each document from a blank page. Andy's own framing is Mad Libs on steroids, a template with typed slots that agents populate with grounded content, scaled to the whole catalog of documents a business actually runs on: proposals, statements of work, reports, briefs, standard operating procedures, compliance forms, contracts. The reason it is a primitive rather than a niche tool is that stories and documents sit at the root of everything, because a document is just a structured story, and every brand in the ecosystem and every customer outside it produces volumes of them.

The problem it solves has two failure modes that the market currently forces a choice between. Structured documents are produced one at a time, slowly and inconsistently, by expensive humans who recreate near-identical work and let the copies drift apart, or they are produced by a raw language-model dump that writes fluently but hallucinates, carries no traceable grounding, and has no real structure or approval path.

Story Factory sits in the gap: grounded generation in the STORM lineage (the Stanford algorithm for writing Wikipedia-grade articles, which plans, fetches facts before drafting, and validates against sources), at the breadth of a whole template catalog, with the human-in-control questionnaire-and-checkpoint workflow as a first-class part of the product rather than bolted-on orchestration.

For whom: any operator or team that produces volumes of structured documents and is currently choosing between the slow expensive human path and the fast ungrounded machine path. Story Factory is concept-stage today, with no standalone repo, though its specialization (PRD Master, the spec-document brand) and its decomposition sibling (Taskmaster) exist in the tree, so the general primitive is the abstraction above a practice the ecosystem already runs in specialized form.

2. Andy's seed, expanded

Andy's words (verbatim from the ecosystem capture): "Story Factory (industrial-scale narrative generation). Stories sit at the root of everything, so the ecosystem needs a primitive that produces them at scale. Story Factory is Mad Libs on steroids: hundreds of report, document, and form templates, filled dozens at a time by agentic systems and workflows, with the user driving through questionnaires and checkpoints that keep the team on track. The structured-document-generation primitive."

Reading between the lines. Four things sit compressed in that seed, and the market read confirms each is a real and largely unoccupied position.

The first is why "stories sit at the root of everything" is a load-bearing claim rather than a flourish. Narrative is how humans process the world, the same insight the PST framework runs on, and a business document is a structured story with the narrative compressed into a fixed form: a proposal tells the story of a problem and a solution, a report tells the story of what happened and what it means, a standard operating procedure tells the story of how the work is done. If narrative is the substrate of understanding, then the ability to produce structured narrative at scale is a primitive the way data modeling is a primitive, which is exactly why Story Factory sits in Category 1 beside WikiDesignCo and Scatter Model rather than in the content or agency categories. It is infrastructure, not a content product.

The second is what "Mad Libs on steroids" actually specifies as an architecture. A Mad Lib is a template with typed slots, and the steroids are that the slots are filled by agents with grounded content rather than by a human guessing a noun, and that there are hundreds of templates filled dozens at a time rather than one filled once. The market read sharpens this into the durable shape: flat templates are not enough, because the real value is a template graph where the relationships between documents are first-class, so a proposal and its statement of work and its compliance form are generated as a coherent bundle that agrees with itself on the facts and the language rather than three separate documents that drift. Story Factory's "filled dozens at a time" is the seed of exactly that bundle-generation capability, and the template-graph framing is how it becomes cross-document consistency rather than batch-of-isolated-docs.

The third is the questionnaire-and-checkpoint driving model, which is the human-in-control part and the answer to the trust problem that sinks ungrounded generation. Instead of a human writing the document, the human answers a questionnaire that drives the intake, and reviews at checkpoints where the agents pause for sign-off, so the human supplies the judgment and the agents supply the production. The market read confirms this pattern is real and names the failure mode to avoid: human-in-the-loop checkpoints work only when they are minimal and high-signal, because cluttered approval workflows backfire, so the winning shape hides complexity from the user, shows concise summaries at checkpoints, and only asks for human judgment where it genuinely affects risk. Story Factory's checkpoints-that-keep-the-team-on-track is that minimal-high-signal review pattern stated in Andy's own words.

The fourth is the STORM lineage, which is what makes the generation trustworthy rather than fluent-but-wrong. STORM is the Stanford algorithm for writing Wikipedia-grade articles, which plans the document, fetches facts before drafting, and validates against sources, producing grounded, citation-backed output rather than confident confabulation. The market read confirms that STORM-style multi-step grounded generation is being built ad-hoc in enterprise prototypes but is not baked into the mainstream SaaS products, which either do deterministic merge (safe but dumb) or add an ungrounded LLM copilot (smart but weakly grounded), so a platform that makes STORM-grade grounding the core of its document engine sells reliability and traceability rather than just AI-inside. Story Factory shares this STORM lineage with Wardley Swarm, whose strategy maps are STORM-inspired so they can be trusted to power content generation, which is why the two are siblings: Wardley Swarm produces the trustworthy strategic map, Story Factory produces the trustworthy document, both on the same grounded-generation discipline. Story Factory is also downstream of Scatter Model, whose Jinja and dynamic-generation layer is the template engine Story Factory's catalog runs on, and it is the general primitive that PRD Master specializes (PRD Master is Story Factory pointed at operational and spec documents). All four siblings are referenced, not copied, per the-disconnection: each fact lives in its own deck, and Story Factory connects to them rather than duplicating them.

3. The three-angle valuation (the core of a self-standing brand)

3a. Finance (credit and capital access)

The finance read on a document-generation platform turns on a structural fact: once a team's document production runs through your workflow, the templates, the questionnaires, and the checkpoints become embedded in how the organization works, and ripping that out means rebuilding the whole document operation. That embedding is the foundation of the credit and valuation story, and it is why the document-automation and contract-software categories sustain healthy multiples.

The economic activity has three natural meters. A seat or subscription meter for the human operators who drive the questionnaires and review the checkpoints, a per-document or per-bundle meter for the output, and a usage meter for the agentic generation itself. Because Story Factory is concept-stage with no live revenue, those throughput figures are projections, and the deck holds that distinction. What can be anchored is the quality profile the category shows. Document-automation and contract-lifecycle tools have strong retention because the document workflow is mission-critical and switching is painful, which is exactly the ARR quality a revenue-based-financing desk or venture-debt lender lends against, and the embedded-in-the-workflow stickiness makes the forward revenue forecastable. The capital path is the standard vertical-SaaS one: private venture and venture-debt early, with an expansion motion that spreads from one document type (say proposals) to the whole catalog inside an account.

The M&A and valuation comps are named and post-2020. The contract-lifecycle-management category, the closest structural neighbor, was sized around $2.2B-to-$2.5B in 2023 growing toward $3.8B-to-$4.0B by 2027 at roughly 12-to-13% CAGR, with Ironclad reported above $3B at peak and Icertis at several billion (funding comps rather than exits). Conga merged with Apttus in 2020 to form a major quote-to-cash plus document-generation platform, which set a baseline for the value of integrated document-automation stacks. On the AI-writing side, Jasper raised in 2021-to-2022 at a widely reported ~$1.5B valuation, establishing a high-growth multiple for the category (with the caveat, which the deck states, that AI-writing valuations have likely compressed since and that the office suites have internalized generic generation). The cross-cutting addressable market the platform sits in (CLM plus proposal and RFP plus document automation, overlapping enterprise content management) is defensibly above $5B by mid-decade.

Run the $10M floor against those comps and the standard conclusion holds: $10M is what the service angle alone floors at, and a brand sitting in a category whose comparables run from low billions to several billions has a software-angle ceiling far above that. The concept-stage discount applies with full honesty: Story Factory has no ARR, so it is valued today on the strength of the thesis, the proven specialized siblings, and the category comps, not on a revenue multiple, and the deck projects no fictional ARR.

The market-maker's tri-level read closes it. The fundamentals are the category's strong retention and the mission-critical stickiness, unproven for this specific brand. The technicals are the land-and-expand motion (one document type, then the catalog) the comparable companies use. The live sentiment is a genuine and large tailwind: the entire enterprise is shifting document work from manual authoring toward agentic orchestration, the demand for grounded generation is rising precisely because the ungrounded copilots disappointed, and the STORM-style grounded approach is exactly what the market is reaching for. Sentiment is moving toward the grounded, structured, human-in-control generation Story Factory is, which is the most favorable reading a young brand in this category can get, tempered by the honest note that the incumbents (SharePoint with Copilot, Box, Templafy) are converging on the same shape and can add grounding over time, so the sentiment tailwind comes with a named competitive clock.

3b. Software (the interface stack)

Software is the core angle for Story Factory, because the brand is a document-generation platform first and a service second. The product is one document-generation core exposed through many surfaces, on the same hexagonal core-one-surfaces-many discipline the ecosystem runs on.

The surfaces map to revenue lines. The questionnaire-driven UI and the template library, where a human intakes a document request and reviews at checkpoints, is the SaaS subscription surface for human operators. The MCP server is the agent-native surface where other Constellation brands and external agents request documents programmatically, and that agentic generation is the credit-metered pattern. The CLI and the API support a credit-and-subscription program for programmatic and batch consumers (the generate-dozens-at-a-time pattern is naturally a batch API). The template-authoring surface is its own monetizable layer, because the market read shows that the durable edge is less the raw number of pre-built templates and more how quickly a customer can author and adapt their own templates with the domain logic and grounding encoded once and reused, so the authoring experience is a product in itself rather than a setup step. The checkpoint-and-review workflow engine is the surface that carries the human-in-control value, and the market read confirms it has to be a minimal-high-signal review rather than a cluttered approval chain.

The platform decomposes into feature factories with clean domain boundaries. Five are legible from the seed and the market read. The template-library-and-graph factory (the catalog, and the relationships between documents so a bundle stays self-consistent, which the market read names as the first-class differentiator over flat templates). The questionnaire-and-intake factory (the dynamic forms that drive the generation, built on the same dynamic-forms capability the ecosystem shares). The grounding-and-fill factory (the STORM-style planner that fetches facts before drafting and logs citations, plus the connectors to the systems of record that the market read identifies as the real grounding requirement). The checkpoint-and-review factory (the minimal-high-signal human-in-the-loop workflow). The export-and-format factory (rendering to the document formats the customer needs). Each is the custom-modular-composable-harness pattern the Harness V2 build provides (referenced from, not copied).

The market read sharpens the software architecture in three ways the deck builds in honestly. First, breadth versus depth: maintaining hundreds of high-quality templates is expensive and enterprises customize heavily, so the edge is less the count and more the speed of customer-side authoring plus the encode-once-reuse grounding, which means the authoring tooling and the template graph are the load-bearing surfaces, not a vanity template count. Second, grounding requires tight integration with systems of record (CRM, ERP, governance and compliance repositories, knowledge bases), so without schema-aware connectors and a mapping UI the platform degrades into a smart template layer that still needs manual data-copying, which means the grounding fabric is a first-class build requirement rather than a nice-to-have.

Third, the checkpoints must be minimal and high-signal, hiding complexity and surfacing concise summaries, or the human-in-the-loop value inverts into friction. These are the engineering shape that makes the thesis shippable, and a deck that omitted them would be selling the abstract idea rather than the buildable product.

The connection to Scatter Model is the cleanest software decision. Story Factory does not rebuild the templating and dynamic-generation engine; it consumes Scatter Model's Jinja and dynamic-generation layer as its template engine, and it consumes the typed IR so that a template's slots are validated against a real model and a generated document cannot reference a field that does not exist. That is the same single-source-of-truth discipline that protects against the Disconnection, applied across two sibling brands: Scatter Model owns the template engine and the IR, Story Factory owns the document catalog, the grounding, and the human-in-control workflow on top, and neither duplicates the other (referenced per the-disconnection, not copied). The differentiation from the convergent incumbents is the connected primitive: SharePoint with Copilot, Box Doc Gen, and Templafy are each converging on templates plus governance plus AI, but none of them ships the template graph plus STORM-grade grounding plus the minimal-checkpoint workflow as one thing, and the sustainable edge is that combination plus the admin and authoring experience plus the analytics on time saved and consistency gained, rather than any single algorithm.

3c. Service (premium-at-accessible boutique delivery)

The service angle for Story Factory is document-production-as-a-service: produce a client's volume of structured documents at scale, deliver them grounded and consistent, and retain the relationship as the document operation becomes ongoing. The delivery moat is the template library and the grounding fabric, because once a client's document standards and data sources are encoded, every subsequent document is a matter of running a proven system with human oversight rather than from-scratch drafting.

The target operator is the Looikos canonical resolved to this domain: the sub-25-employee master-complex who is buried in document production. The market read locates this person precisely. They are the consultant or agency owner who produces every proposal and report from scratch and burns out on the volume, the compliance or operations person buried in repetitive structured forms and reports that are all required and none enjoyable, the grant-writer or bid-writer whose income depends on volume but each document takes days, or the small-business owner who needs professional contracts and statements of work and cannot afford a dedicated writer. These are masters of their domain who are not in the business of document production but are drowning in it, which is the master-complex profile, and the questionnaire-driven generation plus the grounding is the thing that lifts the document load off them without dropping the quality or the accuracy.

The engagement shape is the ecosystem standard. An audit at the start locks the scope (which document types, what volume, what grounding sources, what the checkpoint sign-offs are), and the platform quantifies the price against that audit so the client sees a predictable number. Premium quality at accessible pricing works here because the brand has pre-built the template catalog, the grounding connectors, and the agent harnesses, so delivering a client's document volume is running a proven system with expert oversight rather than artisanal consulting, which is the compression that lets one operator-architect deliver what a team of writers and document specialists would. The accessible-product tier sits around the $1-2k/month band and the retainers in the $2-12k+ band, and the service angle floors around $1M/month at the ecosystem-standard 100-to-250 retainer customers.

The commodity drafting beneath the premium engagements (routine form-fills, simple template population) gets partnered to the sister affiliate network, so service at scale is a network rather than a headcount problem, and the human operating model that runs the relationship is the shared-floor customer-success model (referenced from, not copied). There is a service-angle subtlety the market read surfaces: the strongest value proposition is not a single document but a coherent multi-document package (a proposal plus its statement of work plus its compliance form, all aligned on the facts and language), which almost no vendor markets, so the service positioning leans on the bundle and the cross-document consistency that the template graph makes possible, which is both the harder thing to deliver and the more defensible service to sell.

The retainer logic also depends on positioning the engagement as ongoing document operations rather than a one-time catalog build, because documents change as the business and its compliance landscape change, which is where the durable recurring value sits.

4. The personas (5+, modeled to world-experience depth)

Six personas, first person, at world-experience depth, carrying the pain in close-to-real document-worker language. The Lexicon of Pain below is representative voice: the voice-of-customer research drew on document-production guidance and pain-point sources rather than raw forum transcripts (it flagged this), with the emotional verbs (drowning, buried, stale, blank-page dread, monster proposal) source-supported as the language these roles use, so the phrases are tagged representative rather than documented quotes. The bias is toward the negative emotions, because that is where these people live.

P1. The consultant drowning in deliverable production

I am living in proposal hell. It is every night and every weekend just to get the decks and reports out the door, and I cannot face another blank page. I am not writing anymore, I am manufacturing deliverables. The work I am supposed to be paid for is the thinking, the strategy, the read on the client's situation, and instead I am spending the bulk of my hours turning that thinking into a polished document for the tenth time this month, reformatting, restructuring, making it readable and credible under a deadline that never moves.

How it hits my life and status: my value is supposed to be my thinking, but I am stuck doing production, and if I cannot keep up I will look incompetent or unhireable, so I keep absorbing the document load into my nights and weekends rather than admitting I am underwater. How I got here: the deliverable is how consulting proves its value, so every engagement demands a custom document, and the custom-every-time assumption is the trap because most of the structure repeats and only the substance changes. What it takes to get out: a system that produces the document from my thinking (intake the substance through a questionnaire, generate the structured grounded draft, let me review at checkpoints) so the production stops eating the thinking, which is exactly the questionnaire-and-checkpoint generation Story Factory is built on. Why most stay stuck: the production grind is normalized in the profession, so it reads as the cost of the work rather than a solvable defect, and admitting you need help feels like admitting you are slow. The cost of staying stuck is the nights and weekends, the burnout, and the quiet erosion of the thinking the client actually pays for. The cost to get out is letting a system manufacture the document so the human does the strategy.

P2. The compliance and operations person buried in mandatory forms

I spend my life filling out the same forms. It is the same report every month with a different date, and my whole job is boxes, fields, and checklists, mandatory paperwork that never ends and that mostly nobody reads but all of which is required. I am drowning in it, and the worst part is that the drudgery dulls me, so I am most likely to make the mistake that matters precisely when I am most numb to the work.

How it hits my life and status: if I miss one field I get flagged or blamed, and I am afraid of being the one who breaks compliance because I was too tired to care, so the work carries a low constant dread out of proportion to how boring it is. How I got here: the regulatory and operational machine demands these documents on a schedule, the documents are structurally near-identical month to month, and the system never invested in generating them because each one technically needs a human to certify it. What it takes to get out: grounded generation that fills the repetitive structure from the systems of record and surfaces only the fields that genuinely need my judgment at a checkpoint, which is exactly the grounding-fabric-plus-minimal-checkpoint shape Story Factory is built around and that the market read names as the correct pattern. Why most stay stuck: the work is mandatory and boring rather than urgent and interesting, so it never triggers a project to fix it, it just grinds. The cost of staying stuck is the numbness and the ever-present fear of the missed field. The cost to get out is trusting a grounded system to fill the structure so the human certifies rather than transcribes.

P3. The founder or PM whose documents have rotted

The docs are stale the second they are published. Nobody trusts the PRD anymore, we have three versions of the truth, and the spec does not match reality, so what is the point. Every time I sit down to update the documentation I find it has drifted so far from what we actually built that updating it feels like rewriting it, so I do not, and the gap widens, and the team stops reading the docs and starts asking me directly, which makes me the bottleneck.

How it hits my status and my life: if our docs are wrong the team is flying blind, and if people stop trusting the docs they stop trusting me to run the product, so the rot is not just a documentation problem, it is a credibility problem. How I got here: the document was written once at a moment in time, the product kept moving, and nothing kept the document synchronized with reality, so it decayed the way any unmaintained artifact decays. What it takes to get out: documents that regenerate from a current source of truth rather than being hand-maintained, so the PRD reflects the actual state because it is generated from it, which is exactly where Story Factory's grounding (generate from the systems of record) plus Scatter Model's single-IR meet, and it is the specific defense against the divergent-sources-of-truth failure the-disconnection names. Why most stay stuck: doc rot is invisible until a decision is made on a stale doc and goes wrong, so it never gets prioritized over shipping. The cost of staying stuck is a team that no longer trusts its own documentation and a founder who has become the human source of truth. The cost to get out is letting the document be generated from the live state rather than maintained by hand.

P4. The grant-writer or bid-writer under volume pressure

It is feast or famine, and one proposal can eat my whole week. I am always behind because every bid is a monster, and my income depends on how many I can get out the door, so the math is brutal: each document takes days, the days cap the volume, and the volume caps the income. Time constraints are the whole game, and the moment I take on enough work to make the month I am underwater on the deadlines, and the moment I protect my sanity I am one slow month from panic.

How it hits my life: I am scared I am always one slow month away from a financial hole, so I overcommit, and overcommitting means every bid gets less than it deserves, which lowers my win rate, which forces more volume, which is the loop. How I got here: the work is genuinely high-effort per document (a compelling narrative, the data and evidence, the budget, the compliance with the funder's rules and page limits) and it is priced and won per document, so the only lever I have is throughput and the only way to add throughput is my own hours. What it takes to get out: a system that holds the funder-specific templates and the grounding (the past proposals, the data, the boilerplate that is genuinely reusable) and generates the structured draft so I spend my days on the compelling-narrative judgment that wins rather than on assembling the structure that merely qualifies, which is the template-graph-plus-grounding shape Story Factory is built on, with the grant and RFP vertical being one of the clearest wedges the market read identifies. Why most stay stuck: the volume grind is the accepted reality of the trade, so the writer optimizes their own speed rather than questioning whether the structure should be generated. The cost of staying stuck is the feast-or-famine cycle and the win-rate erosion from spreading too thin. The cost to get out is letting the system assemble the qualifying structure so the human writes the winning narrative.

P5. The analyst who dreads writing up the report

Just write up the report makes my stomach drop. I can analyze all day, but the writing kills me, and I keep staring at the blank page, editing the first sentence for an hour, procrastinating on the part that turns the work into something anyone else can use. The analysis is done, the answer is in my head and my spreadsheets, and the distance between that and a clean readable document feels enormous every single time.

How it hits my status: if I cannot write it well people will think I do not understand it, and I am afraid the rough draft will expose me as less sharp than the analysis actually was, so perfectionism and procrastination feed each other and the report that should take an afternoon takes three days of dread. How I got here: I built my identity and my skill around the analysis, the thinking, the rigor, and the writing-up was always the tax at the end that nobody trained me for and that I quietly resent. What it takes to get out: a system that takes the analysis I have already done and the structure of the report type and produces a grounded first draft I can refine, which removes the blank page entirely, because the market read is explicit that humans vastly prefer reviewing and tweaking over drafting from zero and that this is exactly why first-draft generation has scaled. Story Factory's intake-the-substance-then-generate-the-draft loop is the direct answer to the blank-page dread. Why most stay stuck: the dread is private and recurring rather than a visible crisis, so it never gets named as a fixable workflow problem, it just gets endured every reporting cycle. The cost of staying stuck is the procrastination, the perfectionism spiral, and the analysis whose value is delayed or diluted by the writing bottleneck. The cost to get out is letting the system kill the blank page so the human edits rather than originates.

P6. The small-business owner who needs professional documents

I need real contracts, statements of work, and reports, and I cannot afford a writer or a lawyer to produce them, so I either copy-paste something off the internet that does not fit my situation, or I write it myself badly, or I do not produce it at all and operate on a handshake that bites me later. Every professional document I need feels like a choice between expensive, wrong, or absent, and I am running a real business on documents that would embarrass me if a real professional read them.

How it hits my status and my life: a sloppy or missing contract exposes me legally and makes me look small-time to the customers and partners I am trying to win, and I am ashamed that after years of running this I still do not have proper documents, so I avoid the situations that would require them. How I got here: professional document production was gated behind professionals I could not afford, and the cheap alternatives (generic templates, raw AI drafts) were either wrong for my situation or ungrounded, so I never had a path to documents that were both accessible and correct. What it takes to get out: a system that holds professional-grade templates, intakes my specific situation through a questionnaire, grounds the document in my actual business facts, and lets me review it at a checkpoint, which delivers professional-quality documents at accessible pricing, the exact premium-at-accessible promise of the service angle. Why most stay stuck: the choice between expensive, wrong, and absent has no good option, so the owner picks the least-bad one and lives with the exposure. The cost of staying stuck is the legal exposure and the small-time perception. The cost to get out is trusting an accessible system to produce documents that a professional would respect.

5. The world model (run the PST framework)

The six personas share one suffering loop, and modeling it as a single problem-story is what turns the deck from a feature list into PST. Echolocate, locate the Problem, reconstruct the Story, design the Transformation.

Echolocate the world. The buyer lives inside a document-and-knowledge-work ecosystem under a structural squeeze. On one side is the demand for documents, which only grows: every deal needs a proposal, every cycle needs a report, every regulation needs a form, every product needs a spec, and the volume rises with the complexity of the business. On another side is the supply of document production, which is still mostly expensive human hours, because the document has historically required a person to author it and to stand behind it. On a third side is the new machine option, which arrived loud and disappointed: the ungrounded language-model copilot writes fluently and hallucinates, so the very thing that promised to relieve the document load introduced a new fear, the fear of the confident-and-wrong document. Read it as an M&A firm reads a target and the leverage is clear: document production is a large, permanent, mission-critical cost that the market has tried to automate for decades (the document-automation, contract-lifecycle, and AI-writing categories all exist because this pain is real and old), and the unmet need is grounded generation at breadth with the human kept in control, which is exactly the gap.

Locate the Problem (the cycle of suffering). The pain that arrives is the endless structured-document production: the proposal hell, the monthly form drudgery, the rotting PRD, the monster bid, the blank page. In response a fear gets installed, and the document-worker's fear portfolio is specific. The fear of the deadline (the document that must ship tonight), the fear of inconsistency exposing sloppiness (the missed field, the version that contradicts another version, the draft that reveals you as less sharp than your analysis), and the fear of the document that is wrong and binds you (the contract that bites, the compliance miss, the spec the team trusted and should not have). Those fears drive avoidance, which here takes the form of grinding harder rather than systematizing: the consultant absorbs the production into nights and weekends, the analyst procrastinates and perfects the first sentence, the founder stops updating the docs, the grant-writer overcommits. The avoidance produces the unfavorable outcome (burnout, drift, the win-rate erosion, the stale doc), and the outcome produces shame, the belief not I have a document-workflow problem but I am someone who cannot keep up, who is secretly disorganized, who is less capable than the role requires. The shame is buried under cope: blame the volume, blame the client's deadlines, blame the process, blame the regulation. The red line, the move forbidden, is accountability, because accountability means admitting that the document production was never systematized and that the grind was a choice driven by the belief that every document must be bespoke and hand-made. The refusal opens a blind spot, the blind spot produces the next bad action (another from-scratch deliverable, another deferred doc update, another overcommitted month), and the loop closes and compounds into deeper burnout and deeper doubt.

Reconstruct the Story. The belief structure under the loop is some version of the real work is the thinking and the document is just typing it up, paired with every document is bespoke so it has to be made by hand. The emotional-experience chain that built it is the knowledge-worker one: the person was rewarded for the quality of their thinking (the analysis, the strategy, the expertise) and the document was always the afterthought, the unglamorous tax at the end, so producing it well was never the identity and systematizing it was never the priority. That belief drove actions (write each document from scratch, treat the production as a personal grind, never invest in the structure), the actions produced results, the results became habits, and the habits anchored into an identity where the worker's value is their thinking and the document is beneath it, which is precisely the belief that keeps them trapped in the production. The origin layer, where it gets intimate, is the craft-versus-throughput wound: somewhere the person learned that the thinking is what is valued and the producing is menial, so investing in document production feels like admitting the menial part is real work, and asking for help with it feels like admitting they cannot handle the menial part either. That is the uncomfortable place most of them run from. On the Hawkins scale used descriptively, the shame, the deadline-fear, and the pride-in-the-thinking sit in the destructive band below the courage line, fueling the loop.

Design the Transformation. The bridge across hinges on courage. The first step is truth, and the uncomfortable truth is that the document is the product, the thing the client or the team or the funder actually receives and acts on, so treating it as beneath the thinking is what keeps the thinking trapped inside the production grind. The second is responsibility, owning the reaction rather than the circumstance: the worker did not create the document demand or the disappointing copilots, but they own whether they keep letting the every-document-is-bespoke belief drive the hand-made grind. The third is healing, which hurts because it means letting go of the identity that the producing is beneath them and admitting that the structure was reusable all along, the way the consultant admits most of the proposal repeats and only the substance changes. The fourth is forgiveness, releasing the verdict that needing help with production is a personal failing, forgiving the nights and weekends and the rotted docs and the overcommitted months, and learning from it, which opens the eyes to the new truth that being the person who designs the document system is a larger role than being the person who hand-makes each document. Story Factory's offer is calibrated to that bridge: the questionnaire intakes the thinking so the human supplies judgment not typing, the grounding kills the hallucination fear, the template graph kills the inconsistency fear, the checkpoints keep the human in control so the document that binds is one they signed off on, and the breadth means the whole document operation lifts rather than one document type. Most of the content lives in the negative band, the grind and the dread and the shame, because that is where the audience lives, with the systematized, grounded, human-in-control document operation shown as the reachable other side. That is the Echolocation architecture applied to the person whose document load is quietly consuming the work they are actually good at.

6. Competitive and market read (the alpha / third door)

The competitive field is fragmented at the edges and empty at the center, the now-familiar Looikos market shape in the document domain. Map it by cluster, by what each refuses, and by where the third door is.

Who else does this, and what they will not do. Four clusters plus a convergent threat. The document-automation and assembly tools (HotDocs, Conga, Templafy, airSlate, Quark, Box Doc Gen, SharePoint structured generation) each do deterministic merge well and stop short of grounded reasoning. HotDocs does rules-based assembly for compliance-heavy legal and financial documents but has a steep technical authoring curve and little generative drafting. Conga generates quotes and proposals from Salesforce data but is Salesforce-centric and merge-first. Templafy enforces brand and compliance consistency in Microsoft Office documents but emphasizes governance over agentic multi-step generation and is not questionnaire-driven multi-document orchestration. Quark handles XML and component-content-management structured authoring for regulated documents but is heavyweight and aimed at pharma and technical documentation, not everyday business documents. The consistent refusal across this cluster is grounded reasoning: they do safe-but-dumb merge, not STORM-style plan-fetch-draft-validate. The proposal-and-report tools (PandaDoc, Proposify, Qwilr, Better Proposals) build beautiful proposals but are narrow to the sales-proposal-and-contract domain, treat AI as a copy-assistant rather than grounded reasoning, and have little concept of a questionnaire-driven multi-document package. The AI-writing platforms (Jasper, Writer, Copy.ai) are optimized for unstructured marketing copy and the blank-page assist, not deterministic structured generation with traceable grounding, and they ship prompt-pattern templates rather than deeply structured forms with logic. The document-as-workflow tools (airSlate, SharePoint plus Power Automate, Box) implement the form-to-document-to-approval pattern but treat it as orchestration-layer logic rather than a document-native primitive, and they are weak on narrative sophistication and cross-document consistency. Across all four clusters, the consistent gap is the same: nobody combines template breadth, STORM-grade grounding, and a first-class questionnaire-and-checkpoint workflow as one connected primitive, and almost nobody markets the coherent multi-document bundle.

The convergent threat, named honestly. SharePoint with Copilot and Power Automate, Box Doc Gen, and Templafy are all converging on the same shape (templates plus governance plus AI), and while they are not STORM-grade today they can add better grounding over time, and the office suites have internalized generic generation already. This is the most important competitive fact in the deck, and the honest read is that the sustainable edge is not the underlying grounding algorithm, which incumbents can copy, but the connected combination plus the verticalization plus the admin-and-authoring experience plus the analytics on time-saved and consistency. Story Factory's defensibility has to rest on being the connected primitive done deeply and on owning specific high-value verticals (the security-and-compliance document factory, the professional-services proposal-bundle factory) rather than on a single feature, and the deck states that rather than pretending the algorithm alone is a moat.

The third door. Alpha is the thing competitors know about and will not do, and Story Factory's alpha is the connected combination of four moves that the field ships separately: the template graph (cross-document consistency, a bundle that agrees with itself, which almost no vendor markets), STORM-grade grounding baked into the core (reliability and traceability, not AI-inside), the minimal-high-signal questionnaire-and-checkpoint workflow as a doc-native primitive, and the breadth across the whole document catalog. The market read sharpens the alpha from the abstract version to the defensible one: the wedge is a document-package engine that lets non-engineers declaratively design question-driven workflows generating grounded multi-document bundles from live systems of record, with built-in agent reasoning and human checkpoints and analytics, which is the same four moves stated as a buildable product. The reason competitors will not connect the four is structural: the merge tools are organized around deterministic assembly and will not add real reasoning, the proposal tools are organized around one vertical and will not broaden, the AI-writing tools are organized around unstructured copy and will not add structure and grounding, and the office suites will add pieces but not the deep connected primitive. Connecting the four requires a builder willing to do the unglamorous grounding-and-workflow depth across the whole catalog.

Wardley evolution and the own-versus-rule call. Single-document generation and deterministic merge are product-to-commodity, rent and compose, never custom-build (Story Factory uses Scatter Model's template engine and the existing format-and-export tools as components). STORM-grade grounded generation, the template graph with cross-document consistency, and the document-package engine are genesis-to-custom: novel, differentiating, load-bearing, the thing competitors know about but will not connect, which is the own-and-build capability where the alpha lives. The systems-of-record connectors and the grounding fabric are custom-to-product: build the mapping discipline, compose the individual connectors. The minimal-checkpoint workflow is custom: own the human-in-the-loop design because the market read shows getting it wrong (cluttered approvals) inverts the value.

Market size and demand signal. Triangulate, because there is no clean TAM for grounded-document-bundle generation. The cross-cutting addressable space (contract-lifecycle plus proposal and RFP plus document automation, overlapping enterprise content management) is defensibly above $5B by mid-decade, with the CLM neighbor alone around $3-to-$3.5B in 2025-26 at roughly 12-13% CAGR and the AI-content-generation market in the low single-digit billions growing fast. The demand is revealed and old: enterprises have invested in document automation for decades (HotDocs in law and finance, Quark in regulated documentation, the CLM category's steady growth), which is direct evidence that repetitive document production is a real and durable pain, not a speculative one. The category comps confirm the ceiling: Jasper at a reported ~$1.5B, Ironclad above $3B at peak, Icertis at several billion, the Conga-Apttus merger setting the integrated-stack baseline. Demand is proven by decades of partial-fix investment, the grounded connected fix is unbuilt, and the enterprise is actively shifting from manual authoring to agentic orchestration, which is the wave the brand rides, tempered by the named incumbent-convergence clock.

7. The build (what this brand needs, where Track R feeds Track P)

Story Factory is concept-stage, so the build section is more provisional than the live brands, but the shape is well-determined because the brand sits on top of siblings whose architecture is known and because the market read specifies the load-bearing requirements.

What it is built from. The template engine is Scatter Model's Jinja and dynamic-generation layer, consumed rather than rebuilt, with the typed IR so that a template's slots are validated against a real model. The grounded-generation engine is a STORM-inspired agent pipeline on LangGraph: plan the document, fetch the facts from the systems of record before drafting, draft, validate against sources, and log citations, which is what turns fluent-but-wrong into grounded-and-traceable. The intake is the dynamic-forms capability shared across the ecosystem, driving the questionnaire that replaces the blank page. The checkpoint-and-review workflow is durable execution on Inngest, because a multi-step human-in-the-loop generation that pauses for sign-off is exactly the long-running durable-workflow case, and the market read insists the checkpoints be minimal and high-signal. The export-and-format layer renders to the document formats the customer needs. The grounding fabric, the schema-aware connectors to CRM, ERP, governance repositories, and knowledge bases plus the mapping UI, is a first-class build requirement rather than an add-on, because the market read is explicit that without it the platform degrades into a smart template layer that still needs manual data-copying.

One document-generation core, surfaces many. The generation operations live in a core that never imports a transport, and the questionnaire UI, the MCP server, the CLI, the API, and the batch engine are all thin adapters over it. This is the same core-one-surfaces-many pattern the ecosystem runs on, and for a document-generation brand it is also the defense against the specific failure the brand exists to solve: if the core holds the one authoritative generation logic and the template graph holds the one authoritative relationship between documents, then a generated bundle cannot contradict itself, which is the divergent-sources-of-truth failure the-disconnection names, solved structurally.

The data models. Template, Slot, DocumentType, DocumentBundle, Questionnaire, Checkpoint, GroundingSource, and GeneratedDocument as ECS-shaped Pydantic-IR records. The template graph is the load-bearing data structure, because the relationships between document types (this statement of work must agree with this proposal; this compliance form must reflect this system description) are first-class edges, which the market read names as the differentiator over flat templates.

The agent roster the domain needs. Four feature factories, each a set of harnesses plus a gateway. The intake factory (the questionnaire that drives generation). The grounding-and-research factory (the STORM-style planner plus the systems-of-record connectors). The fill-and-draft factory (the agentic generation that populates the template graph consistently). The checkpoint-and-QC factory (the minimal-high-signal human review plus the consistency validation across a bundle). Each is the custom-modular-composable-harness pattern the Harness V2 build provides (referenced from, not copied), and the grounded-generation discipline is shared with Wardley Swarm's STORM-inspired map agents (referenced, not copied).

The medallion tiers. Applied to template and document maturity: a bronze draft template, a silver validated-and-grounded template with mapped data sources, a gold template with cross-document-consistency edges and a governed review history, and a diamond certified template that is the source of truth for a document type in a regulated or high-stakes context. The customer's access tier maps onto template tier, and the governed-certification loop is where the durable value sits, which the market read corroborates.

Where Track R feeds Track P. Track R has not started. The shape of the need is nameable: Story Factory will want the best harvested patterns for STORM-style grounded generation (whatever the Track-R research-and-writing-agent repos teach), for the durable human-in-the-loop workflow (shared with the harness and with WikiDesignCo's Inngest layer), for the systems-of-record connectors and the grounding fabric (shared with WikiDesignCo's ingestion and with Spider Scrape), and for the document-format-and-export layer. When the repo decks exist at, the value rubric ranks the combined wish-list and the specific capabilities slot in here.

8. Priority read (feeds the value rubric)

Story Factory is a primitive (every brand and every customer generates documents) but its priority is shaped by two dependencies that matter for sequencing. It is downstream of Scatter Model, because it consumes Scatter Model's template and dynamic-generation engine and the typed IR, and it is parallel to PRD Master, which is Story Factory specialized to operational and spec documents. On the promise-dependency graph it is a high-leverage node whose foundational promises (the template engine, the grounded-generation discipline, the durable workflow) come partly from Scatter Model and the harness, so it is gated on those rather than free-standing.

Readiness is the honest constraint, the same as Scatter Model: concept-stage, no standalone repo, so readiness sits below leverage, and the priority read holds that gap rather than letting the strong thesis imply near-shippability. The PRD Master specialization existing in the tree is a partial readiness signal (the specialized practice runs), but the general primitive is unbuilt.

The first-pass tiering, capability by capability:

• Next (build and own, gated on Scatter Model and the harness): the document-package engine, the template graph with cross-document consistency, and the STORM-grade grounded generation. These are genesis-stage, load-bearing, the alpha competitors will not connect, and high leverage across every brand's document needs. They are Next rather than Now because they depend on Scatter Model's template engine being productized and on the harness running the durable human-in-the-loop generation reliably. Routes Powell-VFA: substrate-shaping, score the discounted future.
• Next (the grounding fabric): the schema-aware systems-of-record connectors and the mapping UI, which the market read names as a first-class requirement (without it the platform is a smart template layer), gated on the same dependencies.
• Watch (probe and verticalize before broad investment): the breadth-across-the-whole-catalog ambition. The market read warns that maintaining hundreds of high-quality templates is expensive and that the edge is more the authoring speed and the encode-once grounding than the raw count, so the safe path verticalizes first (own a security-and-compliance or professional-services document factory) and probes demand before going broad. Genesis-and-uncertain, route to a probe.
• Leave (rent and compose, never custom-build): single-document generation, deterministic merge, format-and-export, generic AI-writing. Commodity or product. Compose Scatter Model's engine and the existing tools.

Run the seven-sins gate. Pride or look-ahead: the read scores the brand concept-stage and the connected-primitive as a bet, and names that incumbents can add grounding over time, so it does not score as if the moat already shipped. Envy or survivorship: the failure modes are in the deck (the breadth-versus-depth cost, the incumbent-convergence clock, the cluttered-checkpoint risk, the manual-data-copying degradation), not just the upside. Gluttony or overfitting: the enthusiasm is capped to the proven specialized sibling and the verticalized wedge, not inflated by an abstract hundreds-of-templates count. Sloth or transaction-cost: the build friction (the grounding-fabric connectors, the durable-workflow reliability, the template-graph consistency) is named as the gate. Wrath or regime-blindness: the read assumes the 2026 shift-to-agentic-orchestration regime, which is moving toward the brand, and flags that the same movement brings convergent incumbents. Lust or capacity delusion: Story Factory is one primitive with a verticalized initial wedge, not an attempt to own every document type at once. Greed or fat-tail: the tail risk is an office-suite incumbent (SharePoint plus Copilot) extending into the grounded-bundle space first, which is why the differentiation must rest on the connected primitive plus verticalization plus experience rather than the algorithm, routing VFA. The dependency to flag for the strategist: Story Factory's leverage is high and its readiness is low and it is gated on Scatter Model, so it is a strong Next that should sequence after Scatter Model's template engine is real, and the smart first move is a single high-value vertical rather than the full catalog.