WikiDesignCo

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)

Picture the operator who knows AI is supposed to change their business and cannot make it stick. They paid a developer to build an internal knowledge tool and got a six-week flaming pile of brittle code that nobody will touch now. They looked at hiring the person who could do it right, a Forward Deployed Engineer, and found that senior FDEs in major US tech hubs command total comp well into the mid-six figures, often exceeding $300,000 and reaching toward $400,000-plus at the top end (per self-reported comp data, so directional rather than an official band), and that the role is widely reported as one of the hardest customer-facing engineering profiles to hire, gated behind a budget they do not have. So they keep loading a 200,000-word corpus into every agent call, burning money on redundant processing, watching the agents improvise and hallucinate generic garbage, and telling themselves they will fix the knowledge problem later. Later does not come. That operator is who WikiDesignCo is for, and naming their exact bind is the whole pitch.

WikiDesignCo is the central internal data-platform laboratory of the Looikos ecosystem, and the same capability rented to that operator as Forward Deployed AI Engineering on a flat monthly retainer. Andy's framing in his own walkthrough is the institutional quant firm that keeps a research department, "this fucking laboratory of financial engineering" that runs the crazy wonky experimental work nobody else will touch, except WikiDesignCo is that lab for data platforms, and it is his Skunk Works: people know it exists, it stays mostly internal for now, enterprise offers and accessible products come over time. The thing the operator rents is a metagraph-backed knowledge layer with surgical retrieval through MCP, wrapped in an operating model where one operator-architect plus an agentic stack delivers what a fourteen-specialist publishing house plus a dual-hire FDE team would deliver in-house. The customer never sees the GraphRAG, the temporal validity windows, or the contradiction engine. They see a flat number per tier and a deliverable that holds up. The live receipt is a client paying the $2,800/month part-time tier right now, and the proof-of-platform artifact is the Library, where each 10,000-plus-word piece is itself a sample of the work WikiDesignCo sells. The article is the demonstration. The brand makes its case by doing the work in public, not by claiming it.

2. Andy's seed, expanded

Andy's words (verbatim): "We've got Wiki Design Pro, which is like the central data platform. This is an internal asset. I don't actually intend to release this in a major public format. It was kind of like the equivalent of an institutional quant firm where they might have a research department that comes up with all sorts of crazy wonky shit. They basically really wonk this fucking laboratory of financial engineering. We have the same thing, in this case here that's Wiki design code. Wiki design code is that but for data platforms. What [the agent] harness is for all of this modern AI architecture, AI infrastructure, whatever you want to call it. Wiki Design company is the laboratory where it's my version of Skunk Works. People know it exists. Eventually I'll have enterprise offers for it and probably even some accessible stuff over time. But point is that this is where things are experimental right now."

Reading between the lines. Three things sit compressed in that, and the business brief confirms each past the point of inference.

The first is what the Skunk Works framing actually buys, and it is a posture, not a hedge about maturity. A Skunk Works is the place you run the experiments the main line cannot afford to fail in public, staffed by people trusted to work without the usual approvals. Lockheed's built the U-2 and the SR-71 in a fraction of the normal program time precisely because it was insulated from the bureaucracy. WikiDesignCo is that for data platforms: the lab where the metagraph world-model, the temporal-validity database, the contradiction engine, and the agentic content compiler get built and stress-tested before any of the other thirty-plus brands depend on them. Andy saying "this is where things are experimental right now" is not an apology for the brand being early. It is the operating model. The lab ships the dangerous, novel work first so the rest of the ecosystem can rent it as settled infrastructure, and the customer who rents it never carries the experiment risk.

The second is that WikiDesignCo is ContentFactory V2. ContentFactory was the first live stress-test of the whole idea, and the ContentFactory live instance is the customer-facing receipt that proves the model converts: the dealership client pays the $2,800/month part-time retainer today. WikiDesignCo is the production-grade rebuild underneath it, with the things ContentFactory learned it needed built in from the first commit rather than retrofitted: a metagraph from day one, hexagonal ports-and-adapters architecture from day one, dependency layering from day one, durable execution through Inngest from day one, observability through LogFire from day one, property-test evaluation through Hypothesis from day one. ContentFactory then becomes a customer-facing GUI that runs on top of WikiDesignCo infrastructure, and the downstream Constellation brands (FreelanceBuddy, Social Storyboard, Constellation Media, Node Foreman, Quant Scientist, Depths of the Void) inherit the trust WikiDesignCo establishes. That inheritance is the strategic point. WikiDesignCo is not one brand among forty. It is the floor the others stand on, which is exactly why desk-infra researches it first and why its priority read (§8) ranks it as foundational substrate rather than a leaf.

The third is the shape of the moat, three walls stacked in sequence. One, metagraph world-modeling: epistemic provenance, temporal validity windows, and a contradiction engine treated as first-class structure rather than bolted-on metadata, so the knowledge layer knows not just what is true but when it was true and where it disagrees with itself. Two, operator-plus-FDE compression: one operator-architect plus the agentic stack does the work of a fourteen-specialist publishing house plus a dual-hire FDE team, which is where the accessible pricing comes from without the quality dropping. Three, credit abstraction: the customer-facing interface is credit-denominated in an AAA-game aesthetic, a Diablo-style budget-tier selector where the customer self-selects a spend ceiling, which makes profitability invisible to the customer while making the customer's own budget predictable. Run the seven-sins discipline against the question of which wall actually holds, because the seductive answer (flat-retainer pricing that absorbs API variance) is a look-ahead trap: it is a real wedge today and copyable the moment tokens commoditize, so scoring it as the moat is scoring a fiction. The durable moat is walls one and two, the verticalized knowledge fabric that turns onboarding into mapping a customer's data onto an existing ontology rather than rebuilding from scratch, plus the compression that lets one person ship enterprise-grade output. Andy's own framing and the cold outside read converge on the same two, which is the strongest signal the moat is sited correctly rather than wished into place.

WikiDesignCo is the live instance of the world-model the Harness V2 build serves (see and, referenced not copied), and the software angle every other brand resells is built on the feature factories this lab proves out first.

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

3a. Finance (credit and capital access)

Read WikiDesignCo the way a market maker reads a target, which is the read Andy actually runs on every brand: fundamentals plus technicals plus live sentiment, and verify against the bank account, not the dashboard. What economic activity does it throw off, how does that activity convert to credit and capital access, and what is the brand worth to an acquirer.

The economic activity is recurring retainer revenue against a known cost of delivery. The retainer tiers are real and live: $2,800/month part-time, $4,000/month full-time, $8,000/month real-time, monthly exit, quarterly lock. The dealership client sits at the part-time tier today, and the internal cost of delivery at peak runs roughly $5,300/month in credits that WikiDesignCo absorbs. That looks upside-down for a single early account, and it is meant to. The markup math runs aggregate_cost x 1.25 reserve x 1.65 grandfathered = 2.0625x for early customers and x 1.8 base = 2.25x for standard customers, trending toward 3x to 5x cost-plus-reserves over the three-to-six-year horizon as the platform matures and upstream token prices fall. The arbitrage is explicit: the gap between today's cost of delivery and tomorrow's commoditized floor is a finite window, and every customer onboarded at the current markup funds the subsidized-credit moat the next customer rents. The independent market read confirms the mechanism is sound. GraphRAG and knowledge-based retrieval run roughly ten times fewer tokens than naive vector-only RAG on complex queries and cut cost by around 67% at scale, which is precisely what makes a flat retainer that absorbs usage variance margin-safe rather than reckless.

The credit story for an infrastructure brand runs on the quality of that recurring revenue, not on advertising spend volume. WikiDesignCo is not a heavy advertiser, so the advertiser-as-bank's-friend dynamic that floors some of the agency brands is muted here. What WikiDesignCo offers a lender instead is the cleanest collateral a young software business can have: contracted monthly recurring revenue with quarterly locks, a measurable and improving gross margin, and net revenue retention that should sit in the best-in-class band as customers expand from part-time to full-time to real-time tiers and add platform usage. Best-in-class vertical-AI and SaaS-plus-services businesses run blended gross margin of 60% to 70% and net revenue retention of 115% to 125%. Recurring revenue of that quality is exactly what revenue-based-financing desks and venture-debt lenders lend against, and the predictability of the flat-tier model plus the audit-stage quantification means the forward revenue is forecastable enough to factor. The capital path is the standard one for a brand of this profile: private venture and venture-debt early, with the public path open only if the brand consolidates several Constellation surfaces into one reportable platform entity.

The M&A and valuation read is where the $10M floor reveals itself as a floor. The category comps are strong and named. On the infrastructure side, Pinecone raised a $100M Series C in 2023 at a reported ~$750M post and a $200M Series D in 2024 widely reported above $2B; Glean raised a $100M Series B in 2022 at roughly $1B and a $200M Series C in early 2024 at roughly $2.2B; Neo4j, the cleanest graph-backed-data-platform comp, raised a $325M Series F in 2021 at more than $2B, the largest database round in history at the time, at an implied ~13x to 20x ARR. Those are the ceiling comps, the ones WikiDesignCo's metagraph-plus-RAG layer is in the same category as. The discount that pulls a real number down is the services-discount: pure product and infrastructure trade at roughly 8x to 14x revenue when growth and retention are strong, while AI-implementation services with limited IP trade at 1x to 3x revenue, so a business that is 60% to 70% recurring platform revenue and 30% to 40% services lands in a defensible 5x to 9x blended band. Run that against even a modest steady-state. One hundred to two hundred and fifty retainer customers across the tiers, the ecosystem's standard service floor, produce ARR in the low-to-mid eight figures; at a 5x to 9x blended multiple that is a $50M-to-$150M enterprise value for the service-and-platform angle alone, which is why Andy holds $10M as the floor for one angle rather than the target for the whole brand.

The market-maker's tri-level read ties it together. The fundamentals are the unit economics above: contracted ARR, a 60%-to-70% blended margin protected by the GraphRAG token savings, and an expanding NRR. The technicals are the funnel and retention mechanics, where the flat-tier model plus monthly-exit-quarterly-lock structure is engineered for low churn and tier-expansion. The live sentiment is the strongest tailwind of all: Forward Deployed Engineer postings rose more than 800% between January and September 2025, Salesforce alone is building a team of a thousand FDEs, and the role is one of the scarcest and most expensive in enterprise tech. A brand that sells exactly that scarce capability at an accessible price is reading a market where demand is revealed, supply is constrained, and the narrative is moving in its favor.

3b. Software (the interface stack)

The software angle is the one every other Looikos brand resells, so it carries the most strategic weight. WikiDesignCo's product is a metagraph-backed knowledge platform exposed through one core and many thin surfaces, built on the hexagonal ports-and-adapters discipline so the same operations surface through every interface without duplication.

The core is the metagraph backend. Convex holds the source of truth, Neo4j plus Graphiti hold the temporal concept-graph with its validity windows and contradiction structure, Qdrant holds the vectors, and Typesense holds the full-text index. None of those stores re-implements the graph operations; each is an adapter over a core that never imports a transport. That single discipline is what lets one knowledge layer present itself simultaneously as an HTTP API, an MCP server, a CLI, a web UI, and an agentic surface, with one source of truth behind all of them. The market read makes the value of this concrete. Glean, Vectara, Sana, and Credal each sell a slice of this and refuse the rest: Glean does permission-aware enterprise search but does not own your business ontology beyond what search needs, Vectara gives you managed retrieval but still requires your engineers to design the application, Credal solves secure access but is a component rather than an outcome, and the pure knowledge-graph vendors like Stardog and Oxford Semantic are too heavyweight to onboard an SMB. WikiDesignCo's software angle is the assembled whole that none of them sells as one thing.

The surfaces map cleanly to revenue lines, which is the point of building them as separate adapters. The MCP server monetizes the agentic access pattern: downstream Constellation brands and external agents query exactly the knowledge they need through MCP rather than loading a 200,000-word corpus, a roughly 90% reduction in context usage, and that agentic access is the credit-metered pattern. The CLI and the API support a credit-based and subscription program for programmatic consumers. The web UI, the Library today and the Platform when Wave B lands, is the SaaS subscription surface for human operators. The customer-facing pricing layer is itself a piece of software with a deliberate aesthetic: credit-denominated, AAA-game-monetization styled, a Diablo-style budget-tier selector where the customer self-selects a spend ceiling between hundreds and tens of thousands of credits. That credit abstraction is doing real economic work. It makes the platform's profitability invisible to the customer while making the customer's own budget predictable, which is the resolution to the single hardest problem the market read surfaced: flat all-you-can-eat retainers are brittle if one client hammers an internal chatbot and collapses the margin, so the credit ceiling is the mechanism that keeps the flat-feeling price margin-safe.

Underneath the surfaces, the platform decomposes into feature factories with clean domain boundaries, each domain maintained largely automatically by its dedicated agent harness. WikiDesignCo's factories are legible from the repo: ingestion (web crawl, document processing, chunking, embedding, indexing, inherited from the Archon-forked RAG core), the Content Compiler agentic stack that turns ingested knowledge into in-brand assets, retrieval and the AndyDataBot surface that serves precise context, and the metagraph world-model layer that holds provenance, temporal validity, and contradiction as first-class structure. Each factory is a set of agent harnesses plus a gateway harness specialized for its domain, so the already-domain-specialized agents submit the work and quality rises rather than falling as scope grows. This is the direct reason the Harness V2 build matters to the finance and service angles too: the software is built on custom, modular, composable harnesses that combine into feature factories, build-once-maintain-cheaply-monetize-three-ways (referenced from, not copied).

The bundled-tools subscription is the part the customer experiences as simplicity and the operator experiences as managed complexity. The software line item on a WikiDesignCo invoice bundles roughly twenty-four tools (LogFire, LangGraph, PydanticAI, Graphiti, Neo4j, Convex, Vercel, Higgsfield, Suno, ElevenLabs, Veo, Sora, Inngest, Clerk, Qdrant, Typesense, Remotion, Three.js, Framer Motion, GSAP, Payload, the Claude Agent SDK, the Vercel AI SDK, and the Hypothesis property-test stack) with the management fee baked into the markup. The construction-project-manager-managing-twenty-four-subcontractors analogy maps directly: the customer hires one number and one accountable party, and the platform absorbs the coordination and the cost variance behind it. That is a software product whose value is precisely that the customer never has to assemble or reconcile the stack themselves, which is the same value proposition the FDE hire offers at fifty times the price.

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

The service angle is where WikiDesignCo touches a paying customer today, and it is the angle the whole brand was reverse-engineered from. The model is Forward Deployed AI Engineering rented as a boutique retainer, premium quality at accessible pricing, sold as one flat number per tier.

The retainer structure is live and specific. Three tiers, $2,800/month part-time, $4,000/month full-time, $8,000/month real-time, with monthly exit and an option to lock the monthly rate on a quarterly contract. The customer sees two line items and nothing else: the operator retainer, which is labor plus accountability, and the software subscription, which is the bundled platform with the management fee in the markup. The alignment mechanism that makes the flat price hold across an engagement is audit-stage quantification. At engagement start, an audit locks the ingestion intensity (light, standard, or heavy) and the deliverable shape (per document, per corpus, per sprint), and the platform quantifies the deliverable price against that audit. Because the metagraph stack is extendable, modular, and maintainable, the audit estimates hold, so the customer experiences zero mid-engagement pricing surprise. This is the repo's design answer to the exact failure mode the market read flagged: retainers that promise unlimited usage collapse unless the scope is engineered tightly, and the audit-plus-credit-ceiling pairing is how WikiDesignCo presents a flat predictable price while staying margin-safe behind it.

The target operator is the Looikos canonical: the sub-25-employee master-complex, someone who is a genuine master of a craft, real and durable and non-replicable expertise, but who cannot scale it. For WikiDesignCo specifically that resolves to the knowledge-heavy and content-heavy SMB or agency: the operator whose real value is locked in documents, email, a CRM, and their own head, who needs FDE-grade knowledge engineering but cannot hire a $350,000-to-$500,000 Forward Deployed Engineer and would not get one to take a $2,800 retainer if they could. The market read confirms the gap is real and unserved from both sides: product-company FDEs are too expensive and tied to one platform and will not touch sub-$10K accounts, while the cheap AI-automation agencies ship shallow Zapier workflows and never build a real knowledge platform, knowledge graph, or governed ingestion. WikiDesignCo sits exactly in that gap, with the infrastructure depth of the enterprise vendors and the price accessibility of the agencies.

The compression is what makes premium-at-accessible arithmetically possible rather than a slogan. At the part-time tier the customer pays $2,800/month and buys the equivalent of a fourteen-specialist enterprise-grade publishing house, roughly $2.5M to $3.5M a year fully loaded, plus a dual-hire FDE team at roughly $2.4M a year fully loaded, for a total in-house equivalent near $5M to $6M a year, or $416,000 to $500,000 a month. That is a compression of 149 to 178 times the equivalent in-house spend, anchored on the customer-facing $2,800. The market read independently corroborates the mechanism behind the number: the durable edge is decomposing the FDE role into a small core of senior lead architects who design the playbooks plus a templatized infrastructure that delivers FDE-grade outcomes without staffing an army of $400,000 engineers. WikiDesignCo's version of that decomposition is one operator-architect plus the agentic stack, which is the compression moat from §2 seen from the service side.

The angle floors around $1M/month at the ecosystem-standard count of 100 to 250 retainer customers. It scales well above that as customers expand from part-time to full-time to real-time and add platform usage, which is the NRR-expansion engine the finance angle counts on. The commodity work beneath the premium engagements (routine content production, basic automation) gets partnered to the sister affiliate network of specialists, so service at scale is itself a network rather than a headcount problem, and the human operating model that runs the customer relationship is the shared-floor customer-success model (referenced from, not copied). The relationship with the customer is the irreducibly human part, and it is the part the whole agent-native stack exists to make one person capable of delivering at portfolio scale.

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

Six personas, each modeled in the first person at world-experience depth, each carrying the pain in language close to how these people actually talk. This is the Scar-Tissue Audit run on the buyer: drill past the surface complaint (I need a knowledge tool) to Layer 5 (the buried shame, I am winging it and praying, I built a graveyard of scripts out of ego, I am silently failing at operations), because the operator who names the buyer's Layer-5 pain owns the solution in the buyer's mind before any feature gets mentioned. These personas are the human side of what Andy sells as Intelligence Infrastructure: the same trauma he names in his own service writing (the performative-research box-check, the analysis-paralysis disguised as rigor, the data graveyard that cost six figures) is the pain WikiDesignCo's metagraph absorbs. The Lexicon of Pain below is provisional rather than quoted: the voice-of-customer research returned constructed-but-realistic phrasings rather than verbatim citations (the source flagged it could not surface exact thread quotes), so each phrase is tagged representative voice, not a documented quote. The patterns are corroborated where the business brief confirms them (the six-week flaming pile is in the brief verbatim) and where the market read confirms the structural situation (the FDE gap, the SMB manual-process majority). The bias is toward the negative emotions, because that is where these people actually live.

P1. The master-craftsman who cannot scale (the canonical target)

I am genuinely amazing at the work and absolute garbage at everything around it. I built this thing with my bare hands and I am proud of it, and I spend my day doing invoices, chasing people, fixing dumb little fires, and by the time I get to the actual work I am supposed to be known for I am fried. It feels like I am babysitting my own business instead of running it. I see these AI-first shops pumping out work like a factory and I am over here duct-taping spreadsheets together just to keep up. Every week there is a new AI tool and some guy screaming adapt or die, and I am still trying to write my own SOPs.

How it hits my life and status: a client asked me last month how I am using AI in my process and I said we are exploring options, which is a polite way of saying I am winging it and praying. That is the humiliating part. I know I am good, but it is starting to feel like being good is not enough anymore. How I got here: I optimized for the craft for twenty years and never built the systems, because the craft was the thing and the operations were always going to get handled later. Later never came. What it takes to get out, and why most fail: it takes systematizing knowledge I have never written down, and most people like me fail because the act of documenting it is so overwhelming that we abandon it halfway and go back to doing it manually, which is exactly the trap. The cost of staying stuck is the slow certainty that one bad month and my clients realize they can get eighty percent of what I do from some platform for a fraction of the price. The cost to get out is admitting how messy it has been the whole time. WikiDesignCo is for the operator who is ready to stop being the bottleneck without becoming irrelevant, by renting the FDE-grade systems that turn the craft into something that scales beyond their own hands.

P2. The technical founder who built their own RAG and abandoned it

I did the classic engineer thing. We burned six weeks rolling our own lightweight RAG system because how hard can it be, and we shipped nothing, and now I have a graveyard of half-baked scripts I refuse to open. I spent a month tuning embeddings and chunk sizes for a tool nobody outside the dev team even asked for. The whole thing is so brittle that any schema change means re-indexing everything and praying it does not silently corrupt. Our knowledge base is now half in Notion, half in a janky Postgres table with embeddings, and half in people's heads, which is three halves.

How it hits my status: if I am honest, it was pure ego. I wanted to say we built our own RAG stack instead of we pay a boring monthly fee for something that works. Leadership now sees me as the person who chases shiny objects, and the next time I propose an AI initiative I have already spent my credibility. How I got here: the senior-engineer urge to build the database myself, the conviction that a managed solution felt bloated and we could do it leaner, and the refusal to pay for the thing that solved eighty percent of the use case out of the box. What it takes to get out: swallowing the identity hit of being someone who rents the plumbing rather than building it, which is the hardest part, harder than the engineering. Why most fail: the attachment to the build-everything-in-house identity is the actual blocker, not the technology, and most engineers will defend that identity past the point where it is hurting the company. The cost of staying stuck is the next six weeks, and the customer-facing feature that never shipped because three devs were bikeshedding indexes. WikiDesignCo is the off-ramp that lets the founder keep the engineering pride for the product and rent the knowledge infrastructure that was never the differentiator.

P3. The SMB owner drowning in fragmented knowledge and content operations

Everything is everywhere and nowhere at the same time. We have docs in Drive, SOPs in Notion, the real process in a manager's brain who is always in meetings, and every time someone asks where is X I die a little inside because the answer is basically good luck. We rewrite the same thing over and over because nobody can find the previous version or trusts that it is current. Our content strategy is panic, produce something, throw it in a random folder, repeat. We are on a treadmill where we are constantly producing and nothing gets reused, and it is exhausting.

How it hits my life: I open our shared drive and feel instant decision fatigue. Is it in Marketing, Old Marketing, Archive, To Sort, or Misc. If I got hit by a bus, half the company's knowledge disappears with me, and I am ashamed of how much time we waste asking the same questions in Slack because nobody can find the answer. How I got here: every fix attempt turned into another abandoned folder or tool, so I stopped trying to fix the system and just absorbed the chaos into my own memory, which made me the single point of failure. What it takes to get out: a knowledge layer that actually holds the institutional memory and serves it back precisely, which is exactly the surgical-retrieval-beats-dump-everything problem WikiDesignCo's core was built to solve. Why most fail: the chaos is invisible from outside, so there is never a forcing crisis, just a slow exhaustion that never quite tips into action. The cost of staying stuck is burnout and the quiet fear that real businesses have their act together and I am silently failing at operations. The cost to get out is letting a system hold what I have been holding in my head.

P4. The senior practitioner whose expertise is trapped in their head

I keep getting asked to just document my process, and I do not know how to explain that my process is twenty years of pattern recognition, not a checklist. So much of what I do is gut feel backed by scars from all the times things went wrong, and you do not put that in a wiki page. Every time I try to write it down I hit a thousand edge cases and exceptions and I give up halfway through. I can tell in five minutes that something is off, but if you ask me why I would need an hour to reconstruct the reasoning. People say we just need to clone you like it is a joke, but what I hear is you are the bottleneck.

How it hits my status and my life: I am tired of being the person everyone pings to unblock things, and I also do not trust that if I step back the work gets done right, so I am trapped between resentment and control. How I got here: the expertise accreted invisibly, one corrected mistake at a time, and by the time anyone needed it transferred it had already become tacit and unreachable, the kind of knowledge the carrier cannot fully see themselves. What it takes to get out: a system that can extract the reasoning by interrogating the work rather than asking me to introspect it cold, which is the part WikiDesignCo's metagraph and agentic ingestion are built for, capturing the entities, the relationships, and the provenance of expert judgment rather than demanding a hand-written manual. Why most fail: the conflict underneath is that documenting the expertise feels like manufacturing my own replaceability, so the safer-feeling move is always to keep it in my head, and that fear quietly wins. The cost of staying stuck is being a fragile single point of failure that the whole team is exposed to. The cost to get out is the courage to believe that externalizing the judgment makes me more valuable as the person who designs the system, not less.

P5. The in-house AI champion under pressure to show ROI

I feel like I got sold a sci-fi demo and handed a glorified autocomplete with a dashboard. Leadership saw a slick vendor demo and now I am on the hook to transform the business with what is essentially an API wrapper with a logo. We ran a pilot, everyone played with the chatbot for a week, and then it died quietly, and now I am the person who wasted that budget. The tool works in the sense that it does not crash, but nobody trusts it for real work. Half the tools we evaluated turned out to be thin wrappers over a foundation model with some logging, and I wish I had pushed harder on due diligence.

How it hits my status: I am stuck between skeptical engineers who think it is snake oil and execs who want a case-study-worthy success in the next quarter, and I am embarrassed because I was the one pushing hard for this, so it feels like I fell for the hype deck. How I got here: the pressure to be the innovation champion ran ahead of the diligence, and the vendor's promise that it would just plug in turned into three months of SSO purgatory and permissions hell and weird edge cases with our data. What it takes to get out: a partner who owns the last mile, the workflow redesign and the data plumbing and the change management, rather than a tool that hands me a component and walks away, which is exactly the FDE-grade-versus-shallow-wrapper distinction the market read draws and the gap WikiDesignCo occupies. Why most fail: the disappointing pilot poisons the organization against AI entirely, so the next attempt is fighting both the original problem and the scar tissue. The cost of staying stuck is being the face of an expensive visible failure, and the career exposure of being tied to results I do not fully control. The cost to get out is admitting the first vendor was a wrapper and choosing depth over another demo.

P6. The enterprise evaluation lead deciding build-FDE-in-house versus rent

I am the one who has to recommend whether we hire the Forward Deployed Engineer or rent the capability. The hire is real and the number is brutal: total comp clears three hundred and fifty to five hundred thousand, the role is one of the hardest to fill in enterprise tech, and postings for it went up more than eight hundred percent in nine months, so even with the budget approved I am competing for a person who has so many high-paying offers coming at them that I probably lose the bidding war. If I do land them, they are one person, they take months to ramp, and if they leave the capability leaves with them.

How it hits my status: I own this decision, and if I build in-house and the hire walks in a year I own that outcome, and if I rent and the vendor underdelivers I own that one too, so the decision feels like choosing which way to be exposed. How I got here: leadership decided AI implementation is the bottleneck, which it genuinely is, and handed me the build-versus-buy call without an obviously safe answer. What it takes to decide well: a rented option that is credibly FDE-grade rather than agency-shallow, with absorbed cost variance so the budget is predictable, and enough depth that it does not become another disconnected pilot. Why most stall: the enterprise-grade vendors will not take a mid-market account and the cheap agencies cannot do the real work, so the evaluator gets stuck between two non-fits, which is precisely the unserved middle WikiDesignCo targets. The cost of staying stuck is the bottleneck staying a bottleneck while the quarter burns. The cost to choose is trusting a boutique to do what a $400,000 hire would, which the compression math and the live GPS receipt are built to make credible.

5. The world model (run the PST framework)

The six personas share one underlying problem-story, and modeling it as a single suffering loop is what turns the deck from demographics into PST. The framework runs in four moves: echolocate the world, locate the Problem, reconstruct the Story, design the Transformation.

Echolocate the world. The buyer does not live alone; they live inside an ecosystem that is itself in motion. Read it the way an institutional M&A firm reads a target. On one side is the customer's customer, the people who pay them, whose own expectations are being reset weekly by what AI now makes possible, so the buyer feels the floor rising under them through their own clients. On the other side is the supply of capability: the Forward Deployed Engineer who could fix this is one of the scarcest and most expensive people in the labor market, with postings up more than eight hundred percent in nine months and a thousand-strong team being built at a single vendor, so the obvious solution is structurally out of reach. Between those two pressures sits a tooling landscape that is loud and untrustworthy: enterprise platforms that will not serve them, agencies that ship shallow wrappers, and a constant stream of demos that overpromise. The metagraph slice of this world is dense with relationships that do not fit in rows: the buyer's knowledge, their clients' shifting expectations, the talent market, the vendor noise, the money and the blame flowing between them. WikiDesignCo's whole reason for being a metagraph-native platform is that this is the shape of the customer's world, and you cannot model it as a spreadsheet.

Locate the Problem (the cycle of suffering). The pain that arrives is concrete and recurring: knowledge is fragmented and unscalable, the craft cannot leave the operator's hands, and the one time they tried to fix it themselves it became a brittle mess. In response, a fear gets installed, and most of these buyers run a terrible fear portfolio. The fear of irrelevance (being lapped by AI-first competitors), the fear of humiliation (the six-week flaming pile, the client asking how they use AI and getting we are exploring options), and the fear of being conned again (the wrapper-with-a-logo that died quietly and took the budget with it). Those fears drive avoidance, and avoidance produces the unfavorable outcome: the systems never get built, the operator stays the bottleneck, the pilot stays disconnected. The outcome produces shame, the belief not that I did a bad thing but that I am bad at this, secretly chaotic after all these years, the engineer whose ego cost the company two sprints. The shame is unbearable, so it gets buried under cope: blame the hype cycle, blame the vendors, blame the pace of change, blame the LinkedIn guy screaming adapt or die. The one move forbidden, the red line, is accountability, because accountability means turning around and admitting that the stalled platform and the trapped expertise are not the market's fault but the consequence of fears they let drive the decisions. The refusal opens a blind spot, the blind spot produces the next disadvantageous action (another abandoned folder, another in-house rebuild, another demo-driven pilot), and the loop closes and compounds. This is the station almost every WikiDesignCo buyer is stuck at, and the content has to meet them there, in the denial and the shame, not in the clean future state.

Reconstruct the Story. The belief structure under the loop is some version of we should be able to handle this ourselves, which for the technical founder is the build-everything-in-house identity, for the master-craftsman is the craft is the thing and operations are beneath it, and for the senior practitioner is my judgment cannot fit in a template. The emotional-experience chain that built it runs the way the framework describes: repeated experiences of being rewarded for individual mastery hardened into a belief that mastery is the whole game, that belief drove actions (optimizing the craft, refusing the managed tool, hoarding the expertise), the actions produced results, the results became habits, and the habits anchored into an identity. The origin layer, where it gets intimate, is usually a wound around worth: the person learned somewhere that their value is the thing only they can do, so anything that externalizes or systematizes that thing reads as a threat to their worth rather than a multiplication of it. That is the uncomfortable part most of them run from, the place where documenting the expertise feels like manufacturing their own replaceability, where renting the plumbing feels like an admission that they were never as essential as the identity required. The 130-emotion archive and the Hawkins scale are used here descriptively, to locate exactly where each persona sits: shame, fear, and pride live in the destructive band below the courage line, and the entire suffering loop is fueled from there.

Design the Transformation (the cycle of growth). The bridge across has to be crossable, not a mugging, and it hinges on courage, the separation point between the destructive band and the constructive one. The first step is truth, and the uncomfortable truth WikiDesignCo's content surfaces gently is that the knowledge infrastructure was never the differentiator, the craft was, and renting the plumbing frees the craft rather than diminishing it. The second is responsibility, owning the reaction rather than the circumstance: the buyer did not cause the talent shortage or the vendor noise, but they own whether they keep letting the fear of looking un-essential drive the decision. The third is healing, which hurts the way relearning to walk hurts, because externalizing twenty years of tacit judgment or admitting a failed build means tearing through the identity knot that the expertise is the self. The fourth is forgiveness, letting go of the prior verdict, forgiving the six weeks and the ego and the could-have-bought-it, and having the humility to learn from it, which opens the eyes to the new truth that being the architect of a system is a larger role than being its single point of failure. WikiDesignCo's offer is calibrated to that bridge precisely. The flat retainer removes the financial fear, the audit-stage quantification removes the surprise, the live GPS receipt and the compression math remove the will-this-be-another-wrapper fear, and the operator-plus-agentic-stack model lets the buyer cross from being the bottleneck to being the person who designed the thing that scaled. Most of the content lives in the negative band because most of the audience lives there, with the growth cycle shown as the reachable other side. That is the Echolocation and Mirror-Ocean architecture applied to this specific customer: model the world fully, name where they are stuck, and offer the transformation across.

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

The competitive field is real and crowded at the edges, and empty in the exact middle WikiDesignCo occupies. Map it by what each player does, what each refuses to do, and where the third door is.

Who else does this, and what they will not do. Three clusters of competitor plus one substitute. The enterprise knowledge and RAG platforms (Glean, Vectara, Sana, Credal) each sell one slice and refuse the rest. Glean does permission-aware enterprise search well but does not redesign workflows, does not act as an FDE, and does not own the customer's business ontology beyond what search needs. Vectara delivers quality managed retrieval but still requires the customer's own engineers to design the application, the prompts, and the business logic, so it is a component, not an outcome. Sana is knowledge management and learning, not end-to-end process automation, with limited professional services. Credal solves secure access and governance but is infrastructure rather than outcomes. None of them says for a flat monthly number we will own your AI knowledge infrastructure and deliver specific outcomes, and none of them serves the SMB or mid-market at all; their economic model is platform subscription plus usage, not absorb-the-variance. The knowledge-graph and GraphRAG vendors (Neo4j, Stardog, Oxford Semantic, Writer's graph-RAG, IBM GraphRAG) own the technology WikiDesignCo's metagraph is built on, but they sell tooling to enterprises that already think in ontologies and already have data teams; they will not sit with a fifty-person company and design its ontology, and they are too heavyweight and too expensive to onboard an SMB. The AI-automation agencies sit at the opposite extreme: hundreds of small shops shipping $500-to-$2,000 retainers on Zapier and no-code stacks at roughly eighty-five percent margins, who understand SMB workflows but never touch hard data plumbing, never build a real knowledge platform or graph, and never do genuine FDE work (process redesign, change management, owning a KPI over a long horizon). The fourth competitor is the substitute itself: the in-house FDE hire, which is the thing the buyer would do if they could, and cannot, because the role clears $350K-to-$500K, is one of the hardest to fill in enterprise tech, and the candidates have so many offers that even a funded employer loses the bidding war.

The third door. Alpha is the thing competitors know about, have probably tried, and still will not do, because for their structure it does not make sense. Two moves define WikiDesignCo's alpha, and the market read confirms both are real gaps rather than imagined ones. The first is the verticalized knowledge fabric: using the metagraph not as a buzzword but to pre-encode the canonical ontology of a domain, so onboarding a new customer means mapping their data into an existing structure rather than rebuilding from scratch, which is exactly what the enterprise vendors will not productize for the mid-market and the agencies cannot build at all. The second is the operator-plus-FDE compression: decomposing the FDE role into a small senior core that designs the playbooks plus a templatized agentic stack that delivers FDE-grade outcomes without staffing an army of $400K engineers, which the product companies will not do because their economics are built on pulling through software ACV at large accounts. WikiDesignCo's stated three moats (metagraph world-modeling, operator-FDE compression, credit abstraction) are this alpha named from the inside, and the independent market read arrives at the same two as the durable ones, which is the strongest signal the moat is sited correctly. The flat-retainer-absorb-the-variance pricing is a genuine wedge but not the moat by itself, because it is copyable once tokens commoditize; the depth and the compression are what competitors structurally will not replicate.

Wardley evolution and the own-versus-rent call. Place each core capability on the genesis-to-commodity axis and the play falls straight out. RAG ingestion, chunking, embedding, vector search, the Archon-forked plumbing, is product-to-commodity: good-enough, competed, and reinventing it is the senior-engineer trap, so rent or harvest, never custom-build. The metagraph world-model with epistemic provenance, temporal validity windows, and a first-class contradiction engine is genesis-to-custom: novel, differentiating, load-bearing for the user need, and something competitors know about but will not do at this depth, which is the textbook own-and-build capability where the alpha lives. The credit-abstraction pricing layer and the operator-FDE compression operating model are custom and differentiating, also own. The bundled twenty-four-tool subscription is composition: assemble commodity and product components behind WikiDesignCo's own promises rather than building any of them. That mapping is the entire don't-build-your-own-database discipline made mechanical: rent the commodity, own the genesis, compose the rest.

Market size and demand signal. There is no clean analyst TAM for SMB FDE-as-a-service plus RAG, so triangulate. The demand for AI implementation is revealed and strong: FDE postings up more than eight hundred percent between January and September 2025, a thousand-FDE team at one vendor, the role named one of the fastest-growing in enterprise tech. The SMB substrate is large and underserved: a 2025 survey found seventy-three percent of small businesses still rely on manual processes for at least three core operations. The willingness to pay at the SMB level already exists, with packaged AI workflows selling at $500-to-$2,000 monthly tiers today, which means the buyer is already spending; they are simply not getting FDE-grade architecture for the money. The category comps confirm the ceiling: Pinecone above $2B, Glean at roughly $2.2B, Neo4j above $2B. Demand is proven, supply is constrained, and the middle is empty, which is the precise market shape Andy looks for: find where money is already being spent, build something far better, and make it accessible.

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

WikiDesignCo is the most fully specified brand in the ecosystem because its architecture is fully written down in the business brief, so this section is grounded almost entirely in the business brief.

What it is built from, in two waves. Wave A is live: the Archon-forked RAG core (web crawl, document processing, chunking, embedding, indexing, MCP retrieval) plus the static Library reading surface, the proof-of-platform artifact. Wave B is the production platform and has not started. Its stack is decided: Convex as the source of truth, Neo4j plus Graphiti as the temporal metagraph (the validity windows and the contradiction structure), Qdrant for vectors, Typesense for full-text, Inngest for durable functions, Clerk for auth, the Content Compiler agentic stack, the AndyDataBot retrieval surface, and an MCP server for downstream consumers (ContentFactory and the other Constellation brands). The decisive build judgment is the one the repo already made and the value rubric endorses: the RAG plumbing is a commodity to rent (fork Archon, customize the ten percent that matters), and the metagraph world-model is the genesis capability to own. That is the whole Track-R-feeds-Track-P logic in miniature: harvest the commodity, build the differentiator.

The hexagonal discipline. The load-bearing architectural pillar is core-one-surfaces-many. The graph operations live in a core that never imports a transport, and every interface (HTTP API, MCP server, CLI, web UI, agentic surface) is a thin adapter over that core, none of them carrying its own copy of an operation. This is the direct mechanical defense against the Disconnection: one authoritative representation per operation, every surface referencing it rather than duplicating it, so a fact or a rule cannot drift between the API and the MCP server. The metagraph backend is the canonical example, with Convex, Neo4j, Qdrant, and Typesense all adapters over one core rather than four re-implementations.

The data models. Pydantic-as-IR with no ORM. One typed Pydantic model is the intermediate representation across every backend, decomposed ECS-style into entities and components, splitting out to Zod/TypeScript where the frontend needs it. This is the same Pydantic-IR discipline that Scatter Model productizes (referenced, not copied; see the Scatter Model deck when it exists), which is why WikiDesignCo and Scatter Model are siblings in Category 1: WikiDesignCo is the data platform that consumes the IR discipline, Scatter Model is the brand that turns the discipline into a product.

The agent roster the domain needs. Four feature factories, each a set of harnesses plus a gateway harness: ingestion (crawl, process, chunk, embed, index), the Content Compiler (knowledge into in-brand assets), retrieval and AndyDataBot (precise context service), and the metagraph world-model layer (provenance, temporal validity, contradiction). The agentic stack underneath is LangGraph for workflows, PydanticAI and the Claude Agent SDK for the agents inside the nodes, Jinja for prompts, with tools as standalone shareable functions rather than agent-bound methods. Observability is LogFire on every I/O function, evaluation is Hypothesis property tests written by a separate agent from the builder, durability is Inngest.

The medallion asset tiers. The knowledge corpus is tiered bronze through diamond, with access gated by tier. Raw ingested material is bronze, curated and deduplicated is silver, the validated and provenance-tagged metagraph is gold, and the highest-value distilled expert knowledge is diamond. The credit-denominated access model maps spend tiers onto medallion tiers, which is how the customer's budget selector connects to the depth of knowledge they can reach.

Where Track R feeds Track P. Track R (the external OSS repo research) has not started; Andy provides the GitHub list on the other side of compaction. The hooks are nameable in shape even now: WikiDesignCo will want the best harvested patterns for durable agentic execution (the Inngest-style durability layer), for the temporal-graph and GraphRAG layer (whatever the Track-R graph and retrieval repos teach), for the agent-harness authoring and cataloging pattern (shared with Symphony AGI and Agent Shipyard), and for the ingestion and scraping layer (shared with Spider Scrape). When the repo decks exist at, the value rubric ranks the combined wish-list and the specific capabilities slot in here.

7b. The V1 platform build (2026-07-03 re-anchor)

This section supersedes §7's "Wave B has not started" as of 2026-07-03. The platform build is in flight under team wdc-platform-v1, and the day's operator directives sharpened the architecture in ways this deck must carry, because the downstream brands inherit exactly this.

The architecture is a fractal corpus. Every asset lands once, in its primitive format, in one central pool: a PDF in the PDF place, a YouTube video with its transcript and comments in the video place, a thread in the social place. The refinery decomposes and enriches each primitive (charts and figures scraped out of PDFs as derived assets, chunking, 3072-dimension embeddings, entity extraction, the full NLP battery), and every enrichment layer is stored as addressable, versioned inventory carrying the model and pipeline that produced it. Above the pool sit the views: a workspace scopes the corpus for a project, and a knowledge base is a curated selection over assets and chunks (fifty of two thousand textbooks, or only the sections of those fifty about one topic, assembled by an agent), each knowledge base carrying its own retrieval indexes and its own MCP connection. The same chunk serves thirty knowledge bases across thirty projects, and an enrichment improvement upgrades all thirty at once. This mechanism is what "every asset becomes a view over the same source" means operationally, and it is why per-project data infrastructure across the ecosystem consolidates here instead of fragmenting.

Governance is item-level and load-bearing, because fractal reuse without per-item rules is a breach waiting to happen. Sensitivity, anonymization requirements, usage constraints, and source-client attribution ride as ECS components on every asset and every chunk, and every retrieval path filters on them before anything crosses a workspace boundary. The canonical scenario: a FreelanceBuddy client in oil and gas equipment repair fills a workspace with agent research and five thousand scraped posts; months later a SocialStoryboard client one domain over reuses the shareable portion through a policy-filtered query with an audit trail, and the sensitive material never moves. The same event stream powers the laboratory economics: retrieval events record which chunks earn their keep and for whom, a credit ledger prices every ingestion and enrichment, and the operator tunes intake volume and enrichment depth against measured value, the way a quant desk manages derived-data inventory.

The build decisions of record: a separate GCP project cloned from the ContentFactory Cloud Run recipe (projects are GCP's isolation boundary, so a future spin-off is a billing relink rather than a service extraction); the workspace layer on Convex, generalized from the production ContentFactory schema, which retires the Archon-fork direction for the platform while keeping the Archon lesson (one MCP control plane for agents); Gemini and Vertex as the V1 processing baseline, since Gemini is the model that reads video; and a walking-skeleton gate, one workspace proven end to end (create, upload, ingest, search, agent-retrieve on the deployed stack, Three-Proofs QC) before the first-wave roster of twenty workspaces is seeded from the manifest. The staging truth the whole build honors: the platform is the environment, humans and CLI agents are its users through the same surfaces, and resident Hermes-class agents arrive later, low-level processing first. The first real workload is the world-model business brief, one per workspace, a first-class asset type from the first schema push, because the line between a workspace and its world model is the platform's founding contract.

7c. The four faces and the memory layer (2026-07-04 unified-vision re-anchor)

This section extends §7b with the whole-platform picture the day's research landed, so the deck carries the vision the downstream brands inherit rather than a fragment of it. WikiDesignCo is one thing with four faces, and they are the same platform seen from four sides. §7b named the first two in build terms; this section names all four and the interchange decision.

The first face is the central knowledge platform: one central pool of assets typed by primitive format, with workspaces and first-class knowledge bases as fractal views cut from it, the mechanism §7b already detailed. The second is the client-powering engine: a workspace per company and client, a world-model business brief of roughly fifty-five aspects as the first workload, and a domain authority map as the workspace home view. The map shows, for each element of a domain, the top entities, how much source material backs each, how fresh it is, and where the thin spots are, so the operator sees at a glance where they are already an authority and where to write or ingest more. Publishing into a gap visibly moves the map, which is the game feel the laboratory loop promises, made concrete on a Tuesday.

The third face is the one the deck had not yet named, and it is load-bearing: WikiDesignCo is the unified memory layer of the whole ecosystem, not just documents but CRM threads, agent conversation threads, and customer-service threads, all landing as assets in workspaces. Experiences consolidate into episodes that carry a summary plus pointers back to the exact turns; episodes accumulate until an assessment produces improvement proposals; every proposal resolves to a permanent decision record, greenlit or archived-with-reasoning, so a later agent can query why something was decided and when, and never re-proposes a rejected idea blind. Many agents share one memory, which makes the platform fractal in memory as well as in content. The fourth face is the metagraph itself: every fact carries provenance, confidence, and when-it-was-true automatically, as a habit, while the machinery (reified statements, bi-temporal validity, a contradiction engine) stays abstracted behind plain words in the interface, Sources and Coverage and Freshness and Where-this-came-from, never graph-theory vocabulary and never the Goertzel or quantum framing that belongs only in the private lineage docs.

The interchange decision of record: the Pydantic-IR genome emits Open Knowledge Format bundles as the portable, git-native, human-and-agent-readable file form, adopted first-class because OKF's flat typed frontmatter with one required key is the exact shape of a thin Pydantic node, so serializing to it is a short path rather than a translation project. OKF is the interchange skin that any agent, ours or a client's or a third party's, can read without custom glue; the claims layer stays the reasoning substrate. One intermediate representation, several serializations (Graphiti episodes, vector records, OKF files). The cost of the bet is near zero because a bundle is a directory of markdown in version control, so if the standard stalls the platform still holds readable typed files.

8. Priority read (feeds the value rubric)

WikiDesignCo is foundational substrate, the highest-leverage brand in the ecosystem to stand up, because the other Category 1 brands and the agencies inherit its metagraph, its infrastructure, and the trust it establishes. On the promise-dependency graph it is a foundational-promise node: many leaves depend on it, so it sequences first regardless of how any individual leaf scores. This is the single most important input the desk hands the value rubric: do not rank a brand that depends on WikiDesignCo's metagraph above WikiDesignCo itself.

Readiness is split by wave, and the wave split is the gate. Wave A (the RAG core and the Library) is live and proven; the ContentFactory live instance is the customer-facing receipt that the model converts. Wave B (the production metagraph platform) has not started, and Wave B is what the downstream brands actually inherit, so the priority read has to distinguish the live receipt from the unbuilt substrate honestly rather than treating the brand as uniformly ready.

The first-pass tiering, capability by capability rather than brand-monolithically, because the unit the rubric prioritizes is the capability:

• Now (build and own): the metagraph world-model with epistemic provenance, temporal validity, and the contradiction engine. It is genesis-stage, load-bearing for the user need, the alpha competitors will not replicate at depth, and the thing every downstream brand reads. This is the highest-leverage build in the ecosystem and routes Powell-VFA (it shapes many future decisions, it is substrate, score the discounted future not the immediate fit).
• Now (compose and ship): the Wave-A RAG core and the Library, already live, the proof artifact that earns the trust the rest inherits.
• Next (gated on the Now substrate): the credit-abstraction pricing UI and the Content Compiler agentic stack. Both are differentiating and both depend on the Wave-B metagraph being real, so they are attractive but blocked until the foundational promise is kept. Routes Powell-CFA: direction is set, the parameters need working out.
• Leave (rent, never custom-build): the RAG plumbing itself (ingestion, embedding, vector search). Commodity, correctly already rented by forking Archon. Reinventing it is the senior-engineer trap the whole ecosystem is disciplined against.
• Watch: the specific Track-R OSS harvest targets for the durability, graph, and ingestion layers, which become rankable only when Andy's repo list lands. Revisit on that named trigger.

Run the seven-sins gate against this read to keep it honest. Pride or look-ahead: the read scores Wave B as unbuilt and the metagraph as a bet, not as if it already shipped, so the present is scored and the bet is flagged. Envy or survivorship: the failure cases are in the deck (the six-week flaming pile, the failed pilots) rather than only the GPS win. Gluttony or overfitting: the enthusiasm is capped to the one live receipt, not inflated by the twenty-four-tool feature count. Sloth or transaction-cost: the Wave-B build friction is named as the gate, not rounded away. Wrath or regime-blindness: the read assumes the 2026 FDE-scarcity regime and the token-price-falling trajectory, both stated. Lust or capacity delusion: WikiDesignCo is one foundational build, not an attempt to ship all four factories at once. Greed or fat-tail: the tail risk is the metagraph build proving harder or slower than the differentiation justifies, which is exactly why it routes VFA and gets the discounted-future treatment rather than a rule-based adopt. The dependency to flag for the strategist: WikiDesignCo's Wave B is the keystone the Category 1 and agency roadmap arches over, so its sequencing decision is not a local call, it is the one that orders much of the rest.