Wardley Swarm · Looikos

Project: Wardley Swarm
Looikos cluster: Technical Infrastructure (the decision-and-strategy-modeling primitive)
One-line: A simulation and strategy station that runs agentic brainstorming and Wardley mapping grounded in a unified analytics framework (promise theory, game theory, Bayesian reasoning, Powell's four policy classes, Convergence Flow), with STORM-inspired agents so the maps are trustworthy enough to power downstream content and decisions.
One-line: The decision-and-strategy-modeling primitive: build a strategic map (a chessboard of the situation) that other systems can act on.
Status: Concept (no standalone repo; the analytical frameworks run internally via the convergence-flow and value-rubric tooling; the productized strategy-simulation station is not yet built)

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

Wardley Swarm is the Looikos ecosystem's building block for modeling decisions and strategy, and a self-standing brand that produces rigorous strategy as a reusable artifact you can buy. In plain terms, AI agents build a strategic map of a situation (a chessboard that shows where the pieces are and where they're evolving), run brainstorming and simulations across that map, and ground every element in evidence, so the output is a defensible strategic model rather than a slide or a guess. The analytical spine weaves several frameworks together: Wardley mapping for evolution and situational awareness, promise theory for the dependencies between capabilities, game theory for the competitive dynamics with other players, Bayesian reasoning for confidence under uncertainty, Warren Powell's unified decision framework and its four policy classes for how to act on a decision, and the Convergence Flow backbone that ties them together. The agents are modeled on STORM, Stanford's grounded-research algorithm, so the maps are trustworthy enough to power downstream content and decisions instead of ending as one-off artifacts. High-stakes strategy gets produced two bad ways today. Either it's done by gut, by slides, and by expensive consultants who deliver a static deck and leave, or it comes out of an ungrounded language-model brainstorm that knows the frameworks' vocabulary, enforces none of their rigor, and sounds strategic while meaning nothing. The market research behind this deck confirms both failure modes and the gap between them: the strategy-mapping niche is under-tooled and under-capitalized relative to its importance, the existing Wardley tools are artisanal diagram-drawers with no reasoning or data, the decision-intelligence platforms own data and workflows but expose no explicit strategy frameworks, and the LLM copilots are ungrounded brainstormers rather than defensible strategists. Wardley Swarm sits in that empty space, offering rigorous multi-framework reasoning at the scale agents allow, grounded STORM-style so it holds up under challenge, with the strategic map kept as living, reusable data that powers the rest of the ecosystem. It's built for operators, founders, and strategists who make high-stakes decisions under uncertainty and currently have to choose between an expensive consultant and an ungrounded brainstorm. Wardley Swarm is concept-stage today, with no standalone repo, though its method already runs internally as the value rubric (the scoring method that ranks this research program's work), so the brand is the productization of a discipline the ecosystem demonstrably already uses on itself.

Andy's words from the canonical recorded breakdown, verbatim and lightly de-duplicated, not paraphrased:

Wardley Swarm. This is a simulation station kind of situation where what [Wardley] Swarm does is it'll go and do like brainstorming and [Wardley] mapping using grounded in my analytics framework with promise theory, game theory, Bayesian theorem, Professor Warren Powell's unified decision framework. The idea is to weave these all together with the other systems, like the convergence flow framework, my own patterns, and weave that all together into building actual, almost like a chessboard or a map. But in [Wardley] Swarm you have agents where it's built on, designed and inspired by Storm, the algorithm from wiki [that knows] how to write articles... [Wardley] Swarm is what we're going to be able to do these [Wardley] maps and just people just quickly see the stuff and now they can trust it to go empower and populate content generation.

(Note: the ecosystem overview is a stub and carries no separate Wardley Swarm seed, so the transcript above is the canonical one. Decompressed, the seed describes a simulation-and-strategy station that runs brainstorming and Wardley mapping grounded in the unified analytics framework, weaves in the Convergence Flow backbone, and builds a chessboard-style strategic map with STORM-inspired agents so the maps can be trusted to power downstream content. That makes it the ecosystem's building block for modeling decisions and strategy.)

Reading between the lines. Three things sit compressed in that seed, and the market research confirms each is real and unoccupied.

The first is that the unified analytics framework is the product, not a list of buzzwords, and each piece does a specific job that the others can't. Wardley mapping supplies evolution and situational awareness, placing each capability on the genesis-to-commodity axis so you can see what to build, rent, or harvest. Promise theory supplies the dependency structure, modeling what each component promises and what it relies on, which is how you sequence and how you find the foundational nodes. Game theory supplies the competitive dynamics, modeling the other players (competitors, partners, regulators) as actors with strategies and payoffs rather than as scenery. Bayesian reasoning supplies confidence under uncertainty, tracking what you know about what you know and updating as evidence arrives. Powell's unified decision framework and its four policy classes supply the how-to-act layer, routing each decision to the right machinery (a rule, a tuned policy, a downstream-value calculation, or an explicit simulation) so you don't bring a simulation to a lookup-table problem. The Convergence Flow backbone is Andy's structure for weaving them together. The research confirms this combination exists nowhere: the decision-intelligence platforms have powerful models but implicit strategy logic that never exposes Wardley or Powell or game theory as first-class objects, and the LLM copilots know the vocabulary but enforce none of the structure.

The second is the chessboard, the strategic map the system outputs, and it's more than a diagram because it's meant to be living, reusable data rather than a one-off artifact. The research names this the biggest structural gap in the whole space: no one has turned strategy into a shared, machine-readable substrate, a strategy ontology with nodes (activities, components, actors), edges (value-chain links, dependencies, power relationships), and attributes (evolution stage, uncertainty, policy class, Bayesian priors and posteriors) that agents continuously update and that downstream systems consume as an input. Wardley Swarm's chessboard is that strategy-as-data, and it's what connects the brand to the rest of the ecosystem: the map feeds the metagraph (the strategic model becomes nodes and edges in WikiDesignCo's world-model), and the map feeds the content engines (a grounded strategic map behind a piece of content is what makes the content defensible rather than vibes).

The third is the STORM lineage, which is what makes the maps trustworthy enough to be load-bearing. STORM grounds generation by planning, fetching evidence before drafting, and validating against sources, and applied to strategy it means every map element and every recommended move is traceable to evidence, with a provenance graph showing which agents and sources led to which conclusion, and the ability to interrogate the map adversarially (why is this component in product stage and not commodity, show me the evidence and the counter-evidence). The research names this ability to trace and cross-examine the map as a strong differentiator from both the black-box decision models and the ungrounded copilots. Story Factory uses the same STORM discipline for documents, which is why the two brands are siblings: Story Factory produces the trustworthy document, Wardley Swarm produces the trustworthy strategic map, both on the same grounded-generation backbone, and the map can drive the document. Wardley Swarm is also the method behind the value rubric, sits downstream of WikiDesignCo's metagraph, and is a peer of Scatter Model, whose intermediate representation (IR) gives the map data its types. This deck points to those four siblings rather than restating them.

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

3a. Finance (credit and capital access)

The finance read on Wardley Swarm sits against an unusually large and high-margin backdrop, because the activity it productizes (strategy) is one of the most expensive services in the economy and one of the least disrupted by software so far.

The economic activity has three meters: a seat or subscription meter for the operators who build and explore maps, a usage meter billed in credits for the agentic simulation and mapping, and a premium-advisory meter for the service engagements where the platform plus an expert delivers strategy. Because Wardley Swarm is concept-stage with no live revenue, any throughput figures for those meters are projections, and the deck treats them that way. What can be anchored is the quality profile of strategy and decision-intelligence software: it embeds in the planning cycle, which is mission-critical and annual, so retention is strong and switching is painful once the strategy map becomes the shared source of strategic intent. Annual recurring revenue (ARR) of that quality is what a revenue-based-financing desk or venture-debt lender lends against, and the strategy-as-system-of-record positioning makes the forward revenue forecastable. The capital path is the standard one for high-value vertical decision software: private venture early, with the possibility of premium-priced enterprise contracts (strategy buyers pay consultant-tier rates) lifting revenue per account well above typical SaaS.

The M&A and valuation comps are named and post-2020, and they bracket the opportunity from both the software side and the services side. On the software side, Palantir, the closest high-stakes-decision-platform comp, has carried a market cap in the $30B-to-$60B range in the mid-2020s; Quantexa reached unicorn status above $1B by 2023; Aera Technology is estimated in the $1B-to-$2B range; Pyramid Analytics in the mid-hundreds of millions; and the decision-intelligence and advanced-analytics TAM is triangulated at $30B-to-$50B by 2026. On the services side, which is the demand Wardley Swarm displaces, the global management-consulting market is estimated around $900B-to-$1T, strategy consulting specifically around $100B-to-$150B, and McKinsey, BCG, and Bain together generate on the order of $25B-to-$35B in annual revenue, with strategy work remaining extremely high-margin and largely artisanal. The research also surfaces a signal in what's missing: there's been no large public acquisition of a Wardley-mapping or strategy-mapping tool, which is itself evidence that the strategic-mapping niche is under-tooled and under-capitalized relative to its importance. Stated as a financial fact, the white space is enormous spend on strategy, large spend on decision data, and almost nothing bridging the two with software.

Run the $10M the ecosystem expects from each angle against those comps and the conclusion is the strongest of any infrastructure brand in the ecosystem so far: $10M is what the service angle alone floors at, and a brand that displaces even a sliver of a $100B-to-$150B strategy-consulting market while sitting in the same category as a Palantir or a Quantexa has a ceiling far above that. The concept-stage discount applies in full: Wardley Swarm has no ARR, so it's valued today on the strength of the thesis, the proven internal method (the value rubric), and the category comps, not on a revenue multiple, and the deck projects no fictional ARR.

A market-maker's three-level read (fundamentals, technicals, sentiment) closes the finance case. The fundamentals are the strong retention of strategy-as-system-of-record plus the consultant-tier pricing power, unproven for this specific brand. The technicals are the land-and-expand from one strategic question to the ongoing strategy operation. The live sentiment is a large and specific tailwind: the AI-adoption moment has created exactly the high-stakes-decision-under-uncertainty pain Wardley mapping was invented for, the literature explicitly frames AI-without-strategy as costly chaos, and enterprises are spending heavily on decision and simulation tooling to de-risk autonomous decisions. Sentiment is moving toward rigorous, grounded, defensible strategy as the cost of getting strategy wrong rises, which is the most favorable reading a young brand in this category can get, tempered by one risk: the brand must integrate with the existing data and decision stacks rather than become another silo.

3b. Software (the interface stack)

Software is the core angle for Wardley Swarm, because the brand turns strategy from a one-off consulting deliverable into a living software artifact. The product is one strategy-modeling core exposed through many surfaces, built on hexagonal architecture, where a single core sits behind a thin adapter for each surface.

The surfaces map to revenue lines. The visual strategy-map and simulation canvas, the executive cockpit where a human explores the map, runs scenarios, and selects moves, is the SaaS subscription surface, and the research is emphatic that world-class executive UX could itself be the primary wedge, because the real pain is often the lack of a shared, defensible narrative about the landscape under uncertainty, more than a lack of data. The MCP server (Model Context Protocol, the standard way agents call tools) is the agent-native surface, billed in credits, where other brands in the ecosystem and outside agents query and build maps programmatically. The CLI and the API support a credit-and-subscription program. The map-as-data export is the surface that makes the brand a primitive rather than a destination: the strategic map is a structured, versioned, queryable object that downstream systems (the metagraph, the content engines, roadmapping and OKR tools) consume as an input, and that export is the answer to the strategy-as-data gap the research names as the biggest in the space.

The platform breaks into feature factories with clean domain boundaries, and five are visible in the seed and the research. The framework-library factory encodes Wardley, promise theory, game theory, Bayesian reasoning, Powell's four policy classes, and the Convergence Flow backbone, each as an analytical module rather than a textbook reference, which is the part no mainstream tool has. The mapping factory holds the agents that build the value-chain-and-evolution map as first-class data. The simulation-and-council factory runs the agentic brainstorming and wargaming, where agents play out competitor moves, regulatory shocks, and tech shifts on the map, which the research identifies as a strong, distinct edge over static-analysis tools. The grounding-and-provenance factory carries the STORM-style evidence pipeline, the provenance graph, and the tools for cross-examining the map. The map-to-content-and-decision export factory feeds the map-as-data to the metagraph and the content engines and pushes decisions back into planning tools. Each factory follows the modular agent-harness pattern from the ecosystem's shared harness build, the software that runs its agents.

The research sharpens the software architecture in three ways, and the deck builds each one in. First, the integration risk: the brand must plug into the existing data and decision stacks (Palantir, Snowflake, Quantexa, the EPM and planning tools) and sit at the strategy layer, pulling data and models from them, building the map and the simulations on top, and pushing decisions back, so that it becomes the system of record for strategic intent rather than another data silo competing head-on. Second, the executive-UX requirement: the workflows must match how real founders, executives, and boards make decisions, with structured-dissent features (red-team agents, scenario branches, constraints) and automated board-ready outputs drawn from the live map, instead of stopping at frameworks drawn as textbook shapes. Third, the verticalization path: strategy frameworks are generic but adoption isn't, so the software ships pre-baked ontologies and priors for a turbulent high-stakes vertical (AI adoption, fintech, energy, defense), the canonical Wardley building blocks and typical Powell policy classes and typical game structures for that vertical, which is how it gets defensible traction and proprietary data. Together they give the thesis an engineering shape that can ship.

What sets Wardley Swarm apart is the connected combination, and the research confirms nobody else occupies that space: a strategy operating system that encodes multi-framework strategy reasoning, uses agentic STORM-grounded workflows to tie every map element to evidence and simulation, and treats the strategic map as a living versioned auditable data model that powers downstream systems, exists nowhere today. The Wardley tools draw diagrams with no reasoning, the decision platforms model data with no explicit strategy frameworks, the simulation platforms test agent performance rather than strategic positioning, and the copilots brainstorm without grounding. Wardley Swarm is the assembled whole, and the map-as-data is what makes it infrastructure for the rest of the ecosystem rather than a standalone tool. The map data is typed through Scatter Model's IR and lives in WikiDesignCo's metagraph, so the strategy layer connects to the world model instead of duplicating it, which is the ecosystem's rule against drifting duplicate copies applied across its infrastructure brands.

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

The service angle for Wardley Swarm is strategy-consulting-as-a-service: deliver rigorous Wardley maps, strategic analysis, and decision frameworks as a productized retainer, at a fraction of the cost of a tier-one consultancy. The delivery moat is the framework library, because consultant-grade rigor that's pre-encoded and agentically scaled is the thing that lets one operator-architect deliver what a strategy team would.

The target operator is the ecosystem's standard customer applied to this domain: the owner of a business with fewer than 25 employees, a master of a craft who needs strategy and can't buy it. The research locates the gap. Strategy consulting is artisanal, high-margin, and priced at seven-figure engagements and consultant day-rates, so the founder or operator of a small business is structurally locked out of the rigor that the large enterprises buy, even though the small operator faces the same high-stakes decisions under uncertainty and often with less margin for error. These owners aren't strategists by training and can't afford one, and the productized framework library plus the agentic mapping is what brings consultant-grade strategy within their reach.

The engagement follows the ecosystem's standard shape. An audit at the start locks the scope (which strategic question, which decision, how deep the simulation, what the deliverable is: a one-time map, an ongoing strategy retainer, a board-ready memo cycle), and the platform quantifies the price against that audit. Premium quality at accessible pricing works because the brand has pre-encoded the analytical frameworks and the grounding pipeline, so delivering a client's strategy is running a proven rigorous system with expert oversight rather than reinventing the analysis each time, which is the compression that lets the brand price below a consultancy while delivering comparable rigor. 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 strategic work beneath the premium engagements (routine landscape scans, standard framework applications) gets partnered to the sister affiliate network, and the human operating model that runs the relationship is the ecosystem's shared customer-success model. The research surfaces one more point that matters unusually for strategy: the durable recurring value comes from strategy provenance and ongoing decision stewardship, because boards and regulators increasingly want an audit trail of why a strategic decision was made (why invest in capability X, why exit market Y), and a platform that holds map snapshots over time with their evidence and simulations becomes valuable as a governance and traceability layer that outlasts any one-time analysis. That turns the service from a deliverable into an ongoing relationship where the platform holds the client's strategy of record, which is what makes the retainer durable, and it's the service-side version of the same map-as-living-data that defines the software angle.

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

The six personas in this section speak in the first person, in close-to-real language, and in enough depth to show how each one lives the problem. Their language is representative voice: the source flags some phrasings as actual-ish (close to real Reddit and founder-forum wording) and others as constructed-but-realistic, so the language is tagged representative rather than presented as documented quotes. The bias is toward the negative emotions, because that's where these people live, and the decision-weight fear is unusually heavy here because the stakes are existential.

I feel like I'm one bad bet away from nuking the whole company. Everyone keeps saying trust your gut, but my gut is terrified. It's 3am and I'm lying there thinking, am I steering us into a wall and nobody else sees it yet. The worst part is everyone thinks I'm confident, and inside I'm just picking a door and praying, because every big strategic decision feels like roulette with my team's salaries on the table. Pick the wrong market and we burn eighteen months and die, pick the right one and we're heroes, and I have no structured way to know which is which.

Investors want conviction, my team wants clarity, customers want a roadmap, and I'm the only one who knows I'm mostly guessing, so I carry the performance of certainty over a private terror. I got here because the decisions are genuinely high-stakes and irreversible (there's no undo button, you don't get to rewind twenty-four months of burn) and I have no rigorous way to compare directions, so I default to gut and storytelling and call it vision. Getting out takes a structured, defensible way to model the landscape and the moves, to see the chessboard and play out the timelines with evidence rather than in my head at 3am, which is the strategic map plus simulation that Wardley Swarm builds, and the research confirms the real pain is the lack of a shared, defensible narrative under uncertainty, more than a lack of data. Most founders stay stuck because admitting you're guessing feels like admitting you're not qualified to be the founder, so they protect the bravado at the cost of the rigor. The cost of staying stuck is the sleepless existential dread and the genuine risk of the company-killing bet. The cost to get out is admitting the vision was partly survivorship-bias cosplay and choosing rigor over the performance of certainty.

P2. The strategist whose frameworks are trapped in slides

I spend weeks building beautiful decks that end up as attachments nobody opens. My framework is a sixty-page slideshow I re-hack together every time a client asks basically the same question, everything is bespoke and manual, and by the time I finish the analysis the moment has passed. We keep selling strategic insight, but the actual process is me at 1am copy-pasting slides from three old projects, and the stuff that makes us look smart doesn't scale at all, it's all in my head and in random decks. I'm re-solving eighty percent of the same problems with no system to reuse the thinking.

It's demoralizing to watch leadership ignore my recommendations because by the time they see them the moment has passed, and I'm quietly afraid that my expertise is mostly packaging and performance rather than reproducible value, that I'm a highly paid slide monkey rather than a real strategic partner. I got here because strategy was always delivered as a bespoke artisanal artifact, the slide deck, so the intellectual leverage never got built, and the IP stayed trapped in decks and in my head where it can't scale. Getting out takes a strategy engine that encodes the frameworks as reusable modules and produces the map as living data, so the thinking compounds across engagements instead of being rebuilt each time, which is what Wardley Swarm's framework library and map-as-data are, and the research names the artisanal-PowerPoint problem as the central failure of the whole strategy-tooling space. Most strategists stay stuck because the slide-deck deliverable is how the profession proves and bills its value, so questioning it feels like questioning the job. The cost of staying stuck is the slow erosion of relevance and the fear of being replaced by cheaper analysts or AI. The cost to get out is admitting the deck was theater and building the engine.

P3. The product leader drowning in prioritization

Every week is a knife fight over the roadmap and I can't convincingly explain why we're doing feature A instead of B. Stakeholders fling requests at me like I'm a vending machine, and when I push back they ask based on what, and I don't have a good answer. I'm juggling OKRs, revenue, churn, tech debt, and random executive brainwaves, and I'm one angry VP away from getting labeled not strategic because I can't produce a perfect rationale on the spot. Half my job is pretending there's a rigorous process behind the roadmap when really it's a messy compromise between whoever shouted last and whatever fire is burning.

Being seen as not strategic, as just a ticket-taker, is career death for a PM, and I feel like a fraud every time I defend a prioritization call I know was mostly vibes and politics. I got here because prioritization is multi-dimensional and contested, there's no agreed framework, and the loudest stakeholder or the latest fire wins, so the decisions are made by politics and rationalized after the fact. Getting out takes a defensible, shared prioritization model that connects each product bet to company-level strategy with the reasoning visible, which the Wardley map plus Powell's policy routing provides, turning why-X-over-Y from a vibe into a traceable decision. Most PMs stay stuck because the politics are the water they swim in, so the arbitrariness reads as the nature of the job rather than a fixable rigor gap. The cost of staying stuck is the knife-fight weeks, the wasted engineering on wrong bets, and the fraud feeling. The cost to get out is building the defensible model and using it to hold the line against the politics.

P4. The small-business owner being out-strategized

I'm getting outmaneuvered by bigger competitors and I know I need a real strategy, but I can't drop fifty thousand on a consultant to tell me what to do. It feels like I'm playing checkers while the big guys are playing four-dimensional chess with marketing, pricing, and partnerships. I'm basically guessing, copying what seems to work for others and hoping it sticks, and I'm sick of generic advice like differentiate, because differentiate how, with what money, against a chain with a marketing department. I watch competitors roll out slick campaigns while I'm hacking together a flyer.

It's embarrassing to admit I don't really know my numbers or my positioning, I'm just trying not to sink, and underneath is the fear that I'm risking my family's security on a business that might fail simply because I don't know what I'm doing. I got here because real strategy was gated behind consultants I can't afford and the free advice is too generic to act on, so I never had a path to rigorous strategy and defaulted to imitation. Getting out takes consultant-grade strategy I can afford, a system that maps my actual situation and shows me the specific moves rather than a motivational quote, which is the promise of Wardley Swarm's service angle (premium work at an accessible price) and the gap the research confirms. Most owners stay stuck because strategy feels like a luxury for people who aren't worried about rent this month, and the belief that real strategy is for MBAs and big companies keeps the owner from even seeking it. The cost of staying stuck is being slowly out-competed and the family security riding on guesswork. The cost to get out is admitting the imitation isn't a strategy and buying the rigor that's finally affordable.

P5. The internal analyst whose rigor is not trusted

I spend weeks digging through data, building a solid recommendation, and the reaction is basically thanks, we will go with what the VP feels anyway. I'm tired of hearing that's just your opinion after forty slides of analysis, and if I can't trace every conclusion back to some spreadsheet, leadership acts like I'm making it up. Half the time my deck disappears into an email thread and the decision happens in a room I'm not in. They say they want data-driven strategy, but what they really want is data that supports the decision they already made.

I feel like a slideshow accessory to executive gut calls, and the shame is that when someone challenges my recommendation in the meeting I don't have a simple bulletproof way to walk through the logic, so my work gets treated as optional rather than foundational. I got here because my reasoning lives in my head and my spreadsheets, and the path from the analysis to a transparent, interrogable argument was never built, so a stronger personality in the room can dismiss it as opinion and I can't defend the rigor on the spot. Getting out takes a way to show the reasoning: the provenance graph from evidence to conclusion, and the ability to answer why is this here and not there with the evidence and the counter-evidence. Wardley Swarm builds that STORM-grounded tracing and cross-examination, and the research names it as the differentiator from black-box models and ungrounded opinion alike. Most analysts stay stuck because the dismissal is gradual and political rather than a single crisis, so they endure it cycle after cycle instead of naming the missing way to show their rigor as the fixable problem. The cost of staying stuck is powerlessness, intellectual work that doesn't change outcomes, and the quiet fear that the work is somewhat subjective. The cost to get out is making the reasoning traceable so it stops being just an opinion.

P6. The content strategist who needs a grounded map, not vibes

I'm supposed to produce a content and marketing strategy, and what I actually have is a mood board and a set of assumptions nobody has tested. The content goes out based on a vibe about the audience and the market, and when it underperforms I can't tell whether the content was bad or the strategy underneath it was wrong, because there was never a rigorous map of the landscape behind it. I'm building on sand, and the higher up the strategy goes the more it's just confident assertion.

My work is judged on results I can't fully control because the strategic foundation under it was never solid, and I'm exposed when the campaign misses because I can't point to the rigorous read that justified it. I got here because content and marketing strategy is conventionally done on intuition and trend-watching, so the discipline never demanded a grounded model underneath, and the ungrounded LLM brainstorm tools made it easier to generate confident-sounding strategy with no rigor. Getting out takes a trustworthy strategic map behind the content, the chessboard that grounds the audience read and the competitive position in evidence, which is the map-powers-content connection in Andy's seed, where the grounded map makes the content built on it defensible rather than vibes. This persona is the bridge to the content engines: Wardley Swarm produces the grounded map, the content brands produce the assets on top of it, and the map is what separates a real content strategy from a mood board. Most content strategists stay stuck because vibes-based content strategy is the norm and often produces something, so the missing rigorous foundation is never named as the cause of the inconsistent results. The cost of staying stuck is building on sand and being judged on outcomes the shaky foundation undermines. The cost to get out is demanding a grounded map before the content.

5. The world model (run the PST framework)

The six personas share one loop of suffering, and modeling it as a single problem-story turns the deck from a feature list into a Problem-Story-Transformation (PST) model. The model runs in four moves: echolocate the world, locate the Problem, reconstruct the Story, and design the Transformation.

Echolocate the world. The buyer lives inside a decision ecosystem under rising pressure and rising stakes. On one side is the accelerating pace of change, the AI moment most of all, which resets the landscape faster than anyone can intuit it, so the gut that used to be a decent guide is now guessing against a board that keeps rearranging. On another side is the supply of strategic rigor, which is bifurcated and inaccessible: the tier-one consultancies sell artisanal rigor at seven-figure prices to the largest enterprises, and everyone below that buys a mix of cheaper consulting, BI dashboards, and point tools that don't add up to a strategy. On a third side is the new machine option, which arrived loud and hollow: the LLM strategy copilot knows the vocabulary of every framework and enforces none of them, producing confident strategic-sounding text with no grounding, which is worse than no tool because it manufactures false confidence. Read it as an M&A firm reads a target and the leverage is stark: enormous money flows to strategy (a $900B-to-$1T consulting market, $100B-to-$150B of it strategy), large money flows to decision data (a $30B-to-$50B decision-intelligence TAM), and almost nothing bridges the two with rigorous accessible software, which the research confirms through the absence of any large strategy-mapping acquisition.

Locate the Problem (the cycle of suffering). The pain that arrives is the high-stakes decision under uncertainty with no rigorous way to think it through: the founder's market bet, the strategist's ignored deck, the PM's roadmap knife-fight, the small owner's being out-maneuvered, the analyst's dismissed recommendation. In response a fear gets installed, and the decision-maker's fears are heavy and specific: the fear of the wrong bet that kills the company (existential and irreversible, the no-undo-button dread), the fear of being exposed as not actually knowing what they're doing despite the title and the bravado, and the fear of analysis paralysis (freezing because no framework makes the choice tractable). Those fears drive two opposite but equally costly avoidances. One is gut-and-bravado: make the call on instinct, perform certainty, and bury the terror, which is the founder's and the small owner's path. The other is busywork-and-theater: produce the elaborate deck or the forty slides of analysis that look like rigor but change no outcome, which is the strategist's and the analyst's path. Both avoidances produce the unfavorable outcome (the bad bet, the ignored work, the arbitrary roadmap), and the outcome produces shame. Instead of concluding that they lacked a rigorous method, the person concludes that they aren't strategic at all, that they're a fraud, a slide monkey, a checkers player at a chess table. The shame is buried under cope: blame the market, blame luck, blame the competitors' resources, blame the politics, or hide behind the busywork. The red line, the one move that's forbidden, is accountability, because accountability means admitting that the decision was made on gut or dressed up as rigor it didn't have, and that the missing thing was a real method the person never built or bought. The refusal opens a blind spot, the blind spot produces the next bad decision (another gut bet, another ignored deck, another political roadmap), and the loop closes and compounds, often catastrophically because strategic errors are path-dependent and expensive.

Reconstruct the Story. The belief structure under the loop splits along the two avoidances but rests on a shared root. For the gut-deciders, the belief is that strategy is innate genius that can't be systematized, so either you have the vision or you don't, and admitting you need a method is admitting you lack the genius. For the theater-producers, the belief is that strategy is the impressive artifact, the deck, so the rigor is in the polish rather than in a reproducible engine. The shared root is that strategy is treated as a personal attribute (genius or craft) rather than a modelable discipline, which is the belief that keeps it from being systematized. The experience that built the belief is the high-stakes decision itself: the person was rewarded for confident calls or impressive artifacts and punished (sometimes catastrophically) for visible uncertainty, so they learned to perform certainty or polish rather than to build rigor, because rigor that shows its own uncertainty feels like weakness in a room that rewards conviction. At the origin, where it gets intimate, sits a decision-wound: somewhere the person learned that being wrong about a big call is identity-threatening, that the verdict on a failed bet attaches to the self (you're unemployable, you're a failure, you're not cut out for this), so they protect the self by either never examining the gut or hiding behind the artifact. Most of them run from that uncomfortable recognition, that the bravado or the theater is a defense against the terror of being wrong, not actual strategic command. On the Hawkins scale of emotional states, used here descriptively, the fear, the shame, and the pride that fuel both avoidances sit in the destructive band below the courage line.

Design the Transformation. The bridge across hinges on courage, and it's the same bridge for both avoidances because they share the root. The first step is truth, and the uncomfortable truth is that strategy is a modelable discipline and the rigor is learnable and buildable, so the missing thing was a method, not genius or polish, and a method can be acquired without the identity collapse the fear predicts. The second is responsibility, owning the reaction rather than the circumstance: the decision-maker didn't create the accelerating change or the bifurcated rigor market, but they own whether they keep letting the fear of being exposed drive the gut-bravado or the theater. The third is healing, which hurts because it means letting go of the identity that strategy is innate genius or impressive artifact and admitting the bets were guesses or the decks were theater, the way the founder admits the vision was partly survivorship-bias cosplay and the strategist admits the deck was performance. The fourth is forgiveness, releasing the verdict that a wrong call marks the self, forgiving the bad bets and the ignored decks and the arbitrary roadmaps, and learning from them, which opens the way to a new truth: being the person who builds and reads a rigorous strategic model is a larger and safer role than being the person who guesses confidently or polishes impressively. Wardley Swarm's offer is calibrated to that bridge: the map externalizes the chessboard so the founder can see the bet rather than dread it at 3am, the framework library gives the strategist a reusable engine rather than artisanal slides, the Powell routing gives the PM a defensible why-X-over-Y, the accessibility brings rigor to the small owner, and the provenance and adversarial interrogation give the analyst a way to show the reasoning so it stops being just an opinion. Most of the content lives in the negative band, the 3am dread and the ignored deck and the fraud feeling, because that's where the audience lives, with the rigorous, grounded, defensible, shared strategic model shown as the reachable other side. That's the four-move model applied to the person whose biggest decisions are made in the dark.

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

The competitive field has the emptiest middle of any infrastructure brand in the ecosystem, and the research calls it genuine white space outright. 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. The competitors fall into four clusters, plus consulting as the substitute. The decision-intelligence platforms (Quantexa, Aera, Pyramid, Palantir Foundry) own data and decision workflows but expose no explicit strategy frameworks: Quantexa does contextual graph analytics for risk and compliance, Aera does autonomous supply-chain operations, Pyramid is analytics-first producing dashboards, and Palantir has powerful data ontologies and digital-twin modeling but strategy is emergent from models and dashboards rather than expressed as analyzable Wardley maps or Powell policy classes, and it's heavyweight and consultant-implemented rather than a self-serve founder cockpit. The Wardley-mapping tools (OnlineWardleyMaps, the Miro and Mural templates, the various AI-Wardley experiments) are artisanal and diagram-centric: they faithfully draw the map primitives but connect to no live data, run no simulation, carry no multi-framework reasoning, and produce a one-off static artifact whose quality depends entirely on the human mapper. The simulation and wargaming platforms (the corporate scenario tools, the defense wargaming systems, and the emerging agentic-simulation platforms like Maxim AI, Sierra, LangWatch, and Salesforce's CRMArena) are about agent performance and safety rather than strategic positioning, so they lack the strategy frameworks, and they output evaluation metrics rather than reusable strategic maps. The AI strategy copilots (the general LLMs and the vertical strategy-copilot wrappers) are ungrounded brainstormers that know the framework vocabulary but enforce no structure or correctness and output text rather than schema'd reusable strategy objects. The fifth competitor is the substitute the brand actually displaces: tier-one strategy consulting, which is rigorous but artisanal, unscalable, and priced beyond the mid-market and the small operator. Across all of them the gaps are the same: no one offers a Wardley-native, agentic, multi-framework, STORM-grounded strategy operating system, and no one has turned strategy into a shared machine-readable substrate.

The third door. Alpha is the thing competitors know about and won't do, and Wardley Swarm's alpha is the connected combination of three components that the field has separately or not at all. The first is multi-framework explicit strategy reasoning (Wardley plus Powell's four policy classes plus game theory plus Bayesian priors as first-class encoded modules), which exists in no mainstream platform. The second is STORM-style grounding and defensibility (every map element and move traceable to evidence, a provenance graph of which agents and sources produced which conclusion, and adversarial interrogation of the map), which differentiates sharply from both the black-box decision models and the ungrounded copilots. The third is agentic scale plus the map-as-reusable-data (the strategy ontology as a living, versioned, queryable object that agents continuously update and downstream systems consume), which the research names as the biggest structural gap in the space. Competitors won't connect the three for structural reasons, and the research spells them out: the decision platforms are organized around data and won't expose explicit frameworks, the Wardley tools are organized around diagramming and won't add reasoning or data, the simulation platforms are organized around agent-testing and won't add strategic positioning, the copilots are organized around text and won't add grounding or structure, and the consultancies are organized around high-margin artisanal delivery and won't productize. Connecting the three takes a builder willing to do rigorous, unglamorous depth work across all of them, which is the analytics-framework-as-product thesis the brand is built on.

Wardley evolution and the own-versus-rule call. Generic LLM brainstorming and diagram-drawing sit between product and commodity on the evolution axis, so the brand rents or composes them instead of building them in-house. The multi-framework reasoning engine, the STORM-grounded provenance layer, and the strategy-ontology map-as-data sit between genesis and custom-built: they're novel, differentiating, load-bearing, and the thing competitors won't connect, so the brand owns and builds them, and that's where the alpha lives. The data and decision-platform connectors sit between custom and product, so the brand builds the integration discipline that lets it sit at the strategy layer over Palantir, Snowflake, and the EPM tools rather than competing as another silo, which the research flags as the core execution risk. The executive UX and the verticalized ontologies are custom-built, and the brand owns them, because the research identifies world-class executive UX as a potential primary wedge and verticalization as the path to defensible traction and proprietary data.

Market size and demand signal. The backdrop is enormous and the bridge is empty. Management consulting is around $900B-to-$1T with strategy consulting at $100B-to-$150B and MBB revenue at $25B-to-$35B; the decision-intelligence and advanced-analytics TAM is $30B-to-$50B by 2026; and the strategy and planning software market (EPM, FP&A, OKR) is $10B-to-$15B-plus. The category comps confirm the ceiling: Palantir at a $30B-to-$60B market cap, Quantexa a unicorn above $1B, Aera at $1B-to-$2B. The demand is revealed and specific: on top of the AI-adoption pressure described in the finance case, the cost of bad strategic bets is well documented (the majority of large bets and mergers destroy value), so willingness to pay to de-risk high-stakes decisions is high. The consulting spend proves the demand, nobody has built rigorous, accessible software to bridge it, and the AI moment is raising both the stakes and the pain. That's the wave the brand rides, tempered by the integration risk named in the software section.

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

Wardley Swarm is concept-stage, so the build section is more provisional than the live brands, but the shape is well-determined because the method already runs internally as the value rubric and because the market research specifies the load-bearing requirements.

What it is built from. The framework library is the heart: Wardley mapping, promise theory, game theory, Bayesian reasoning, Powell's four policy classes, and the Convergence Flow backbone, each encoded as an analytical module rather than a textbook reference, which no mainstream tool has and which the value rubric already implements by hand. The grounded-mapping agents are a STORM-inspired pipeline on LangGraph: plan the map, fetch evidence before asserting a placement, build the value-chain-and-evolution structure, and log the provenance, so every element is traceable. The simulation-and-council engine runs the agentic brainstorming and wargaming, agents playing out competitor moves and shocks on the map, which the research names as a strong, distinct edge. The visual map canvas is a Three.js and React surface, the executive cockpit the research insists must be world-class. The map-as-data export projects the strategy ontology into the metagraph and the content engines and pushes decisions into planning tools.

The hexagonal discipline. There's one strategy-modeling core and many surfaces. The mapping and reasoning operations live in a core that never imports a transport, and the canvas, the MCP server, the CLI, the API, and the export engine are all thin adapters over it. For a strategy brand whose whole value is a trustworthy shared model, this design also defends against duplicate copies drifting apart: the map is the one authoritative representation of strategic intent, every surface references it rather than copying it, and the provenance graph means a conclusion can't exist without its evidence, so the strategy can't quietly contradict itself or drift from its grounding.

The data models. StrategyMap, MapNode (activities, components, actors), MapEdge (value-chain links, dependencies, power relationships), EvolutionStage, PromiseEdge, PolicyDecision (the Powell routing), BayesianBelief (priors and posteriors), and EvidenceProvenance, each a typed Pydantic-IR record. As in the software design, the map data is typed through Scatter Model's IR and lives in WikiDesignCo's metagraph, which connects the strategy layer to the world model.

The agent roster the domain needs. The build needs four feature factories, each a set of agent harnesses plus a gateway. The research-and-grounding factory runs the STORM evidence pipeline and the connectors to the data and decision platforms the research says the brand must integrate with. The mapping factory holds the agents that build the map as first-class data. The simulation-and-council factory runs the agentic wargaming and the red-team agents that supply structured dissent. The QC-and-provenance factory handles the cross-examination of the map and the evidence validation. Each follows the same modular harness pattern as the software factories, and the STORM grounding is shared with Story Factory.

The medallion tiers. The data-engineering medallion tiers apply to map maturity: a bronze draft map, a silver grounded map with evidence-tagged placements, a gold map with simulation history and provenance and a governed review trail, and a diamond certified map that's the strategy-of-record for a domain with full snapshot history. The governance-and-traceability value the research names (boards and regulators wanting a strategy-provenance audit trail) maps directly onto the higher tiers.

Where Track R feeds Track P. Track R, the review of open-source repositories whose patterns feed the brand builds in Track P, hasn't started. The shape of the need is nameable: Wardley Swarm will want the best harvested patterns for STORM-style grounded research (shared with Story Factory), for the agentic-simulation and multi-agent-council engine (whatever the Track-R simulation and agent-orchestration repos teach, plus the LangGraph primitives the harness already plans), for the data and decision-platform connectors (the integration layer the research says is the execution risk), and for the graph-visualization canvas. When the repo decks exist, the value rubric (this brand's method) ranks the combined wish-list and the specific capabilities slot in here.

8. Priority read (feeds the value rubric)

Wardley Swarm's method is the value rubric that prioritizes this research program, so the brand is being prioritized by an application of itself. That self-reference is the strongest possible evidence that the method works, because the ecosystem already runs a manual version of Wardley Swarm to make these Now/Next/Watch/Leave calls. On the promise-dependency graph the brand is high-leverage (strategy sits behind every other brand's direction) and partly proven (the framework runs manually), but its productized form is downstream of WikiDesignCo's metagraph (the map-as-data lives there) and parallel to Story Factory (the shared STORM grounding), so it's gated on those plus the harness.

Readiness is the binding constraint: the brand is concept-stage with no standalone repo, so readiness sits below leverage, though the framework already being encoded in the value rubric is a stronger readiness signal than most concept-stage brands carry.

The first-pass tiering, capability by capability:

Now (build and own, partly already encoded): the framework library (Wardley, Powell, promise theory, game theory, Bayesian, Convergence Flow as analytical modules). It already runs in manual form as the value rubric, so productizing it is closer to ready than the rest of the brand, and it's the genesis capability competitors won't build. In Powell's terms it routes to the downstream-value calculation (a value-function approximation), and reflexively, Powell routing is itself part of the product.
Next (build and own, gated on the metagraph and the harness): the STORM-grounded mapping-and-provenance engine and the agentic simulation-and-council engine. They're genesis-stage, load-bearing, and the alpha, but they're gated on the metagraph holding the map-as-data and the harness running the multi-agent simulation reliably.
Next (the integration layer): the connectors to the data and decision platforms, which the research names as the core execution risk (become the strategy layer over the existing stacks, not another silo), gated on the same dependencies.
Watch (probe and verticalize): the breadth-across-all-strategy-domains ambition and the executive-UX cockpit. The research says to verticalize first (own a turbulent high-stakes vertical with pre-baked ontologies and priors) and that world-class executive UX may be the primary wedge, so both route to a focused probe rather than a broad commitment.
Leave (rent or compose): generic LLM brainstorming, diagram-drawing, basic charting. They're commodity or product, so the brand composes them.

Run the read through the seven-sins check, which pairs each deadly sin with a bias that distorts a forecast. Pride or look-ahead: the read scores the brand concept-stage and the connected strategy-OS as a bet, while crediting the proven framework (the value rubric), so it neither over- nor under-claims readiness. Envy or survivorship: the failure modes are in the deck (the integration-or-become-a-silo risk, the executive-UX-is-hard risk, the verticalization requirement, the concept-stage gap) alongside the white-space upside. Gluttony or overfitting: the enthusiasm is capped to the proven method and the verticalized wedge, not the abstract every-strategy-domain ambition. Sloth or transaction-cost: the build friction (the integration connectors, the simulation reliability, the grounding pipeline) is named as the gate. Wrath or regime-blindness: the read assumes the 2026 AI-adoption-raises-the-stakes regime, which is moving toward the brand. Lust or capacity delusion: Wardley Swarm is one primitive with a verticalized initial wedge, not an attempt to model every strategy domain at once. Greed or fat-tail: the tail risk is a decision-intelligence incumbent (a Palantir) adding explicit strategy frameworks, or the brand failing to integrate and becoming a silo, which is why the integration layer routes to the downstream-value calculation and the differentiation rests on the connected primitive. The dependency to flag when the brands are ranked against each other: Wardley Swarm is the method behind the rubric, so it has unusual self-evidence of leverage, but its productized form is gated on the metagraph and the harness, making it a strong Next whose framework library is closer to a Now, and the smart first move is a single high-value vertical with world-class executive UX rather than the full strategy-OS.