SuperHarness · Looikos

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

Field	Value
Project	SuperHarness
Looikos cluster	Infrastructure & Agent Platforms (the harness layer itself)
One-line	The brand under which Andy teaches harness engineering, releases stress-tested open-source Hermes-based harness plugins, and sells multi-five-figure harness buildouts. The renamed, recentered successor to Symphony AGI, anchored on the domain name Andy secured.
Status	Active brand direction as of 2026-07-03. SUPERSEDES as the brand identity; that deck's market read, valuation comps, personas, and feature-factory analysis remain in force and are referenced here, not repeated. The Hermes/Harness V2 build continues under this name.

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

SuperHarness is the harness engineering brand of the Looikos ecosystem: the public identity under which Andy teaches the discipline, releases stress-tested open-source plugins for the Hermes scaffold, and sells multi-five-figure harness buildouts to organizations whose agentic ambitions have outgrown their duct tape. A harness, in this vocabulary, is everything around the model that turns raw intelligence into dependable work, and the brand's central claim is anatomical: the industry is still arguing definitions and semantics, but every serious harness resolves into the same set of organs (prompts, skills, personas, model selection, hooks, reference material, templates, agent SOPs, data models, integrations, memory, evaluation, observability, continuous integration, workflows, loops, error handling, navigation, operations), and the engineering practice that treats them as one body is what separates a demo from an operation. The name is new as of 2026-07-03, anchored on the domain Andy secured; the substance beneath it is the live Harness V2 build the Symphony AGI deck documented, recentered from "orchestration platform" toward "the discipline, taught and sold." Symphony AGI's conducting philosophy survives intact inside it: you do not manage a swarm by adding players, you conduct it by understanding what the piece is for.

1Animation · placeholder

demo versus operation

What it showstwo side-by-side rigs built from the same prompt-plus-model core; the left rig runs bare and buckles the moment a second task arrives, the right rig has the harness organs wired around the same core and absorbs the same load without a stumble

Narrative roleanchors the central claim of §1, that the harness is what separates a demo from an operation

What it teachesthe model is the smallest part; the apparatus around it is what makes work dependable

Intended impactthe reader stops crediting the model for reliability and starts crediting the harness

Animation will go here. This is the brief; the motion designer builds from it.

2. Andy's seed, expanded (the 2026-07-03 recentering)

Andy's framing (2026-07-03 directives, condensed with fidelity): SuperHarness is "a Hermes-based harness" brand. The process he designed and is building for himself is powered by OpenAI's Codex as the most powerful coding model, with Claude Code as the orchestrator and personal-assistant layer (driven through the desktop app or through Warp in the terminal), and open source carrying the heavy lifting and parallel execution when multiple perspectives are wanted. A harness breaks down into coherent parts with specialized systems in each: the prompts (,, readmes, "a ton of different markdown files"), skills, personas, model understanding and testing, hooks, reference materials and examples, Jinja templates and the process for managing and updating them, guides and SOPs for agents, data models grounded in Pydantic-as-IR (the discipline ScatterModel productizes; see the scatter-model deck for canon), integrations across the agent protocols (MCP, A2A, ACP, ADK, GUIs, "there's so many of them"), memory (with WikiDesignCo as part of it), evaluation rubrics, observability, continuous integration pipelines and feature factories, workflows (orchestrations, LangGraph, DAG-thinking like Airflow), loops ("the modern version of prompts... a big part of what makes agents so powerful now"), errors and retries for reliability and durability, navigation (CLI, grep, APIs, "they need to navigate it somehow"), and operations (an operational ledger with the nine-stage hierarchy, "kind of like a CRM... built in directly to harnesses"). His conviction, verbatim in spirit: it is so early that people are still arguing about semantics, but all of these are going to be vital, "like the parts of a cell, the organs of a body." The brand builds notoriety by intermittently open-sourcing stress-tested pieces, and monetizes as teaching plus "multi five-figure harness buildouts."

Reading between the lines. Three moves sit inside the recentering.

First, the rebrand shifts the product from platform to practice. Symphony AGI was framed as the thing you run on; SuperHarness is framed as the thing you learn and hire. That is a sharper wedge into the same market the Symphony AGI deck mapped, because the buyer's trust problem (a hundred wrapper demos, a fear of science projects) is answered better by a named discipline with a public body of work than by another platform pitch. The platform does not disappear; it becomes the reference implementation the practice teaches from, which is the same artifact-is-the-demonstration move the whole ecosystem runs.

2aAnimation · placeholder

ANIMATION 2a: platform becomes practice

What it showsa boxed product labeled PLATFORM turns inside out; its walls fold back to reveal a lit workshop where the same components hang on the wall as teachable modules, tools a person picks up rather than a box they rent

Narrative roleanchors the first recentering move, platform to practice

What it teachesthe rebrand sells the discipline you learn and hire, not the thing you run on

Intended impactthe reader sees why a named practice answers the buyer's trust problem better than another platform pitch

Animation will go here. This is the brief; the motion designer builds from it.

Second, the Hermes trio assigns model classes to seats instead of betting the brand on any one model. Codex takes the heavy-coder seat because it is the strongest pure implementer; Claude Code takes the orchestrator seat because holding context, dispatching, and grading is its home ground; open-source workers take the parallel fan-out seats because multiple cheap perspectives beat one expensive one on wide problems, with a stronger model synthesizing the winners. The scaffold is the constant and the seats are swappable, which is the same model-agnostic credit-quality argument the Symphony AGI deck made in its finance angle: the harness proven on the cheaper model upgrades in one line.

Third, the anatomy is the curriculum, and the curriculum is the moat. Enumerating the organs is not taxonomy for its own sake. Each organ is a teachable module, a sellable buildout component, and an open-sourceable plugin surface, which means the brand's three revenue motions (teach, release, build) all decompose along the same lines. A competitor can copy any single released plugin; copying the assembled anatomy, with the tested judgments about how the organs compose under production load, requires the operational corpus, and that corpus lives in WikiDesignCo where it compounds privately.

2bAnimation · placeholder

ANIMATION 2b: the copyable plugin, the uncopyable assembly

What it showsa rival lifts one glowing plugin cleanly off the anatomy and clicks a perfect copy into their own rig; then they reach for the whole assembled body and their hands pass through it, because the connective tissue of tested compose-judgments lives in a private corpus they cannot reach

Narrative roleanchors the third recentering move, the anatomy as the moat

What it teachessingle parts are free to copy, the assembled judgment about how they compose is not

Intended impactthe reader understands why open-sourcing pieces strengthens rather than leaks the moat

Animation will go here. This is the brief; the motion designer builds from it.

2Animation · placeholder

the Hermes trio

What it showsthree labeled engines docking into one scaffold: CODEX into the heavy-coder bay, CLAUDE CODE into the orchestrator seat, a rack of open-source workers fanning out to the sides; a task visibly splits across the rack, attempts stream back, the orchestrator routes the winner to Codex for the deep build

Narrative roleanchors the scaffold-over-model claim

What it teachesthe right model in the right seat, and the scaffold outlives any single engine

Intended impactthe reader sees model churn as a seat swap, not an existential rewrite

Animation will go here. This is the brief; the motion designer builds from it.

3. The anatomy of a harness (the curriculum spine)

This enumeration is the brand's load-bearing content: Andy's own decomposition, assembled from building these systems daily. Each organ is a real subsystem with its own engineering practice.

3aAnimation · placeholder

ANIMATION 3a: the organs enumerated

What it showsthe harness organism from the hero returns, and this time each organ is named and lit one at a time in the order the section teaches them (prompts, skills, personas, model selection, hooks, reference, templates, SOPs, data models, integrations, memory, evaluation, observability, CI, workflows, loops, errors, navigation, operations), each glowing then settling into the whole

Narrative roleanchors the top of the anatomy section, the curriculum spine

What it teachesthe harness is a fixed set of nameable subsystems, each its own engineering practice

Intended impactthe reader gets the full map before the detailed walk, so no organ feels arbitrary

Animation will go here. This is the brief; the motion designer builds from it.

Prompts are the tissue everything grows from:,, readmes, operating contracts, the dozens of markdown files that define who an agent is and how it should think. They are versioned artifacts with owners and review discipline, never strings buried in code. Skills package procedural knowledge into loadable units, keeping the base prompt lean while making deep procedure available on demand. Personas shape register and judgment per role, the difference between five agents that all sound like the base model and a crew whose members can be trusted with different work. Model selection and testing treats the roster as a portfolio decision, verified by testing rather than vibes and revisited as the frontier moves; Hermes exists precisely because no single model wins every seat.

Hooks are the mechanical enforcement layer: code that fires on tool use and writes, blocking the em dash, rejecting the invalid model ID, catching the deferral. Prose rules bind an agent that chooses to follow them; hooks bind everyone, and anything load-bearing eventually graduates from instruction to hook. Reference material is curated context, and getting the right reference into the right context at the right moment is a retrieval problem, one of several places the harness plugs into WikiDesignCo. Templates (Jinja, for everything that repeats) make output shapes deterministic where determinism is cheap, with template lifecycle managed as its own process because a stale template silently propagates a stale standard. Guides and SOPs for agents are operating procedures written for machine readers: how to hand off, how to report, what evidence a claim requires, with the nine-rung hierarchy as the master SOP.

Data models ground every structure in Pydantic as the intermediate representation, so every message and artifact an agent produces has a typed shape that survives translation across storage and transport; ScatterModel is the sister asset that productizes exactly this discipline, one typed model projecting from a single IR to database, backend, frontend, and templates (see the scatter-model deck). Integrations answer how the harness connects to the world, and the honest answer is plural: MCP as today's workhorse, A2A for agent-to-agent traffic, ACP, ADK-style toolkits, plain APIs, CLIs, SDKs, sometimes a GUI driven directly. Knowing which protocol fits which seam is a core harness-engineering judgment. Memory is layered by time and truth, with WikiDesignCo as the deep layer: the corpus, the knowledge bases, and the metagraph agents query before acting and write back to after. A harness without a memory architecture repeats its mistakes with great confidence.

3bAnimation · placeholder

ANIMATION 3b: memory layered by time and truth

What it showsan agent about to act pauses and reaches down through stacked memory strata (a fast working layer, a reference layer, and the deep WikiDesignCo corpus with its metagraph) to pull the one relevant prior fact up into its context, acts, then writes the outcome back down into the deep layer as a new typed record

Narrative roleanchors the memory organ and its WikiDesignCo plug inside the anatomy

What it teachesmemory is architecture, layered by recency and by truth, not a single dumped window

Intended impactthe reader sees why a harness without a memory layer repeats its mistakes confidently

Animation will go here. This is the brief; the motion designer builds from it.

Evaluation rubrics define what good means before work begins, and in a loop-driven harness the evaluator is most of the system's real intelligence (§4 returns to this). Observability makes the harness auditable, LogFire spans on every operation of consequence, under the house law that what is not in the traces did not happen. Continuous integration keeps the harness itself improving: prompts, skills, and hooks flow through the same review discipline as code, because they are code, and the feature factory is this organ at domain scale. Workflows structure multi-step work as explicit graphs, LangGraph orchestrations with DAG-thinking a data engineer knows from Airflow; determinism lives in the workflow, judgment lives inside nodes.

3cAnimation · placeholder

ANIMATION 3c: determinism in the graph, judgment in the node

What it showsa directed graph of fixed edges lights up as the deterministic skeleton, its arrows firing in a set order; then one node zooms open to reveal a reasoning agent making a genuine call inside, while the graph around it stays rigid and predictable

Narrative roleanchors the workflows organ, the split between structure and reasoning

What it teachesthe workflow holds the deterministic shape, the node holds the judgment, and mixing them is the failure

Intended impactthe reader learns where to put certainty and where to allow reasoning

Animation will go here. This is the brief; the motion designer builds from it.

Errors and retries are the durability organ: retry policies, idempotency, loud typed failure events, and never a fallback that masquerades as success. A harness earns trust exactly as fast as its failure handling deserves it. Navigation is how agents move through their world (a shell with grep, filesystem access, an API surface, a browser), and mismatched navigation is a silent capability killer. Operations closes the anatomy: the operational ledger that knows the task, the project, the owner, and the status, structured by the nine rungs from Mission to Event. This is CRM-shaped machinery built for agents as first-class users, the territory PRD Master develops into a product (see the prd-master deck), because a harness without an operational ledger cannot be managed, only watched.

3dAnimation · placeholder

ANIMATION 3d: the operational ledger for agents

What it showsa live ledger surface where each row is a unit of agent work, its nine rungs from Mission to Event filling column by column as the work proceeds, owner and status updating in place, so the whole fleet's activity reads at a glance the way a CRM reads a sales pipeline

Narrative rolecloses the anatomy walk on the operations organ

What it teachesagents need a first-class operational record structured by the nine rungs, or the fleet can only be watched, not managed

Intended impactthe reader sees operations as the organ that turns a swarm into something governable

Animation will go here. This is the brief; the motion designer builds from it.

3Animation · placeholder

instruction graduates to hook

What it showsa prose rule written on a card repeatedly failing to stop a rushing stream of agent actions; the card then forges into a mechanical gate bolted across the stream, and the next violating action visibly bounces off it

Narrative roleanchors the enforcement claim inside the anatomy

What it teachesanything load-bearing graduates from instruction to hook, because hooks bind everyone

Intended impactthe reader feels the difference between advice and architecture

Animation will go here. This is the brief; the motion designer builds from it.

4. Loops (the organ the era is named after)

Loops get their own section because Andy weights them heaviest and the industry has just caught up to why. Loop engineering is the emerging discipline of designing the cycle that drives agents (act, observe, evaluate, decide, repeat) rather than prompting each step by hand, and the 2026 practitioner literature now names it as the successor layer to prompt engineering: the highest-leverage design surface has moved from the words you type to the cycle that keeps an agent productive, verified, and on-goal, including while you sleep.

Andy's version of the loop is specific and it is the one this brand teaches. A fresh agent makes an attempt against pre-established criteria and publishes its work. A reviewer agent evaluates the attempt against those criteria. A third agent reads the review, the original, and the requirements, does its own research, and makes a better attempt. Each participant runs with a lean, purpose-sized context instead of one bloated window, which is why loops produce more quality per token than monolithic sessions: the loop does its action, completes, and keeps going, incrementally and iteratively improving. The external literature lands on the same structural conclusion the practice found first: the verifier is the bottleneck and the crown jewel, because the generator retries cheaply forever, so the quality of the evaluation criteria decides whether all that motion compounds into value. Loops are to this era what prompts were to 2023, and the evaluation-rubric organ is where a SuperHarness buildout earns its fee.

4aAnimation · placeholder

ANIMATION 4a: the verifier is the bottleneck

What it showsa generator glyph fires attempt after attempt almost for free, a cheap fountain of tries; beside it a single verifier gate is the narrow point everything must pass, and its criteria bar is what actually rises; sharpen the gate and the whole stream's quality climbs, blur it and the fountain of tries compounds into nothing

Narrative roleanchors the loops section's second claim, that the evaluator holds the real intelligence

What it teachesthe generator retries cheaply forever, so the quality of the evaluation criteria decides whether motion becomes value

Intended impactthe reader relocates their effort from generating to specifying what good means

Animation will go here. This is the brief; the motion designer builds from it.

4Animation · placeholder

the loop beats the marathon

What it showsa circular track with four stations (ATTEMPT, PUBLISH, REVIEW, IMPROVE); a fresh agent glyph spawns with a small clean context meter, completes its arc, despawns; the next glyph spawns standing on the prior work; a fixed criteria bar at center climbs each revolution while every context meter stays small

Narrative roleanchors the loops-replace-prompts claim

What it teachesfresh agents on a well-built loop beat one exhausted agent, at lower token cost

Intended impactthe reader wants their own loop by the third revolution

Animation will go here. This is the brief; the motion designer builds from it.

5. What carries over from Symphony AGI (referenced, not repeated)

The Symphony AGI deck (2026-06-21) remains the standing research for everything the rebrand does not change, per the one-source rule. Carried in full and cited from there: the conducting design philosophy (§2, first claim: topology derived from the domain's intent, never imposed volume); the three-angle valuation with its comps (Cognition, Imbue, Replit, Cursor, Zhipu, the MosaicML strategic-multiple logic) and the credit-quality argument for self-hosted, model-agnostic open-core (§3a); the artifact-marketplace third door (§2, third claim: every reusable unit of agent engineering as a versioned, cataloged asset, the lane the incumbents will not occupy); the feature factory as the productized unit (§2, fourth claim); and the five personas with their PST world model. Where that deck says Symphony AGI, read SuperHarness; the metagraph records the supersession as a bi-temporal edge rather than an erasure, which is exactly how this ecosystem treats every renamed belief.

5Animation · placeholder

supersession, not erasure

What it showsa node labeled SYMPHONY AGI does not vanish; a new node SUPERHARNESS lights beside it and a labeled SUPERSEDES edge draws between them, both timestamped, so the old belief stays queryable as history while the new one carries current truth

Narrative roleanchors the carry-over section's premise, that the rename is a recentering not a reset

What it teachesthe ecosystem records renamed beliefs as bi-temporal edges, keeping the prior research live and cited

Intended impactthe reader trusts that nothing researched under the old name was thrown away

Animation will go here. This is the brief; the motion designer builds from it.

The deltas the rebrand adds on top of that base: the brand's center of gravity is the practice (teach, release, build) rather than the platform; the anatomy of §3 is the public curriculum and the buildout checklist; loops are promoted from an implementation detail to a headline discipline; and the WikiDesignCo dependency is now a build in flight rather than a plan (wikidesignco deck §7b), which converts the memory organ from aspiration to integration work.

6. Business model and the WikiDesignCo relationship

Revenue stacks in three tiers, and the tiers are the same three motions the anatomy decomposes into. The buildout tier sells bespoke harness engineering at multi-five-figure engagements: an organization with real workloads gets a Hermes-based harness designed around the full anatomy, with the evaluation rubrics, the observability, and the operational ledger that make it maintainable after the engagement ends, priced against the fear it resolves (the science project that never ships). The teaching tier packages the discipline itself, the anatomy as modules and loop engineering as the flagship, with Data Monastery as the neighboring teaching brand for the data layer beneath (see the data-monastery deck). The open-source tier is the top of the funnel rather than a revenue line: internally stress-tested Hermes plugins released deliberately and intermittently, each one a proof artifact aimed at the engineers who influence buildout purchases.

6aAnimation · placeholder

ANIMATION 6a: three motions, one anatomy

What it showsthe harness anatomy sits at the center and three revenue arrows draw off the same organs: an open-source funnel releasing single lit plugins at the top, a teaching tier lifting organs out as curriculum modules, and a buildout tier assembling the whole body for one client, all decomposing along the identical organ lines

Narrative roleanchors the revenue-model claim that teach, release, and build share one spine

What it teachesthe three revenue motions are the same anatomy read three ways, not three separate businesses

Intended impactthe reader sees the open-source release as the top of a funnel, not a giveaway

Animation will go here. This is the brief; the motion designer builds from it.

The WikiDesignCo relationship runs in both directions and is the deepest dependency in the ecosystem. Downward, every organ that touches knowledge runs on the platform: memory queries the corpus and the metagraph, reference material is retrieved from knowledge bases through their MCP connections, templates and rubrics live as versioned assets, and the operational ledger's records land as typed, provenance-bearing data. Upward, the platform is operated by harnesses, so every SuperHarness advance upgrades the crew that runs the corpus. The staging truth both share, per the 2026-07-03 directives: the platform is the environment, humans and CLI agents are its users through the same surfaces, Gemini and Vertex carry the in-platform processing for now (LangGraph workflows or direct calls, Gemini being the model that reads video), and resident Hermes-class agents arrive later, low-level processing first, while real-time acting stays with humans and CLI agents. GPS ContentFactory is the live laboratory where that staging earns its keep on a paying customer today.

6Animation · placeholder

the two-way dependency

What it showsa harness organism and a corpus field connected by two thick flows: knowledge streaming up from the corpus into the harness's memory and reference lobes, and refined work streaming down from the harness's hands into the corpus as new typed assets

Narrative roleanchors the SuperHarness-WikiDesignCo relationship

What it teachesthe harness runs on the platform and the platform is run by harnesses; each advance upgrades the other

Intended impactthe reader understands why these two assets are built as one motion

Animation will go here. This is the brief; the motion designer builds from it.

7. Priority read (feeds the value rubric)

SuperHarness inherits Symphony AGI's position on the dependency graph: the apparatus every brand is conducted by, foundational alongside WikiDesignCo, with the two forming the substrate pair (the harness runs the work, the platform remembers it). The Now lanes: continue the Hermes/Harness V2 build under the new name, and let the anatomy structure both the internal practice and the first public teaching material. The Next lanes, gated on WikiDesignCo's walking skeleton landing: wire the memory organ to real workspace knowledge bases via MCP, and cut the first open-source plugin release from a stress-tested internal piece. The Watch lane: the loop-engineering conversation is moving fast in public, so the teaching material's framing gets re-grounded against the literature at each authoring pass rather than assumed stable. The Leave lane is unchanged from the Symphony AGI read: never rebuild what the scaffold rents (model runtimes, commodity orchestration primitives).

7Animation · placeholder

the substrate pair

What it showstwo foundation stones set side by side under the whole ecosystem, one labeled SUPERHARNESS (the crew that runs the work) and one WIKIDESIGNCO (the corpus that remembers it); the brand nodes above rest their weight on both, and the Now/Next/Watch/Leave lanes sort into place around them

Narrative roleanchors the priority read, SuperHarness as foundational substrate paired with the platform

What it teachesthe harness and the platform are the two-stone floor every other brand stands on

Intended impactthe reader ranks this brand as substrate, never above the thing it depends on

Animation will go here. This is the brief; the motion designer builds from it.

8Animation · placeholder

every act lands as a typed record

What it showsa loop revolution completes and drops a typed token into a ledger (LoopCriteria met), a plugin release drops another (PluginRelease), a buildout closes and drops a third (BuildoutEngagement), each token carrying its LogFire span as a thread of light trailing back to the moment it happened

Narrative roleanchors the brand's own bottom rungs, Data and Event, as lived records

What it teachesthe practice produces typed, provenance-bearing records for every act, not just outputs

Intended impactthe reader sees the discipline as auditable by construction, down to the single event

Animation will go here. This is the brief; the motion designer builds from it.