> **A note on sources:** the external documents this report refers to were copied into `canon/` on 2026-07-05. The report's citations record what it read when it was written and are left verbatim; to follow one to the live document, open the copy under `canon/`. # Civilian Coder :::animation HERO **HERO: the door with no floor** - **What it shows:** a person steps through a door marked ACCESS UNLOCKED and finds themselves standing on nothing, a terminal glowing with AI-generated code they did not write floating in a void; a lattice of scaffolding then assembles beneath their feet plank by plank, each plank a concept they finally understand, until they stand on solid ground and the code becomes legible to them - **Narrative role:** sets the thesis and serves as the share/card thumbnail; the whole deck is the argument that access without understanding is a trap and the brand builds the missing floor - **What it teaches:** AI let anyone through the door of coding, but almost no one gave them a floor to stand on, and that floor is the whole product - **Intended impact:** the reader stops picturing a coding course and starts picturing a system that catches people who already got in and are standing on nothing ::: | Field | Value | |---|---| | Project | Civilian Coder | | Looikos cluster | Education, Mission and IP (Category 5) | | One-line | An accessible, agentic, personalized coding-education ecosystem that teaches real programming capability to people the industry locked out. | | Status | Concept (no repo yet; the build inherits the Looikos harness and the Scatter Model profile primitive). | | Existing code | None yet. Inferred build dependencies named in section 7. | | Desk | desk-education | | Coverage | INFERRED-heavy on the brand specifics (concept stage). Market size, M&A comps, the competitive field, the Lexicon of Pain, and the build economics are VERIFIED against three sequential Perplexity passes (section 10). | | Date | 2026-06-20 | --- ## Nine-rung frame (this research task) This deck is a read-only modeling artifact. Its nine rungs for the research lane: - **Purpose (the rails, held at every rung):** scale Andy Houston to a portfolio of independently valuable, agent-native brands run by one person. Civilian Coder earns its place by being researched deeply enough that an agent team can build and operate it without headcount, and by feeding learner-interaction data back as corpus for the simulation compiler. - **Mission (rung 1):** convert the captured Looikos ecosystem into a research-grounded intelligence corpus, one deep dive per brand. - **Objective (rung 2):** a finished, evidence-tagged, ~10,000-word deep-dive deck for Civilian Coder at `symphony/stack-recon/projects/civilian-coder.md`, graded CLEAN by the lead. - **Initiative (rung 3):** the symphony-recon Track-P run (Looikos brand research). Track R (OSS repos) is the sibling initiative; this deck names the capabilities it will need from Track R as OPEN placeholders, and does not block on them. - **Project (rung 4):** the TEAM_SPEC and the five desks. This deck is desk-education's first of three (Civilian Coder, then Sunflower Seeds, then Depths of the Void). - **Task (rung 5):** this single brand deep-dive, owned by desk-education, executed against `_PROJECT_TEMPLATE.md` and the PST framework. - **Action (rung 6):** A1 ingest the seed; A2 build the skeleton with word targets; A3 run three sequential Perplexity passes (market and comps; the Lexicon of Pain; the build reality); A4 run PST on each persona; A5 write each section incrementally; A6 self-check; A7 post and hand off. - **Decision (rung 7):** which Wardley stage the adaptive-tutoring capability sits at (INFERRED genesis-to-custom from reception evidence); which five personas to model (the ones whose pain drives the three angles); the first-pass priority tier (desk proposes, lead decides). Where a fact cannot be verified, it is tagged OPEN, never fabricated. - **Data (rung 8):** N/A (this doc is the artifact). The deck later seeds the metagraph as a BrandDeck entity. - **Event (rung 9):** N/A (this doc is the artifact). The real events are: deck written to disk, progress posted to Linear, grade recorded. --- ## 1. What it is (the one-paragraph truth) Civilian Coder is a coding-education platform for the people the existing industry quietly leaves behind: the career-switcher who burned through a bootcamp and never got the job, the hobbyist trapped in tutorial hell who can follow any video and build nothing alone, the capable developer in Kyiv or Cebu blocked by jargon-dense English documentation rather than by logic, and the new 2026 archetype who pays for Claude Code or Cursor every month, ships things that work, and lives in quiet terror that he doesn't understand a line of what the machine wrote. The core mechanic is a single discipline applied relentlessly: explain a hard concept the way you would explain it to a smart non-native English speaker, in simple words, with the right example for that specific person. The platform is agentic and personalized: instead of serving one fixed curriculum to everyone, it maintains a living profile of each learner (what they know, what they've failed at, how they're feeling about it) and optimizes the voice, the pace, and the examples per user through constant lightweight feedback. It's gamified, so the boring middle of the learning curve has scaffolding that holds a person through the days they'd otherwise quit. It runs on premium membership and community, so the learner is paying for a relationship and a cohort rather than access to a video library. And it tracks results per user, because in Andy's frame trust comes only from real outcomes, and a coding school that can't prove its learners learned to code is selling the same content library the market has already commoditized to zero. :::animation 1a **ANIMATION 1a: one curriculum splits into a thousand paths** - **What it shows:** a single rigid curriculum track, one fixed line every learner is forced down, shatters into a thousand branching paths; four distinct figures walk in from different edges, a career-switcher, a hobbyist, a developer typing in Cyrillic, a young coder with an AI tool open, and each path reshapes its pace, its vocabulary, and its examples to the figure walking it - **Narrative role:** anchors the §1 claim that the platform serves no fixed curriculum and instead adapts per learner - **What it teaches:** the core mechanic is personalization, one living path per person, not one course for everyone - **Intended impact:** the reader sees the difference between a video library and a system that reshapes itself around who is learning ::: :::animation 1b **ANIMATION 1b: the profile that remembers who you were** - **What it shows:** a learner's living profile card fills in real time as they work, three tracked fields glowing, WHAT THEY KNOW, WHAT THEY FAILED AT, HOW THEY FEEL ABOUT IT; when the learner hits a wall and starts to close the laptop, the profile notices the drop and the system quietly changes the next example rather than losing them - **Narrative role:** anchors the claim that the platform maintains a living per-learner profile and teaches against it - **What it teaches:** the system tracks not just skill but failure and emotional state, and it teaches against all three - **Intended impact:** the reader grasps that the product knows the learner as a person, not as an anonymous seat ::: :::animation 1c **ANIMATION 1c: the wall, and the hand on the bridge** - **What it shows:** a learner stands frozen at a tall wall on the day the shame peaks, a QUIT button pulsing beside them; instead of the wall a narrow bridge appears with a cohort of figures already crossing it, a coach's hand steadying the learner, a streak counter and a next small mission lighting the far side, and the learner takes one step instead of quitting - **Narrative role:** anchors the §1 claim that the brand refuses to let a learner quit at the shame peak - **What it teaches:** the gap the market ignores is a relationship-and-adaptation gap, closed by holding a person through the day they would otherwise walk away - **Intended impact:** the reader feels why a content library structurally cannot do this and a relationship can ::: In short, the world already has more coding content than any human could consume in ten lifetimes, and that content is now free, because a general-purpose model will explain any of it on demand. What the world doesn't have is a system that knows you, sits with you through the specific wall you're stuck at, refuses to let you quit on the day the shame peaks, and walks you across to the other side where you can actually build. That's a relationship-and-adaptation gap rather than a content gap, and a content-library business model structurally can't close it. Civilian Coder is the brand built into that gap. --- ## 2. Andy's seed, expanded **Andy's words, verbatim from his recorded breakdown of the brands `../../looikos_andy_transcript.md` lines 996-1015, lightly de-duplicated rather than paraphrased:** > Next is civilian coder. So civilian coder is about... now that AI agents have made the technical world accessible to practically anybody, you just need a cloud code [Claude Code] subscription. Civilian coder is about helping to guide people through the deep end of technical concepts in an accessible way. So the idea... is I imagine where I'm traveling through Southeast Asia, let's say Vietnam or Thailand... where English is... a second or third or even fourth language to them. And I need to explain a highly technical concept... very simple vocabulary... Civilian coder is the kind of thing where you could come from any perspective, and ideally it's set up in an agentic manner that it'll actually optimize its voice and examples and everything based on you in particular. So you'll be filling out forms... we'll adjust it to make it a gamified quality user experience. But it's kind of like a course, but instead of just teaching one programming language... civilian coder is an ecosystem of education where our objective is to teach everything technical... it becomes more and more valuable of a membership subscription... we'll actually maintain a profile of the users and be tracking and judging ourselves on how much we're actually helping guide them to be getting the results. (Note: the ecosystem map `../../LOOIKOS_ECOSYSTEM.md` is currently a stub and doesn't name Civilian Coder, so the transcript above is the canonical seed.) > Civilian Coder, **decompressed from that transcript** rather than quoted: an accessible technical-education ecosystem (AI made coding reachable for anyone with a Claude Code subscription): agentic and personalized (it optimizes voice and examples per user via constant feedback forms), gamified, premium-membership, community-driven, maintaining a profile and result-tracking for every user. Its method is the "explain a hard concept to a smart non-native English speaker in simple words" approach. **Reading between the lines.** Every clause in that seed is a compressed instruction, and the decompression connects each one to a load-bearing piece of the ecosystem. "AI made coding reachable for anyone with a Claude Code subscription" names the wedge with more precision than it first appears. Andy is pointing past the general beginner at a brand-new archetype that didn't exist three years ago: the person who already pays for an AI coding tool, already produces output with it, and is therefore already inside the door but standing on no floor. Market research confirms this is the structurally under-served segment, the "AI-first beginner" who can ship and can't reason. Rather than a prerequisite Civilian Coder imposes, the subscription is the signal that identifies the customer most acutely in pain and most able to pay. [VERIFIED that the archetype is under-served, market pass; INFERRED that Andy's clause targets it deliberately] :::animation 2a **ANIMATION 2a: inside the door, standing on no floor** - **What it shows:** a figure who has already paid for an AI coding tool stands just past a threshold marked ACCESS, shipping working output that scrolls past them, but the ground beneath their feet is missing and they teeter over the gap; a spotlight finds them and a label reads THE CUSTOMER MOST IN PAIN AND MOST ABLE TO PAY - **Narrative role:** anchors the reading of the wedge clause, the AI-first beginner who is inside the door and on no floor - **What it teaches:** the subscription is a signal that identifies the acutely-stuck payer, not a prerequisite the brand imposes - **Intended impact:** the reader sees exactly which customer the seed targets and why that customer converts ::: "Agentic and personalized, it optimizes voice and examples per user via constant feedback forms" is the brand dogfooding the entire Looikos thesis. Every Looikos brand exists to model a customer's world deeply enough to make any asset custom to one person's specific problem (the PST framework, Andy's method for reading a buyer's Problem, Story, and Transformation). Civilian Coder is that capability pointed at the learning experience itself. Rather than a satisfaction survey, the constant feedback forms are the live signal that updates the per-learner model, the same way the sibling brand Scatter Model's agents update a typed profile as you talk to them. Every learner is an RPG character whose stats, weaknesses, and emotional state the system tracks and teaches against. That profile is one person's slice of the Looikos knowledge graph (the metagraph), kept current in a temporal database so the system knows the difference between the version of you that didn't understand recursion and the version that does. :::animation 2b **ANIMATION 2b: the learner as an RPG character sheet** - **What it shows:** a learner turns into an RPG character sheet with live stats, skill levels, weaknesses flagged in red, an emotional-state bar, and an XP track; as the person talks to the system the sheet updates in real time, and a temporal slider marked BEFORE RECURSION and AFTER RECURSION lets the system see two different versions of the same learner - **Narrative role:** anchors the reading of the agentic-personalization clause, the per-learner model updated by constant feedback - **What it teaches:** the feedback forms are a live signal that updates a per-learner model, the same primitive Scatter Model updates as you talk to it - **Intended impact:** the reader sees personalization as a running model of a person over time, not a one-time intake survey ::: "Gamified" does structural work, and the build research is blunt about it: cosmetic points and badges habituate and stop working, while the gamification that actually retains learners is the kind that wraps the mastery model in proximal goals, visible progress, and social accountability. In PST terms, gamification is the scaffolding for courage. The cycle of suffering closes when a person quits at the shame peak; the streak, the squad, the next achievable mission are the structural supports that hold them on the bridge long enough to cross it. Duolingo proved that a habit-forming, gamified, lightly emotional learning loop is a multi-billion-dollar moat. Civilian Coder borrows the mechanics and points them at the harder, more anxiety-loaded act of learning to code. :::animation 2c **ANIMATION 2c: gamification as scaffolding for courage** - **What it shows:** the boring middle of a steep learning curve sags like a rope bridge over a gap where most people fall off; struts snap into place under it, a streak counter, a squad of fellow learners, a next achievable mission, and the sagging middle stiffens into a walkable span that holds a wavering figure through the stretch they would have quit - **Narrative role:** anchors the reading of the gamified clause, gamification as the structural support that carries a learner through the shame peak - **What it teaches:** the gamification that retains is scaffolding for courage across the boring middle, not cosmetic points and badges - **Intended impact:** the reader stops reading gamification as decoration and sees it as the load-bearing thing that prevents quitting ::: "Premium-membership and community-driven" is the software-and-service answer to what happened to Chegg, whose library of homework answers lost its paying users once a general model could answer the same questions free. If the product is a content library, a general model eats it, because the content is now free. If the product is a membership in a community with a coach who knows you and a cohort climbing alongside you, the moat is the relationship and the longitudinal data, neither of which a stranger with a chat window can replicate. The membership is the recurring revenue (the finance angle's throughput), and the community is the retention engine and the overflow capacity for the sister network of partner tutors (the service angle). "Maintaining a profile and result-tracking for every user" is the trust mechanism and the corpus engine at once. Trust in Andy's frame comes only from real outcomes, so a coding school must prove its learners learned. The per-user result-tracking is that proof. It's also the exhaust: thousands of learners' real struggle-and-breakthrough traces, in real coding workflows, are the proprietary longitudinal data the market research names as the only durable moat, and the substrate the Looikos simulation compiler learns from. That makes Civilian Coder a sensor as well as a brand, one that feeds the simulation compiler at the top of the stack. :::animation 2d **ANIMATION 2d: the membership that a chat window cannot copy** - **What it shows:** on the left a content library dissolves the instant a general model lights up beside it, its videos evaporating because the same answers are now free; on the right a membership persists, a coach who knows the learner by name, a cohort climbing together, and a thick longitudinal record of the learner's history that a stranger with a chat window cannot reproduce - **Narrative role:** anchors the reading of the premium-membership clause, the software-and-service answer to the Chegg problem - **What it teaches:** a content library gets eaten by a general model, but a relationship plus longitudinal data is a moat that does not - **Intended impact:** the reader sees why the membership, not the content, is the defensible surface ::: :::animation 2e **ANIMATION 2e: the sensor that feeds the apex** - **What it shows:** thousands of learners' struggle-and-breakthrough traces flow off their screens as glowing threads, converge into one proprietary river labeled LONGITUDINAL LEARNER DATA, and pour into a distant apex engine that visibly learns from them, so the school is drawn as both a teaching product and a data organ feeding something larger - **Narrative role:** anchors the reading of the result-tracking clause, the per-user tracking as both trust proof and corpus engine - **What it teaches:** result-tracking is the exhaust that becomes the durable moat and the substrate the simulation compiler learns from - **Intended impact:** the reader sees the brand as a sensor for the whole ecosystem, not just a standalone course ::: "The explain-a-hard-concept-to-a-smart-non-native-English-speaker-in-simple-words approach" is the craft Andy prizes most, knowledge distillation, stated as a teaching method. It assumes the learner is intelligent and treats the difficulty as a compression problem on the explainer's side, not a deficiency on the learner's. That one reframe is the emotional core of the brand, because the population it serves has spent years being told, implicitly, that their confusion is a verdict on their intelligence. The method says the opposite: you're smart, the explanation was bad, and we'll fix the explanation. It's also the first step of the transformation the brand designs for its learners. :::animation 2f **ANIMATION 2f: the difficulty moves to the explainer's side** - **What it shows:** a hard concept sits as a dense tangled knot in front of a capable learner who is told, wordlessly, that the tangle is a verdict on them; then the knot lifts off the learner and moves to the explainer's side, where it is combed into a few plain words and the right example, and the learner's face clears as a caption reads YOU ARE SMART, THE EXPLANATION WAS BAD - **Narrative role:** anchors the reading of the founding method, knowledge distillation stated as a teaching stance - **What it teaches:** the method treats difficulty as a compression problem the system must solve, not a deficiency in the learner - **Intended impact:** the reader feels the emotional core of the brand, the reframe that lifts the verdict off the learner ::: --- ## 3. The three-angle valuation Every Looikos brand stands on three angles at once, finance, software, and service, and Looikos sets $10M as the minimum each angle should reach, a floor rather than a target. ### 3a. Finance (credit and capital access) The financial shape of an education membership is the cleanest in the portfolio, because it's recurring consumer and business subscription revenue, which lenders and acquirers understand and price readily. **The revenue throughput.** Civilian Coder generates several layered streams. The consumer membership sits in the band the market will bear for a premium, personalized, outcome-tracked product rather than a commodity course: the build and market reads together put sustainable ARPU at $10 or more per month even on a frontier-model tutor, and Duolingo-class consumer learning subscriptions ($7 to $13 per month for the paid tiers) confirm the floor while the AI-tutor premium pushes the ceiling toward the $20 to $40 band that Copilot, ChatGPT Plus, and Duolingo Max already occupy. [VERIFIED comps; INFERRED exact Civilian Coder pricing] On top of the consumer tier sit cohort-based intensives (a paid, dated, coached sprint), employer-sponsored seats (the service angle's B2B2C path, billed per seat per month), and certification or assessment fees for learners who want a credential the result-tracking can actually stand behind. The floor comes from the service angle alone: at 100 to 250 retainer-equivalent business customers in the $2k to $12k-plus band, it reaches roughly $1M per month, and the consumer membership stacks on top of that, not under it. :::animation 3a1 **ANIMATION 3a1: the stacked revenue ladder** - **What it shows:** four revenue lines stack into one rising column, a consumer membership band at the base widening as members join, cohort intensives, employer-sponsored seats billed per seat, and certification fees on top; a ruled line marked ONE MILLION A MONTH sits at the service-angle floor and the consumer membership visibly stacks above it rather than replacing it - **Narrative role:** anchors the §3a revenue throughput, the layered streams and the floor math - **What it teaches:** the streams stack rather than compete, so the service floor and the consumer membership add together - **Intended impact:** the reader sees the revenue as a stack that clears the floor before the consumer tier is even counted ::: **Why that throughput converts to credit and capital.** Recurring subscription revenue is the single most financeable cash-flow shape there is. A book of monthly memberships with measurable churn and lifetime value is what revenue-based-financing lenders and venture-debt providers underwrite against, advancing capital as a multiple of monthly recurring revenue. The heavy, fast-moving transaction volume of a consumer membership business (thousands of small recurring charges, plus the advertising spend that acquires them) is the structural profile that makes an operator the kind of customer banks and card processors want to extend credit lines and factoring against, which is the standing with banks that ad spend earns, and Andy builds toward it across the whole portfolio. The brand is designed so its real economic activity becomes a lever for capital access rather than only a profit line. **The M&A and valuation read, tri-level.** Read the comps the way a market maker reads a tape: fundamentals, technicals, sentiment. Fundamentals first, the post-2020 comps. Skillsoft acquired Codecademy in 2021 for about $525M, on roughly $60M to $70M of revenue, a multiple in the 7x to 8x range. [VERIFIED deal and price; INFERRED multiple from reported revenue] Vista Equity took Pluralsight private in a deal announced in late 2020 and closed in 2021 at about $3.5B, on roughly $390M to $400M of revenue, an 8x to 9x range. [VERIFIED price; INFERRED multiple] Udemy went public in 2021 near a $4B valuation and Coursera near $4B to $5B; both compressed hard in the public market to revenue multiples in the 2x to 5x band by 2024. DataCamp is private, last reported with strong growth and tens of millions of learners, valued privately in the mid-to-high single-digit revenue-multiple range at the 2020-2021 peak. [INFERRED] The reading: education assets transacted at 7x to 10x revenue at the peak of edtech enthusiasm and reset to 2x to 5x as the public market re-rated the whole category. A self-standing Civilian Coder, valued across all three angles as an M&A target rather than on the service angle alone, sits comfortably above the $10M floor; the floor is one angle's number, and the multiple the asset earns depends entirely on which side of the next reading it lands. Technicals next, the channel and funnel mechanics that move the multiple. The whole category re-rated downward on a single shock that was both technical and a matter of sentiment, and the assets that earn the high multiple again will be the ones whose funnel mechanics prove they aren't what got disrupted. Sentiment comes last, and for this brand it carries the most weight. The defining sentiment event in edtech is the Chegg collapse. Chegg's moat was a large, searchable library of textbook solutions and Q&A. When ChatGPT shipped, students stopped paying for a library they could now query for free in their own words, Chegg publicly acknowledged generative AI was crushing new-user growth, and the stock fell more than forty percent in a single day before a sustained multiple compression. [VERIFIED] The market now prices every content-library education asset as a Chegg-in-waiting, which is the entire reason the category sits at 2x to 5x. The strategic consequence for Civilian Coder is direct and favorable: the brand is deliberately built as the thing ChatGPT can't substitute, a longitudinal, relationship-and-outcome business rather than a content library, which means it's positioned to be valued on the Duolingo side of the sentiment line (gamified, habit-forming, personalized, durable; a market cap in the tens of billions at points) rather than the Chegg side. The finance angle's central thesis is that the brand's design choices are the argument for the higher multiple. :::animation 3a2 **ANIMATION 3a2: which side of the sentiment line** - **What it shows:** a single dividing line runs down the frame; on the left a CHEGG marker, a stack of textbook-solution pages that collapses to a low multiple the moment a general model appears; on the right a DUOLINGO marker, a habit-forming personalized loop that holds its high multiple; Civilian Coder's chip slides across to the right side because it is built as a relationship-and-outcome business rather than a library - **Narrative role:** anchors the load-bearing sentiment read in §3a, the Chegg-versus-Duolingo valuation split - **What it teaches:** the market prices content libraries as Chegg-in-waiting, and the design choices are what earn the Duolingo-side multiple - **Intended impact:** the reader sees valuation as a consequence of build choices, not an external accident ::: ### 3b. Software (the interface stack) The software angle is what every Looikos brand resells three ways, so it carries the most weight in the value rubric. Civilian Coder's product surface decomposes cleanly into an API, a SaaS UI on top, and the diversified programmatic interfaces (MCP, CLI, SDK), each optimized for its environment. **The API.** Underneath everything is a teaching-and-personalization API: endpoints that take a learner's state and a target skill and return the next task, the right explanation calibrated to that learner's level and language, an assessment of a code submission, and an updated mastery estimate. That makes the API personalization-as-a-service and assessment-as-a-service, the asset that makes the rest possible. The API is where the proprietary value concentrates, because the hard, non-commodity parts of the build (the skill graph with calibrated difficulty, the trustworthy mastery model, the pedagogy policy that decides when to recap, escalate, or slow down) all live behind it. It's sold as credit-based and subscription access to anyone building on top. :::animation 3b1 **ANIMATION 3b1: the proprietary value sits behind one door** - **What it shows:** a teaching-and-personalization API renders as a single sealed door; a learner's state and a target skill go in one side, and out the other comes the next task, an explanation calibrated to that learner's level and language, a graded submission, and an updated mastery estimate; behind the door the three hard non-commodity parts glow, a calibrated skill graph, a trustworthy mastery model, a pedagogy policy - **Narrative role:** anchors the §3b claim that the API is where the proprietary value concentrates - **What it teaches:** the defensible parts of the build all live behind the API, which is what makes the surfaces on top possible - **Intended impact:** the reader sees the API as the value core rather than a plumbing detail ::: **The UX/UI SaaS platform.** On top of the API sits the learner-facing application: the editor, the exercises, the gamified shell (streaks, XP, mastery map, leagues, the limited-AI-reveal "hearts" mechanic), the per-user dashboard, and the community. That's the SaaS subscription, the consumer and prosumer product, and the place the relationship lives. It's built on an embedded code editor (Monaco or CodeMirror) over a hybrid execution layer: in-browser WebAssembly (Pyodide for Python, native for JavaScript) for instant cheap feedback, and server-side sandboxed containers for full test suites and multi-file projects. [VERIFIED build pattern] **MCP, CLI, SDK.** The three programmatic interfaces are where Civilian Coder is native to its customer rather than bolted on. The CLI is the decisive one, because the wedge customer already lives in a terminal next to Claude Code; an in-terminal coach that watches what you're actually building and teaches against your real stuck points, in the environment where you got stuck, is the "teach with your AI tools, not about them" wedge the market read identified as the sharpest available. The MCP server (Model Context Protocol, the standard way AI agents reach tools) exposes the tutor as a capability other agents and IDEs can call, which sells agent access and lets the tutor ride inside Cursor, Claude Code, or any MCP-aware host rather than competing with them. The SDK lets a bootcamp, an employer, or a sister-network partner embed the Civilian Coder tutor into their own product. The pricing maps the way it does across the Looikos brands: MCP monetizes agentic access, CLI and API support the credit-and-subscription program, and the UI supports SaaS. :::animation 3b2 **ANIMATION 3b2: the coach that lives in the terminal** - **What it shows:** a split terminal where the wedge customer is already building next to Claude Code; a coach presence appears in the same terminal, watching the real project scroll by, and when the learner gets stuck on their actual code the coach teaches against that exact stuck point in the environment where it happened, with a banner reading TEACH WITH YOUR AI TOOLS, NOT ABOUT THEM - **Narrative role:** anchors the §3b claim that the CLI is the decisive surface because the wedge customer already lives in a terminal - **What it teaches:** an in-terminal coach that teaches against the learner's real work is the sharpest wedge available - **Intended impact:** the reader sees why meeting the customer inside their existing tools beats a separate course ::: **The feature-factories and which harnesses it needs.** The platform decomposes into clean domain boundaries, each maintained largely automatically by a dedicated harness: a curriculum-generation factory (lessons, exercises, and explanations as structured documents), an assessment-and-grading factory, a personalization-engine factory (the learner model, knowledge tracing, the FSRS spaced-repetition scheduler), a community-and-social factory, and a progress-analytics factory. The shared Looikos components carry the heavy lifting. Story Factory is the natural producer of the lesson and exercise templates filled at scale; Scatter Model is the producer of the per-learner Pydantic RPG profile and the Jinja-driven dynamic prompt and form layer that personalizes voice and examples; WikiDesignCo is the knowledge substrate and the Graphiti temporal store the learner profile lives in; and the harness itself is what makes the whole thing maintainable by one person plus agents. That's the software angle's defining promise: build once, maintain cheaply, sell three ways. ### 3c. Service (premium-at-accessible boutique delivery) The service angle is where the floor of $1M per month gets built, and education is unusually well-suited to it because the deliverable (a person who can now do something they couldn't) is the outcome a retainer buys. **The target operator.** The standard Looikos target, the owner of a business under twenty-five people who has mastered a craft, is concrete for this brand: the expert individual instructor, the small dev shop owner, or the senior engineer who is a real master of a craft and can't scale themselves past the hours in a day. They have durable expertise nobody can copy, which is a real edge, and they're trapped one-to-one. Civilian Coder partners with that operator the way every Looikos brand partners with masters: it has already modeled the entire problem-and-solution world the operator's students live in, and it already has the software platform behind it, so the operator delivers premium quality at accessible prices without building any of the infrastructure. The expert's voice and judgment become the high-tier diamond mentorship; the platform handles the scale, the tracking, the gamified retention, and the overflow. :::animation 3c1 **ANIMATION 3c1: the trapped master, unclamped** - **What it shows:** an expert instructor sits clamped to a single one-to-one session, a hard ceiling labeled HOURS IN A DAY pressing down; the platform slides underneath them and the ceiling lifts, their voice and judgment fanning out to many learners at once while the software carries the scale, the tracking, the gamified retention, and the overflow they could never staff - **Narrative role:** anchors the §3c claim about partnering the trapped master operator - **What it teaches:** the platform unclamps a genuine expert from one-to-one delivery without diluting their judgment - **Intended impact:** the reader sees the service angle as a multiplier on real expertise rather than a substitute for it ::: **The retainer economics and who pays them.** Three service shapes carry the angle. First, employer learning-and-development retainers: a company with a development team that now has to make every engineer productive and safe with AI coding tools (the exact problem the market read flagged as moving faster in enterprise than in consumer) pays a monthly retainer in the $2k to $12k-plus band to upskill that team, with manager dashboards, cohort tracking, and measurable reduction in AI-introduced defects as the legible return. Second, cohort-based bootcamps and intensives: paid, dated, coached sprints run on the platform, premium because they are outcome-tracked and personally coached, accessible because the software does the heavy lifting the human coach used to do alone. Third, one-to-one mentorship at scale: the diamond tier, where a learner gets a human master plus the always-on agentic coach between sessions. The 100-to-250-customer math that puts the service angle's floor around $1M per month works for any brand and lands naturally here, because employer L&D contracts and cohort programs sit squarely in the retainer band, and the consumer membership stacks above rather than replacing them. :::animation 3c2 **ANIMATION 3c2: three service shapes, one retainer band** - **What it shows:** three delivery shapes line up into the same retainer band, an employer L&D contract with a manager dashboard showing fewer AI-introduced defects, a dated coached cohort sprint running on the platform, and a diamond one-to-one mentorship with an always-on agentic coach filling the space between human sessions; a shared bracket marks all three inside the two-thousand-to-twelve-thousand-plus monthly band - **Narrative role:** anchors the §3c retainer economics, the three service shapes that carry the angle - **What it teaches:** employer L&D, cohorts, and diamond mentorship all sit in the same retainer band and the human relationship is the deliverable - **Intended impact:** the reader sees the concrete business customers who pay the floor, not an abstract service tier ::: **The sister-network and the operating model.** Standard tutoring and support work beneath these engagements (the overflow when a cohort scales, the off-hours human help, the localized instruction for a non-English market) gets partnered to the sister affiliate network of specialist tutors and instructors, so service at scale is itself a network rather than a hiring problem. Emerging-market senior talent pays off directly here too: excellent instructors in the Philippines, Ukraine, or Colombia, abundant and constrained mainly by English, become first-class operators because the platform's live-transcript and agent-native systems dissolve the English constraint, and a path to buy into ownership of their shop self-selects for the ones who think in decades. :::animation 3c3 **ANIMATION 3c3: the English constraint dissolves** - **What it shows:** an excellent instructor in Manila or Lviv stands behind a glass wall labeled ENGLISH, their real teaching skill visible but muffled; the platform's live-transcript and agent-native layer washes over the wall and it turns clear, their instruction flowing through undistorted to learners worldwide, and a path marked BUY INTO OWNERSHIP opens beside them - **Narrative role:** anchors the §3c emerging-market senior-talent arbitrage - **What it teaches:** the platform removes the language tax so abundant emerging-market instructors become first-class operators - **Intended impact:** the reader sees the service network as a global talent unlock rather than a hiring cost ::: The human side runs on the shared floor, the Looikos customer-success model (built for success, not sales) in which senior people rotate through one room with AI agents listening in. The relationship with the learner is the irreducibly human part, and it's also the part that produces the outcomes that produce the trust that produces the next 250 customers. --- ## 4. The personas (modeled to world-experience depth) Five personas speak here in the first person, each using the words the coding community uses about itself, drawn from the voice-of-customer research, and each leaning toward the negative emotions where most of the audience lives. The terms in quotes are recognized community idioms, not paraphrase. [Lexicon VERIFIED against the VoC pass, section 10] :::animation p0 **ANIMATION p0: five learners, one buried verdict** - **What it shows:** five figures stand around a single dark loop labeled the cycle of suffering, each entering at a different surface, a failed bootcamp, a blank editor, a documentation wall, a management meeting, an AI completion they cannot explain, yet all circling the same buried belief at the loop's center reading I AM NOT A REAL PROGRAMMER; a lit far bank marked CAN ACTUALLY BUILD is visible to all of them and none has crossed - **Narrative role:** frames the whole persona section, the shared verdict underneath five different surfaces - **What it teaches:** the five personas differ on the surface and run the same loop around the same installed belief - **Intended impact:** the reader reads the personas as one structure with five entry points rather than five separate buyers ::: ### Persona 1: The bootcamp-burned career switcher I'm thirty-four. Two years ago I quit a stable job that was slowly killing me, an administrative role in an industry everyone agrees is dying, and I bet on code. I told my wife it was the smart move, the future-proof move. I drained most of our savings into a bootcamp that promised "six months to six figures." I graduated. I didn't get the job. I haven't gotten the job for fourteen months. I open LinkedIn and watch people from my cohort post their first dev role and I do the math on why it was them and not me, and the math always comes out the same way: it must be me. In the words I'd only ever type into an anonymous thread at 2am, I'm a "bootcamp grad with no job," and I'm starting to suspect the whole thing was a "pay-to-pray bootcamp," a "bootcamp mill" that sold me a survivorship-biased dream. I'm "too junior for dev and outdated in my old career," stuck in a no-man's-land I built myself. How I got here was hope plus a sunk cost. I believed the marketing because I needed it to be true. And now the sunk cost has me in a vise: "I've spent so much already, I can't quit now, but I can't afford to keep going like this." The shame under the regret, the thing I can't say out loud, is about what I told my family, not about money: I told them I was becoming a developer. I posted the progress. I made it my identity. And now I have to walk that back, and the sentence that loops in my head is "I walked away from a stable career for nothing; I'm not a developer and now I'm not anything." When my partner is quiet about the finances I hear a verdict: "I gambled my family's security." Maybe they're right. Getting out takes the one thing the bootcamp never sold me, because it couldn't be packaged into a twelve-week curriculum: a system that meets me where I am, somewhere broken between "beginner" and "job-ready," and rebuilds the specific competence I'm missing while refusing to let the shame spiral finish the job. People like me usually fail because we're carrying a financial wound and an identity wound at once, and every existing platform treats us as a fresh enrollment, a blank beginner, which reopens the identity wound on day one. Getting out would cost a fraction of what I've already spent, and the cost has an end. Staying stuck costs the marriage, the savings, and the version of myself I was brave enough to reach for once and may never reach for again. :::animation p1 **ANIMATION p1: the identity wound reopened on day one** - **What it shows:** a career-switcher watches cohort peers post their first dev jobs while a sunk-cost vise labeled SIX MONTHS TO SIX FIGURES clamps tighter; a generic platform greets him as BEGINNER, MODULE ONE and the label reopens a wound; then a different system meets him at the exact broken-in-between spot he actually stands and rebuilds only the missing competence - **Narrative role:** anchors persona 1, the bootcamp-burned career-switcher carrying a financial wound and an identity wound at once - **What it teaches:** treating him as a fresh beginner reopens the identity wound; meeting him where he actually is starts the repair - **Intended impact:** the reader sees why placement-at-true-level is the wedge for the switcher who cannot afford to feel like a beginner again ::: ### Persona 2: The tutorial-hell hobbyist I'm twenty-six and I've completed, conservatively, forty tutorials. I can follow any of them. I can type along with a four-hour YouTube build and end with a working app and feel, for about an hour, like a programmer. Then I open a blank editor to build my own thing and I freeze. Nothing comes. I'm in "tutorial hell," and I know the term because the whole internet knows it. A "course collector." A "tutorial addict." I "copy-code" beautifully and I can't start from a blank file to save my life. It shows up as blank-editor paralysis, and the terror is that the moment I'm on my own, I discover that everything I thought I knew was "muscle memory and pattern-matching, not real comprehension." I can recognize the right answer when it's shown to me and I can't generate it. The fear is precise: that if I start something and get stuck, "it proves I've wasted all this time." So I do the thing that feels like progress and is actually avoidance: "one more tutorial on React, then I'll be ready to build something." There's always one more tutorial. The next one is always safer than the blank file. The shame is the dependency. "I can only code when someone tells me each step." I feel infantilized next to the people who "just build stuff," and the gap between the months I've put in and what I can actually do alone "feels like a personal defect, not a normal stage." When I read the success posts, "I learned in six months and got a job," it confirms that I am "uniquely slow." The self-talk has hardened into a label: "I've done twenty tutorials and still can't build anything, so I'm just not cut out for this," and the perfectionist trap that keeps me safe in tutorials, "I need to know everything before I start, and if it's not architected correctly it's pointless." I got here because tutorials are designed to feel like learning while removing the thing that produces it, the productive struggle of being stuck and finding your own way out. The way out is graduated, scaffolded independence: tasks just past the edge of what I can do, with help that appears only after I've really tried, so the struggle is real but survivable and the win is mine. Most people never get there, because no tutorial library has any incentive to make me independent; an independent learner stops consuming content. If I stay stuck, I'll quietly conclude I'm "not a logical person" and walk away from something I'm fully capable of doing, because of a feeling manufactured by the format I was taught in. :::animation p2 **ANIMATION p2: the blank file that tutorials never let you face** - **What it shows:** a hobbyist types confidently along with a four-hour tutorial and a working app appears, then the tutorial vanishes and a blank editor stares back and nothing comes; a tempting NEXT TUTORIAL button glows as the safe escape; instead a scaffolded task appears just past the edge of what he can do, help arriving only after a genuine try, and the first line he writes alone is his - **Narrative role:** anchors persona 2, the tutorial-hell hobbyist frozen at the blank file - **What it teaches:** tutorials remove the productive struggle that produces learning; graduated scaffolded independence restores it - **Intended impact:** the reader sees why the escape into one more tutorial is avoidance and what actually breaks the loop ::: ### Persona 3: The capable non-native English speaker I'm twenty-nine, I live in Lviv, and in my own language I'm sharp. I reason well, I learn fast, I've built things. But I'm an "ESL developer" in an ecosystem that runs entirely on fast, idiomatic, native English, and the gap between my logic and my English is mistaken, by everyone including me, for a gap in my ability. It shows up at the "documentation wall." The docs assume fluent English and cultural knowledge, and I lose critical nuance on words that carry weight, "deprecate," "override," "hook," "stale," "brittle," each one a small translation tax before I can even reason about the actual problem. The error messages are nested English I have to decode before I can debug, an extra step native speakers never see. Stack Overflow answers are "fast, colloquial English," sarcasm and slang and abbreviation, and I'm never quite sure I understood the solution or whether my question will look "stupid." The conference talks and the YouTube tutorials run at native-speaker speed with no subtitles, and I'm "constantly behind." The shame is specific and it's corrosive because it attaches to identity, not skill. I interpret my slower reading as "I'm too slow to keep up with this industry." I pre-censor myself in the community: "don't ask that question, your grammar will look bad and they'll think you're dumb." I generalize a single bad day into a permanent verdict: "I couldn't follow that talk; I'll never fit into this community." And underneath it all is the attribution error that does the most damage: "if my English were better, I'd already be a good programmer; it's my fault." In the phrase non-native developers use about themselves, I'm "reduced to a child" the moment I enter an English-heavy ecosystem, fully capable in one language and made to feel stupid in another. I got here by internalizing structural bias as personal deficiency. The industry's lingua franca isn't my native tongue, and instead of seeing that as a friction the tools should remove, I see it as proof that "native speakers are naturally better at understanding complex topics; I'll always be behind." The way out is the brand's founding method: an explanation calibrated for a smart non-native English speaker, in simple words, that treats the difficulty as the explainer's job to compress rather than my deficiency to overcome. Most platforms fail people like me because every major one is built English-first and treats my confusion as a content problem to solve with more English. Getting out costs little. Staying stuck means the global talent pool loses one of its capable members to a language tax that good tooling could have erased, and I lose the career I was fully equipped for. :::animation p3 **ANIMATION p3: the translation tax at the documentation wall** - **What it shows:** a sharp developer in Lviv hits a documentation wall where each weighted word, DEPRECATE, OVERRIDE, HOOK, STALE, charges a small translation tax before he can even reason; then the same concept is re-explained in simple words with the right example, the tax drops to zero, and his real speed of thought, hidden until now, becomes visible - **Narrative role:** anchors persona 3, the capable non-native English speaker taxed by an English-first industry - **What it teaches:** the language gap is a friction the tooling should remove, not a verdict on ability - **Intended impact:** the reader sees the founding method as the direct cure for a global talent loss ::: ### Persona 4: The returning lapsed coder and the exposed manager I'm forty-one and I used to be able to do this. Fifteen years ago I wrote real code. Then I moved into management, the technical muscle atrophied, and I told myself it was fine because I still understood the shape of things. Then 2024 happened, the whole field moved under me, and now I lead a team building with tools I don't understand, and I can't say so to a single person on it. It shows up as a daily, low-grade dread. I sit in architecture reviews and nod at terms I half-recognize. My engineers ship things with Copilot and Cursor and talk about agents and context windows, and I make decisions about all of it from a position of "I should know this and I don't." The "imposter syndrome" people talk about for juniors is worse for me, because I have the title. The fear is being "found out," that someone asks me to explain a thing I approved and I can't, that the gap between my role and my actual current knowledge becomes visible. The shame is that I'm supposed to be the one who knows. "If they ask me to explain my own product's architecture, they'll realize I have no idea what I'm doing." I discount the fifteen years I do have, "anyone could do what I do, I just got lucky and got senior before AI." I won't ask my reports to teach me because the power dynamic makes the vulnerability unbearable; admitting the gap to the people I evaluate feels like professional suicide. So I stay silent in standups, I learn nothing, and the gap widens, which is the cruelest part: the silence that protects my status is the exact thing guaranteeing the eventual exposure. I got here because the field really lurched, and management is structurally positioned to fall behind and structurally forbidden from admitting it. The way out is a private, judgment-free, fast path back to the current reality, one that respects what I already know and fills the specific new gaps (what an agent actually is, what the AI tools actually do, where they fail) without making me sit through a beginner curriculum I don't need. Most managers never find one, because the only learning options are either public (a course my reports might see me taking) or beginner-shaped (insulting to fifteen years of real experience). Civilian Coder's per-learner adaptation is built for this: it meets the manager at the manager's actual level, not at a generic "module one." If I stay stuck, I make worse and worse technical decisions from a position of bluff, until the bluff fails publicly and takes my authority with it. :::animation p4 **ANIMATION p4: the private door for the exposed manager** - **What it shows:** a manager nods along in an architecture review at half-recognized terms, a widening gap between his title and his current knowledge glowing over his head, unable to ask his own reports without risking his authority; a private judgment-free door opens that respects his fifteen years and fills only the specific new gaps, an agent, a context window, where the tools fail - **Narrative role:** anchors persona 4, the lapsed coder turned exposed manager who cannot admit the gap - **What it teaches:** he needs a private path that credits what he knows and fills the exact new gaps, not a beginner curriculum - **Intended impact:** the reader sees why per-learner adaptation at true level is what reaches a buyer whose status forbids public learning ::: ### Persona 5: The subscription-rich, skill-poor vibe-coder I'm twenty-three and I pay for Claude Code and Cursor every month. I ship things. My side project works, my demos run, and from the outside I look like I can code. On the inside I'm an "autocomplete engineer," a "prompt-programmer," and I'm terrified that someone is going to find out. My situation is the wedge the whole brand is built around, and I'm living in the center of it: inside the door, standing on no floor. It shows up the moment something breaks that the AI can't one-shot. The code passes the tests and I "cannot explain it, optimize it, or debug it without re-prompting." When the model is confidently wrong, I have no foundation to catch it, so I copy the next suggestion and the next, and I drift further from understanding with every accepted completion. I "skipped the struggle," and now I'm "terrified I lack the fundamentals" even as I keep shipping working code. The fear runs in two directions at once: the immediate fear that "if my team knew how much of this came from Copilot, they'd realize I'm not a real engineer," and the existential one, "if I keep relying on AI I'll never truly learn, and when the tools change I'll be useless," sharpened by the suspicion that "companies will just hire one senior plus AI, juniors like me won't be needed." The shame is that I feel I "cheated at learning." I didn't "earn" my productivity or my portfolio. "This portfolio isn't mine, it's the AI's." And it produces a paralyzing oscillation: some days I let the AI write everything because I'm "too slow" without it, and other days I swear off it entirely because using it means I'm "cheating," and neither pole teaches me anything. The self-talk has a policing quality, "I should be able to write this function without asking ChatGPT; needing help means I'm not good enough," which is exactly backwards but feels like rigor. I got here because the tools are extraordinary at producing output and indifferent to whether I understand it, since understanding was never their job. They're productivity tools that "implicitly teach through usage but have no teaching objectives, no progress tracking, no psychological scaffolding." The way out keeps the AI and adds a system that teaches me with it: that watches what I generate, finds the conceptual gap the generation papered over, and turns my own real stuck points into the curriculum, so I move from "AI generates eighty percent of my code and I don't understand it" to "I can specify, review, and debug what the AI writes." Most people like me stay stuck because the entire market is split between tools that build for me and never teach, and courses that teach a curriculum disconnected from what I'm actually building. Civilian Coder is the only shape that closes that loop. Staying stuck means a career built on a foundation I know is hollow, lived with the daily anxiety of a fraud waiting to be caught, in a field that's about to start testing for exactly the depth I skipped. :::animation p5 **ANIMATION p5: the loop closed, not the AI removed** - **What it shows:** a young vibe-coder accepts AI completion after AI completion, drifting further from understanding with each one, oscillating between letting the AI write everything and swearing it off; then a teaching layer watches what he generates, finds the conceptual gap the generation papered over, and turns his own real stuck point into the lesson, moving him from AI WROTE 80% AND I DON'T UNDERSTAND IT to I CAN SPECIFY, REVIEW, AND DEBUG IT - **Narrative role:** anchors persona 5, the subscription-rich skill-poor vibe-coder at the center of the wedge - **What it teaches:** the cure keeps the AI and adds a system that teaches with it, mining the learner's real generation for the missing concept - **Intended impact:** the reader sees the exact loop only this brand closes, teaching with the tools rather than against them ::: ### A note on the sixth shape A self-taught teenager or Gen-Z learner sits adjacent to all five, learning to code as a native of the AI era with no professional identity yet to protect, which inverts the shame (curiosity rather than fear) while keeping the same need for scaffolded independence and a community. They are the long-tail funnel and the cultural-credibility audience rather than the acute-pain wedge, so the brand serves them but doesn't lead with them; the five above are where the conversion and the retainer revenue concentrate. --- ## 5. The world model (the PST framework run on the customer) The five personas differ in surface circumstance and converge on one structure. Running the PST framework (Problem, Story, Transformation) on that structure makes the brand's reason to exist legible. **Echolocate the world.** The first pass pings the whole market around the learner. The learner sits inside a market that has, in three years, inverted. The supply of coding knowledge went to infinite and free the moment a general model could explain anything on demand, which collapsed the value of the content library (the Chegg event) and stranded an entire generation of education businesses whose only asset was that library. At the same time the demand for the specific capability of reasoning about code, rather than producing it, went up, because the tools now produce the code and someone still has to understand it. An M&A firm reading this as a target would see that the pain is enormous and growing, the incumbents are structurally unable to address it without cannibalizing themselves, the leverage sits in the relationship and the longitudinal data rather than the content, and the cost of carrying the problem (a stalled career, a hollow foundation, a daily fraud-anxiety) vastly exceeds the cost of fixing it. Mapped as a graph, this customer is a person connected to their tools, their failed attempts, their emotional state, and their unbuilt project, and the existing market models none of that; it models which course they bought. :::animation 5a **ANIMATION 5a: the market that inverted in three years** - **What it shows:** two curves cross in an X; the SUPPLY OF CODING KNOWLEDGE curve plunges to free the instant a general model lights up, taking a stack of content-library businesses down with it, while the DEMAND TO REASON ABOUT CODE curve climbs because the tools now write the code and someone still has to understand it; the crossing point glows as the opening - **Narrative role:** anchors the echolocate step, the three-year inversion of the market the learner sits inside - **What it teaches:** content went free while the demand to reason about code rose, stranding library businesses and opening a gap - **Intended impact:** the reader sees the structural opening the brand is built into rather than a generic market claim ::: **Locate the Problem (the cycle of suffering).** The learner is stuck at a specific point, and it's the same point across all five personas. Pain arrived: a rejection, a failed build, a broken thing the AI couldn't fix, a term they didn't understand in a meeting. In response a fear got installed and then over-invested in, and it's always a variant of the same fear: "I am not a real programmer." That fear drives avoidance, one more tutorial instead of the blank file, silence in the standup instead of the question, swearing off the AI instead of learning with it. The avoidance produces the unfavorable outcome, no independent project, no closed knowledge gap, no job. The outcome produces shame, which turns "I did a bad thing" into "I am a bad thing": I'm stupid, I'm a fraud, I'm not cut out for this, I'm not a logical person. That belief is unbearable, so it gets buried under denial and cope, "coding is gatekept," "the bootcamp scammed me," "I'm too old," "I'm too slow," "native speakers are just better," "AI ruined the field." Every one of those is a way to avoid the one forbidden move, the red line, which is accountability: turning around to face the buried belief and recognizing that the wall is internal wiring, not external fact. Refusing that turn opens the blind spot, more avoidance, more tutorials, more silence, more drift, which produces more pain, and the loop closes and compounds. The fear portfolio driving it is a terrible investment: heavy positions in the fear of exposure, the fear of having wasted irrecoverable time and money, and the fear of being fundamentally, permanently not-enough, none of which pays a return and all of which chips away at the identity. :::animation 5b **ANIMATION 5b: I did a bad thing becomes I am a bad thing** - **What it shows:** the loop turns through its stations, pain then installed fear I AM NOT A REAL PROGRAMMER then avoidance then a bad outcome then shame; at the shame station the caption visibly rewrites itself from I DID A BAD THING to I AM A BAD THING, and the exit marked ACCOUNTABILITY is blocked by a red line while copes stack over it, the bootcamp scammed me, I am too old, native speakers are just better - **Narrative role:** anchors the locate-the-problem step, the cycle of suffering and its load-bearing shame move - **What it teaches:** the shame converts a bad result into a verdict on the self, and the forbidden move out is accountability - **Intended impact:** the reader sees why comfort fails and why the exit is turning to face the buried belief ::: **Reconstruct the Story (the belief structure and its origin).** Repeated emotional experiences built the belief structure these learners run on long before the coding attempt. The chain is the standard one: emotional experiences, repeated, harden into belief structures, which drive actions, which produce results, which become habits, which become personality. The belief at the root is almost always some early-installed "you're not technical," "you're not a math person," "smart means it comes easy and it does not come easy to you," delivered by a teacher, a parent, a humiliating moment in a math class before the person had the vocabulary to defend against it. That belief made the first confusion in coding feel like confirmation of an old verdict instead of a normal stage. The career-switcher's belief that the bootcamp failure is a personal defect, the hobbyist's belief that being stuck means "not a logical person," the non-native speaker's belief that slowness in English is slowness of mind, the manager's belief that not-knowing-now erases fifteen years of knowing, the vibe-coder's belief that needing the tool means not being good enough, are all the same old belief wearing five costumes. Under that sits the shame most people won't look at: at some level the person has accepted the verdict and organized years of avoidance around never confirming it again. Demographics throw that identity-deep read away, and PST is built to act on it. :::animation 5c **ANIMATION 5c: the old verdict wearing five costumes** - **What it shows:** a single early-installed belief, YOU ARE NOT TECHNICAL, YOU ARE NOT A MATH PERSON, delivered by a teacher or parent in a childhood classroom, then walks forward wearing five costumes in turn, the switcher, the hobbyist, the ESL developer, the manager, the vibe-coder, the same figure underneath each; the first coding confusion lands on it and it reads as confirmation of the old verdict - **Narrative role:** anchors the reconstruct-the-story step, the belief structure and its origin - **What it teaches:** the five personas run one early belief in five disguises, which is why the confusion feels like proof - **Intended impact:** the reader sees the origin the demographics discard and why the wound is identity-deep ::: **Design the Transformation (the cycle of growth).** The brand's job is to build a bridge the learner can cross without being mugged by their own shame. The hinge is courage, the point that separates the suffering loop from the growth cycle, and gamification is the scaffold that makes courage repeatable on the days it would otherwise fail. The product walks the learner across in sequence. Truth comes first: the accurate, uncomfortable read that the wall is the explanation and the wiring rather than the intelligence, delivered through the founding method that assumes the learner is smart and treats the difficulty as the system's job to compress. Responsibility follows: owning the reaction to the wound rather than the wound itself, the one thing that's theirs, turned into the small daily action the platform makes just achievable enough to take. Then comes healing, which hurts: the productive struggle of the blank file the tutorials removed, the bug the learner sits with, the concept that finally lands after the third different explanation, scaffolded so the struggle is real but survivable. Forgiveness closes it, letting go of the could-have and should-have, the wasted bootcamp money, the years of avoidance, and the old "not technical" verdict, which opens the eyes to a new truth (I can actually do this) and loops the cycle upward instead of down. The product is the bridge, the cohort is the company on the crossing, the coach is the hand, and the per-learner model is what keeps the calibration right so the next step is always crossable. :::animation 5d **ANIMATION 5d: the four-step crossing** - **What it shows:** a learner crosses a bridge built in four labeled planks, TRUTH the wall is the explanation not your intelligence, RESPONSIBILITY the small daily action that is yours, HEALING the real productive struggle that survivably hurts, FORGIVENESS dropping the wasted money and the old verdict; a cohort walks alongside and a coach's hand steadies, and on the far bank the loop turns upward instead of down - **Narrative role:** anchors the design-the-transformation step, the cycle of growth the product walks the learner across - **What it teaches:** the transformation is a calibrated crossable bridge of truth, responsibility, healing, forgiveness, scaffolded so courage repeats - **Intended impact:** the reader sees the growth cycle as a concrete sequence the product embodies, not an aspiration ::: **Bias to the negative.** Fewer than ten percent of people spend real time in the constructive emotions, so the content, the copy, the onboarding, and the daily loop must meet the learner where they actually are, in the trench of the shame and the fear, and earn the right to point at the growth cycle by first proving the system understands the suffering better than the learner does. That's what converts, and it's why the personas are written in their own pain language rather than the language of aspiration. --- ## 6. Competitive and market read (the alpha / third door) **The market.** Adult online programming education is a $10B to $30B global market in 2024, growing at low-double-digit CAGR into 2026, with tech skills at the higher end of the e-learning growth band. [VERIFIED, composite] Learner counts run into the low tens of millions of active adult learners annually across MOOCs, bootcamps, and platforms; Coursera alone reports around 124M registered learners with computer-science and data consistently among its largest domains, and Code.org's 90M-plus K-12 accounts are the top of a funnel that feeds adult upskilling. The AI-coding-education subsegment isn't yet reported as a standalone category but is plausibly already a multi-billion-dollar slice by 2026, pulled by enterprise reskilling (institutions explicitly funding AI-coding-tool training for tens of thousands of developers) and consumer AI-tool subscriptions. The demand signal is unambiguous and the segment is real. **The incumbents, and what each refuses to do.** The field sorts into three modalities. Content libraries and marketplaces (Udemy, Coursera, Pluralsight, much of DataCamp) monetize access to mostly static content at near-zero marginal content cost per learner; their economics depend on that, which is why they structurally can't pivot to high-touch per-learner agentic adaptation without raising their cost-per-learner and cannibalizing the library that is their asset. Interactive platforms (Codecademy, freeCodeCamp, Scrimba, Boot.dev, Codedex, Exercism, Brilliant) run in-browser exercises with autograders and light gamification, and several are genuinely good at the interactive layer, but they're curriculum-and-content platforms at heart; going full agentic tutor that orchestrates the learner's external tools and models emotional state is a different product with higher per-learner cost and far less content leverage, so they add AI hints rather than rebuild around an agent. The AI-native tools (Replit Ghostwriter, GitHub Copilot, ChatGPT-as-tutor, Cursor, Claude Code) are productivity tools, not teachers: ChatGPT adapts at the session level but holds no persistent learner model, no longitudinal curriculum, no accountability; Copilot and Cursor implicitly teach through usage but have zero teaching objectives, progress tracking, or psychological scaffolding, and they assume a baseline literacy the wedge customer lacks. [All VERIFIED, competitive pass] :::animation 6a **ANIMATION 6a: three modalities, each with a locked door** - **What it shows:** three columns stand side by side, CONTENT LIBRARIES with a vast static shelf, INTERACTIVE PLATFORMS with autograded exercises and light gamification, AI-NATIVE TOOLS shipping code fast; each column has a door marked PER-LEARNER AGENTIC ADAPTATION that is padlocked, a caption on each lock naming why opening it would break that column's economics or positioning - **Narrative role:** anchors the §6 incumbent read, the three modalities and what each structurally refuses to do - **What it teaches:** every incumbent modality is locked out of the same move for its own structural reason - **Intended impact:** the reader sees the competitive field as three groups that all decline the same ground ::: **The third-door alpha.** Alpha, the investor's word for an edge, is the thing competitors know about, have likely tried, and won't do, because it doesn't make sense for their structure. The alpha here is the combination, not any single element: per-learner agentic personalization that is tool-centric (teaching with the learner's Claude Code and Copilot, against their real project and their real stuck points, not about coding in the abstract), fused with emotional-state-aware pedagogy where the detected state drives an explicit policy (when to switch from open-ended generation to scaffolded code, when to drop to a smaller subtask, when to insert a morale win), fused with gamified accountability deeper than streaks (weekly missions tied to a real portfolio, squad-based commitment, the limited-AI-reveal mechanic that nudges effort before help). Content libraries can't run this at their unit economics. AI tools won't build the beginner-focused pedagogy stack because it slows their productivity positioning for advanced users. The market pass pressure-tested this hypothesis and confirmed it directionally while sharpening it: the wedge must be the AI-first-beginner archetype specifically, the personalization must be tool-centric and outcome-tied rather than "better recommendations," and the durable moat, once the architecture is inevitably copied, is the proprietary longitudinal trace of real learner behavior in real coding workflows plus proven outcomes (job placement, time-to-ship, reduced AI-introduced defect rates). That moat is precisely the per-user result-tracking in Andy's seed. :::animation 6b **ANIMATION 6b: the third door is the combination** - **What it shows:** three separate capabilities orbit apart, TOOL-CENTRIC PERSONALIZATION teaching against the learner's real project, EMOTIONAL-STATE-AWARE PEDAGOGY where detected state drives an explicit policy, GAMIFIED ACCOUNTABILITY deeper than streaks; they fuse into one glowing device that the incumbents cannot run at their unit economics, and behind it a slow-accumulating vault labeled LONGITUDINAL TRACE PLUS OUTCOMES fills as the real moat - **Narrative role:** anchors the third-door alpha in §6, the combination competitors will not do - **What it teaches:** the alpha is the fusion of three elements plus the proprietary outcome data, not any single feature - **Intended impact:** the reader locates the specific edge and its durable moat rather than a vague better-product claim ::: **The Wardley read (what to own versus rent).** A Wardley map places each capability on an axis from genesis (new and custom) to commodity. Curriculum content is a commodity racing to free, and it must be rented or harvested rather than custom-built; the spaced-repetition scheduler (FSRS, SM-2) and the code-execution sandbox primitives are products to rent or compose, not invent. The generic AI tutor ("ask AI about this lesson") is productizing fast and will be table stakes within the year, so building it earns no durable edge. The alpha sits at genesis-to-custom and is where the brand builds and owns: the PST-aware adaptive engine that maps detected emotional state and mastery to a pedagogy policy, and the per-learner metagraph profile that makes the personalization real and accumulates the moat-grade longitudinal data. [Evolution stages INFERRED from reception evidence; tools move stages fast, so this is an evidence-tagged claim, not a fixed truth.] Own the engine and the profile, rent the content and the sandboxes, harvest the gamification mechanics, and let the AI coding tools be the strong coding engines the brand sits on top of as the learning-and-behavior layer. :::animation 6c **ANIMATION 6c: own the left, rent the right** - **What it shows:** a Wardley evolution axis runs left to right; on the commodity right sit curriculum content racing to free, spaced-repetition schedulers, and code sandboxes, each stamped RENT OR HARVEST; on the genesis-leaning left sit the PST-aware adaptive engine and the per-learner metagraph profile, stamped OWN, glowing as the only two things the brand builds itself - **Narrative role:** anchors the Wardley build-versus-rent read in §6 - **What it teaches:** the durable edge is owning the adaptive engine and the learner profile while renting everything commoditizing - **Intended impact:** the reader sees exactly which two capabilities earn ownership and which are wasteful to build ::: --- ## 7. The build (where Track R will feed Track P) Modern adaptive learning runs on several narrow engines glued together rather than one big AI, which suits the harness-and-feature-factory shape. [VERIFIED, build pass] **The harness shape and the feature factories.** Civilian Coder is a set of feature factories with clean domain boundaries, each maintained largely automatically by a dedicated harness: curriculum generation, assessment and grading, the personalization engine, community and social, and progress analytics. The agent roster the domain needs is concrete: a curriculum-author agent (produces lessons, exercises, and explanations as structured documents), a tutor-and-explainer agent (the calibrated, non-native-English-friendly explanations, with tiered model routing), an assessor agent (grades submissions, extracts error signals), a personalizer agent (updates the learner model and chooses the next task), a community-moderator agent, and a progress-analyst agent (the outcome tracking that is the trust mechanism and the corpus engine). The hard, ownable parts the alpha lives in are the content modeling (mapping exercises to a skill graph with calibrated difficulty and prerequisites), the trustworthy mastery estimate, and the pedagogy policy that decides when to recap, escalate, or slow down; the commodity parts (the FSRS scheduler, the BKT or IRT knowledge-tracing primitives, the sandbox) are composed in. :::animation 7a **ANIMATION 7a: the agent roster on the harness** - **What it shows:** six labeled agents take stations around a central spine, a curriculum-author, a tutor-and-explainer with tiered model routing, an assessor, a personalizer choosing the next task, a community-moderator, a progress-analyst; three of the surfaces they touch glow brighter and marked OWNABLE ALPHA, the calibrated skill graph, the trustworthy mastery estimate, the pedagogy policy, while commodity primitives snap in from the side - **Narrative role:** anchors the top of §7, the harness shape and feature factories - **What it teaches:** the domain decomposes into narrow agents on one spine, with the alpha concentrated in three ownable surfaces - **Intended impact:** the reader sees the build as a maintainable roster rather than one monolithic AI ::: **The data models (ECS / Pydantic-IR).** The data model is a small set of typed entities, the same discipline the sibling brand Scatter Model uses. The core entities and their components: a `Skill` (name, description, prerequisites, tags, difficulty parameter); an `Item` (type, mapped skill ids, difficulty, estimated time, language, test suite); a `Learner` (preferences, goals, locale); a `LearnerSkillState` (mastery probability, last practiced, times practiced, per-learner ability offset); a `LearnerItemHistory` (attempt index, outcome, time spent, hints used, code snapshot, error signals); a `SpacedRepCard` carrying the FSRS parameters; and, the component that makes this brand different from a generic intelligent tutoring system (ITS), an `EmotionalState` / `EngagementMetrics` / `FrustrationSignals` set (session length, sessions per week, repeated wrong attempts on one skill, high hint-reveal usage, drop-off after a hard item, plus coarse LLM-derived confidence and affect tags gathered with explicit consent). That emotional component is the per-learner RPG profile's most valuable axis, it's what feeds the PST pedagogy policy ("user is struggling with loops, be more step-by-step"), and it's the signal the metagraph and Graphiti's bi-temporal model are built to hold across the before-and-after of a learner's understanding. [Data model VERIFIED as a buildable pattern; the emotional-axis extension is the brand-specific INFERRED design move] :::animation 7b **ANIMATION 7b: the emotional axis makes the profile different** - **What it shows:** a stack of typed entities assembles into one learner genome, Skill, Item, Learner, LearnerSkillState, LearnerItemHistory, SpacedRepCard, and then one more block snaps on top glowing brighter than the rest, EMOTIONAL STATE AND ENGAGEMENT SIGNALS, drop-off after a hard item, repeated wrong attempts, high hint usage; that block feeds a policy line reading STRUGGLING WITH LOOPS, BE MORE STEP-BY-STEP - **Narrative role:** anchors the §7 data-models paragraph, the ECS genome and its brand-specific emotional axis - **What it teaches:** the emotional-and-engagement component is the axis that separates this from a generic tutoring system - **Intended impact:** the reader sees the data model as the concrete place the PST pedagogy actually lives ::: **The economics, kept sane.** The LLM is where unit economics live or die. A heavy learner uses roughly 30k tokens a day; on a frontier model that's about $1.80 a month, on a self-hosted cheap open model about $0.30. [VERIFIED, build pass] The disciplines that hold the cost under the ARPU: tiered model routing (a small fine-tuned model for routine hints, encouragement, and scaffolding; a frontier model only for complex debugging and nuanced review), short-context-plus-RAG rather than dumping full learning history into the window, semantic caching of system prompts, standard-error explanations, and exercise descriptions (realistic 20-to-40 percent hit rates), response-length control, fixed-turn flows, and fair-use caps that double as a gamification mechanic. Code execution is sub-cent per active learner per day if engineered well: in-browser Pyodide and native JavaScript for cheap instant feedback, a hosted Judge0-style API while under roughly 10k monthly actives, and a self-built Kubernetes sandbox (containers with seccomp and apparmor, or Firecracker micro-VMs) once scale justifies it. That's the reason behind Andy's rule of running on cheap open-source models: the bulk modeling and the bulk teaching run on cheap models, the frontier model is reserved for the moments that need it, and the margin survives. :::animation 7c **ANIMATION 7c: tiered routing keeps the margin alive** - **What it shows:** a stream of learner requests hits a router that sends routine hints, encouragement, and scaffolding down a wide cheap lane to a small fine-tuned model, and sends only complex debugging and nuanced review up a narrow lane to a frontier model; a cost meter reads about a dollar-eighty a month per heavy learner against a higher ARPU line, and a cache labeled SEMANTIC catches repeated prompts before they cost anything - **Narrative role:** anchors the §7 economics paragraph, the unit-cost discipline that keeps cost under ARPU - **What it teaches:** tiered model routing plus caching runs bulk teaching cheap and reserves the frontier model, so margin survives - **Intended impact:** the reader sees the cheap-models discipline as the concrete reason the business math works ::: **The medallion tiers and the access model.** The medallion asset tiers (bronze, silver, gold, and diamond, rising in value) map onto the membership: bronze is the free and public lessons (the funnel and the cultural-credibility layer for the sixth shape); silver and gold are the personalized membership with the full adaptive engine, the gamified shell, and the cohort; diamond is the one-to-one human-master mentorship plus the always-on agentic coach and the employer-cohort engagements, which is where the service angle's retainer revenue concentrates. Access rises with tier, and the result-tracking that proves outcomes is what justifies the diamond price. :::animation 7d **ANIMATION 7d: bronze funnel to diamond outcome** - **What it shows:** the medallion stack lights in order, bronze as free public lessons drawing a wide funnel of newcomers in, silver and gold as the personalized membership with the full adaptive engine and cohort, diamond as one-to-one human-master mentorship plus the always-on coach and employer cohorts; a proof badge marked TRACKED OUTCOMES sits beside diamond and justifies its price - **Narrative role:** anchors the §7 medallion-tiers and access model - **What it teaches:** the tiers rise from a free funnel to outcome-proven diamond mentorship, and tracked results justify the top price - **Intended impact:** the reader sees how the membership ladder maps onto the data tiers and where the retainer revenue concentrates ::: **Where the repo research feeds the build.** The list of open-source repos to study isn't provided yet, so the specific repos are OPEN. The capabilities to source from that research are nameable now: an adaptive-assessment / knowledge-tracing implementation, a spaced-repetition engine (FSRS reference), a safe code-execution sandbox, and a semantic-caching layer for the LLM tier. Each will get its own deck `.md` and be ranked against the others in the value rubric; this deck's job is to name the demand so the supply side can be matched to it. Among the brand builds, Civilian Coder uses the shared Looikos components by reference rather than by copying: Story Factory for the curriculum templates, Scatter Model for the learner profile and the dynamic prompt layer, WikiDesignCo and Graphiti for the knowledge and the temporal learner store, and the harness for the maintainability. [Repos OPEN; primitive dependencies INFERRED from the ecosystem map] :::animation 7e **ANIMATION 7e: named demand waiting for supply** - **What it shows:** four labeled sockets sit empty and outlined in dashed lines marked OPEN, a knowledge-tracing engine, a spaced-repetition reference, a safe code-execution sandbox, a semantic-caching layer; beside them four solid ecosystem primitives already plug in, Story Factory, Scatter Model, WikiDesignCo with Graphiti, the harness, so the deck shows exactly which dependencies are filled and which await Track R - **Narrative role:** anchors the §7 Track-R-feeds-Track-P paragraph, the explicit build gaps - **What it teaches:** the brand names its open repo demand precisely and reuses existing primitives by reference rather than copying - **Intended impact:** the reader trusts the build to state its own gaps honestly and to reuse the shared components ::: --- ## 8. Priority read (feeds the value rubric) This read feeds the cross-brand ranking, which weighs every brand against the value rubric `VALUE_RUBRIC.md`. **Dependencies.** Civilian Coder is a leaf, not a substrate. It depends on promises kept elsewhere: the harness (the dispatch and maintenance spine), the Scatter Model learner-profile and dynamic-prompt primitive, and a code-execution sandbox capability. Its alpha (the PST-aware adaptive engine and the per-learner metagraph profile) can't be stood up before those foundational promises exist, and the rule that a brand waits on the promises it depends on keeps it out of the Now tier, the first of the four Looikos tiers (Now, Next, Watch, and Leave), however attractive it scores. :::animation 8a **ANIMATION 8a: the leaf blocked by unkept promises** - **What it shows:** a promise graph where Civilian Coder is a leaf near the top whose three foundational dependencies below it, the harness, the Scatter Model profile primitive, a code-execution sandbox, are still unlit; the leaf's own attractiveness score glows bright but a gate stays shut because the promises beneath it are unkept - **Narrative role:** anchors the §8 dependencies read, the leaf-not-substrate position - **What it teaches:** the brand's alpha cannot stand up before its foundational promises exist, which blocks the Now tier - **Intended impact:** the reader accepts the hold as a sequencing fact rather than a doubt about the concept ::: **Leverage.** Standing Civilian Coder up won't clear the way for other brands the way a substrate does, and its leverage is a different, real kind: it's a demand-generation asset (a large consumer funnel into the ecosystem), a dogfooding asset (it exercises the personalization, the emotional modeling, and the gamification primitives harder than almost any other brand, surfacing their defects early), and a corpus asset (the longitudinal learner traces feed the simulation compiler). Those are genuine, but they're downstream of the substrate being ready. :::animation 8b **ANIMATION 8b: demand asset, dogfood asset, corpus asset** - **What it shows:** Civilian Coder sits in the center feeding three distinct outputs outward, a wide consumer funnel labeled DEMAND pouring learners into the ecosystem, a stress-test labeled DOGFOOD exercising the personalization and emotional and gamification primitives until their defects surface, and a data stream labeled CORPUS feeding the simulation compiler; all three arrows point downstream of a substrate marked NOT YET READY - **Narrative role:** anchors the §8 pull read, the three real kinds of pull that are not structural-unlock - **What it teaches:** the brand's pull is demand, dogfooding, and corpus, all genuine but downstream of the substrate - **Intended impact:** the reader places the pull correctly as valuable but not a reason to advance the brand ahead of its substrate ::: **Readiness.** The brand is concept-stage with no repo. The market, by contrast, is hot and the wedge is timely, which is a reason to keep it warm, not a reason to pull it forward past its dependencies. **The seven-sins check on this read.** The seven sins are the ways an analysis fools itself, and four of them are checked here. Pride and look-ahead: the score mustn't assume the harness, Scatter Model, or the sandbox already exist; they don't, so the brand is scored on the present and the dependency is flagged, not wished away. Envy and survivorship: the competitive read deliberately pulled the failure case (Chegg) and the structural reasons incumbents won't move, not only the Duolingo success story. Lust and capacity delusion: this is one of roughly forty brands, and adopting it before its substrate is the exact over-reach the gate exists to catch. Greed and fat-tail: the tail risk is real, a frontier-model price shock or a platform (Anthropic, OpenAI) shipping a competent persistent AI tutor natively would compress the window, which is why the moat is staked on the longitudinal data and the outcomes rather than on the adaptive architecture alone. **First-pass tier: Next, gated on substrate.** It isn't Now, because its foundational dependencies aren't kept yet and committing to a leaf before its substrate exists is the classic failure the rubric guards against. It isn't Watch either, because the demand is verified, the wedge is sharp, and the brand is a strong dogfood-and-corpus asset rather than a speculative bet. The instinct is Next: build it as soon as the harness, the Scatter Model profile, and a sandbox capability are real, and in the interim let the free bronze tier and a thin CLI coach run as a probe that begins accumulating the longitudinal data the moat depends on. [Tier INFERRED, pending the strategist's cross-brand reconciliation and the Track-R wish-list.] :::animation 8c **ANIMATION 8c: Next, gated on substrate, probing meanwhile** - **What it shows:** a status dial reads NEXT rather than NOW or WATCH, held there by a gate marked SUBSTRATE, the harness, the Scatter Model profile, a sandbox; while it waits, a thin probe runs in the corner, a free bronze tier and a lightweight CLI coach quietly filling a jar labeled LONGITUDINAL DATA so the moat begins accruing before the full build starts - **Narrative role:** anchors the §8 Now/Next/Watch call and the interim probe - **What it teaches:** the call is Next gated on substrate, with a bronze-and-CLI probe accumulating the moat data in the interim - **Intended impact:** the reader leaves with a concrete sequence and an action to take now rather than a vague later ::: --- ## 9. The brand's own nine-rung position Distinct from the research-lane frame in the header; this is Civilian Coder itself. :::animation 9a **ANIMATION 9a: the brand as one derivation chain** - **What it shows:** the nine rungs stack from Purpose at the rails down through Mission, Objective, Initiative, Project, Task, Action, Decision, Data, to Event, each rung filling with Civilian Coder's own content, treat confusion as an explanation problem, prove it with tracked outcomes, run five feature factories, walk one learner through one skill, serve the next crossable step, log a skill mastered and a job landed, so the whole brand reads as one chain from purpose to captured event - **Narrative role:** anchors §9, Civilian Coder modeled as an operating business for the metagraph - **What it teaches:** the brand is a full nine-rung derivation from purpose to logged outcome, not a pitch - **Intended impact:** the reader sees the brand resolve into a governable chain the metagraph can hold and query ::: - **Purpose (the rails):** democratize real coding capability for the people the industry locked out, by treating confusion as an explanation problem to be solved, not a verdict on intelligence. - **Mission (rung 1):** build the accessible, agentic, personalized coding-education ecosystem that takes a learner from stuck to genuinely able, and proves it with tracked outcomes. - **Objective (rung 2):** a premium-membership platform with measurable learner outcomes (independent project shipped, job placed, AI-generated code understood and debugged), floored at the $10M three-angle valuation. - **Initiative (rung 3):** the consumer membership, the employer L&D service line, and the diamond mentorship tier, run as one platform. - **Project (rung 4):** the five feature factories (curriculum, assessment, personalization, community, analytics) on the harness. - **Task (rung 5):** a single learner's path through a single skill, from diagnosis to mastery. - **Action (rung 6):** the daily mission, diagnose state, set the next crossable step, teach against the real stuck point, debrief with an emotional check-in. - **Decision (rung 7):** the pedagogy policy, given mastery and emotional state, what to serve next (recap, escalate, scaffold, or insert a morale win). - **Data (rung 8):** the per-learner RPG profile, the skill graph, the mastery states, the emotional and engagement signals, the full interaction history. - **Event (rung 9):** a task attempted, a skill mastered, a streak held, a project shipped, a job landed, each captured as the outcome that builds the trust and feeds the corpus. --- ## 10. Sources **Method.** A1 ingested Andy's seed from `../../looikos_andy_transcript.md` lines 996-1015 (the canonical recorded source; `LOOIKOS_ECOSYSTEM.md` is a stub and carries no per-brand seed). A2 built a word-targeted skeleton before any prose (skeleton-of-thought discipline). A3 ran three sequential Perplexity passes, each informed by the last, never parallel-blasted. A4 ran PST on each persona. A5 wrote each section incrementally (under ~1500 words per pass). A6/A7 self-check and hand-off. **Perplexity queries (verbatim, sonar-pro, sequential):** 1. Market and competitors and M&A read for an agentic coding-education product (TAM and growth; incumbents by modality and what each refuses to do; post-2020 edtech M&A comps and multiples; the Chegg cautionary tale; the strategic gap, with an explicit pressure-test of the per-user-agentic-personalization-plus-emotional-plus-gamified-accountability hypothesis). Fed sections 3a, 6, and the seed decompression. Citations surfaced included defensescoop.com (DoD AI-coding RFI), code.org, nobleprog.com, cloud.google.com. 2. The Lexicon of Pain / Voice of Customer for struggling coding learners, requested as the recognized community idioms plus the fear / shame / self-talk analysis per situation (tutorial hell; imposter syndrome; bootcamp-burned; 2024-2026 AI-dependence anxiety; non-native English speakers). The first form of the query was declined on bulk-copy grounds; reframed to the documented-terminology-and-emotional-analysis form, which returned the material. Fed section 4 (all five personas) and section 5. Citations included codecademy.com/resources/blog (common obstacles), dev.to (barriers for non-native English speakers), a UCSD CHI-2018 paper on non-native English speakers learning programming. 3. The build reality for an AI-native adaptive coding platform (knowledge tracing BKT/IRT/DKT, FSRS/SM-2 spaced repetition, browser code-execution sandboxes via Pyodide/Judge0/containers, LLM unit economics and cost-control, gamification that retains versus shallow gamification, the per-learner data model). Fed sections 3b, 7, and the Wardley read in 6. Citations included sciencedirect.com (gamification and engagement in adaptive platforms), coursera.org/articles/adaptive-learning, dl.acm.org, forasoft.com. **Voice-of-Customer channels named in the research** (as the documented homes of the patterns, referenced not scraped): r/learnprogramming, r/cscareerquestions, the freeCodeCamp forum, dev.to, Hacker News, bootcamp-review sites, and the academic literature on non-native English speakers in programming. **Ecosystem and discipline docs cross-referenced** (by reference, single-source-of-truth): `LOOIKOS_ECOSYSTEM.md` (the seed and the three-angle model), `THE_PST_FRAMEWORK.md` (the world model in section 5), `symphony/stack-recon/_PROJECT_TEMPLATE.md` (the contract), `VALUE_RUBRIC.md` (the priority read), `SKELETON_OF_THOUGHT_WRITING.md` and `the-disconnection.md` (the disciplines). The Scatter Model, Story Factory, and WikiDesignCo references point at their own ecosystem entries and future decks rather than restating them. **Evidence-tag legend.** VERIFIED = market data, M&A comps, build patterns, or competitive facts confirmed in the Perplexity passes, or Andy's primary seed. INFERRED = faithful decompression or design judgment grounded in the verified material. OPEN = not yet knowable (the Track-R repo list; exact Civilian Coder pricing; the strategist's final priority tier).