FILE #001[ACTIVE BUILD]
Brand Cortex
Brand identity as executable code. The 2019 thesis meets its infrastructure.
FILE CONTENTS
2019. Modular Branding — the idea that brand identity could work like code. Tokenized. Version-controlled. Executable. Published in the Bitkom Digital Design Yearbook. Nice theory. No tools to build it.
Brand Cortex translates the Kapferer identity prism into a token architecture that AI agents can read, interpret, and generate from. Feed it a brand. It returns executable identity. A living system that generates consistent brand expressions and feeds real-world performance data back into the core.
The brand finally gets a feedback loop.
FILE #002[FIELD REPORT]
Fox Geometry
11 books. 48 hours. One agent loose in a mythology.
FILE CONTENTS
April 2025. 48 hours. One agent, released into an empty narrative universe.
What came back: 11 books. Japanese kitsune mythology fused with speculative documentation. Non-linear timelines. A protagonist named Thalia Reinhardt. Mathematical equations for consciousness evolution that nobody requested.
Whether the output is good remains open. The real question was different: what happens when agents run long enough to produce something larger than their prompts? When hallucination stops being a bug and starts generating its own internal logic?
The books exist. Messy. They need revision. But the process changed how we think about agent creativity. A genuine capacity that emerges from sustained autonomy.
Published under the pen name Beat Erik.
FILE #003[DOCUMENTING]
The Trust Protocol
Managing something that works shifts but has no pulse.
FILE #004[FIELDWORK]
Ghost Clients
We built your customers before you did. They have opinions.
FILE #005[INCUBATING]
Signal Gallery
A site that generates its own transmissions. Autonomously. Continuously.
FILE #006[ACTIVE BUILD]
Brainhuggers Specify
Spec-driven development for everything. Not just code.
FILE CONTENTS
Every AI coding tool on the market solves the same problem: write code faster. None of them ask the harder question: what should we build, and why?
Specification-Driven Development has been emerging as a discipline — GitHub's Spec-Kit, AWS Kiro, a dozen open-source frameworks. All focused on code. All assuming the human already knows what they want.
Brainhuggers Specify extends SDD beyond code into every business function. Brand architecture. Org design. Entire product conceptions. The spec becomes the universal interface between human intent and agent execution.
Write a spec. The agents build it. Not just software — entire business systems. Spec in, artifact out. It sounds absurd until you watch it work.
The protocol that governs how the Bureau builds everything else.
FILE #007[ACTIVE BUILD]
Brainhuggers CLI
A terminal that adopts you back. Six providers. One companion. Zero wrappers.
FILE CONTENTS
Every AI coding assistant is the same product. Thin skin over one API. A chat window that autocompletes. We wanted something different: a terminal that feels alive.
Brainhuggers CLI is a Rust-native terminal assistant forked from claw-code, rebuilt from the studs. Six LLM providers — OpenRouter, Anthropic, xAI, OpenAI, Ollama, Claude CLI — with automatic detection. No config ceremony. It finds what you have and starts talking.
The real departure is the buddy system. Gacha-style companion creatures — 18 species, five rarity tiers, deterministic generation seeded from your machine identity. They level up as you work. They react to your errors. They have moods. A capybara that vibes while you debug. A dragon that gets dramatic when the context window fills up. A 1% shiny rate for the ones who grind.
Underneath the charm: prompt caching with hit tracking, MCP orchestration with graceful degradation, context window preflight, crash recovery with exponential backoff, extended thinking with token budgets. The kind of infrastructure you only build when you actually use your own tool every day.
Not a wrapper. Not a skin. An instrument.
FILE #008[ACTIVE BUILD]
Cortex Audio Engine
Eurorack in a browser. Mutable Instruments DSP compiled to WASM and left running.
FILE CONTENTS
Mutable Instruments shut down in 2022. Emilie Gillet open-sourced everything — Clouds, Rings, Plaits — and walked away. The modules became legends. The code became an archive.
We brought them back. Not as hardware. As WebAssembly. The Cortex Audio Engine compiles real MI DSP cores to WASM via Emscripten, runs them inside AudioWorklets, and connects them to DaisySP as a base synthesis layer. Eurorack-grade granular processing, physical modeling, and additive synthesis — in a browser tab.
The engine powers brainhuggers.com itself. Generative ambient audio that evolves with scroll position and time of day. Seven patches from the Noway Register — the sonic identity we built before we had a visual one. The site hums.
Not a simulation. Not a toy. The actual DSP code that ran on 32-bit ARM chips, now running on your laptop. Latency under 10ms. No plugins. No installs. Just sound.
FILE #009[FIELD REPORT]
Wrapper Funeral
We autopsy AI wrappers so you don't have to. Recurring series.
FILE CONTENTS
The AI industry has a wrapper problem. Take an API. Add a UI. Charge $49/month. Call it innovation. We think these products deserve a proper funeral.
The Wrapper Funeral is a recurring teardown format. We take a funded AI product, strip it to its API calls, measure what the wrapper actually adds, and publish the autopsy. No malice. Just measurement.
The format scales. One teardown per quarter. Each one asks the same question: what are you paying for? Sometimes the answer is real. Sometimes the body is hollow.
A public service announcement disguised as content.
FILE #010[DOCUMENTING]
Brand Hallucination Index
Monthly scorecard. How badly does AI hallucinate about your brand?
FILE CONTENTS
Ask Claude about Nike. Ask GPT about IKEA. Ask Gemini about Deutsche Telekom. Write down what they say. Compare it to reality. Score the gap.
The Brand Hallucination Index is a monthly publication that measures how accurately AI models represent real brands. Three brands scored so far. The methodology is public. The results are uncomfortable. Models confidently state product lines that don't exist, invent executive names, and hallucinate entire brand histories.
This matters because AI is becoming the first point of contact between consumers and brands. If the model is wrong about you, the model IS your brand — to everyone who asks it instead of searching.
Three scorecards exist. The methodology is documented. Publishing infrastructure is the remaining gap. The data is already more interesting than we expected.
FILE #011[INCUBATING]
Phantom Panel
Synthetic audience panels. We built your customers before you did.
FILE #012[INCUBATING]
Guardrail Theater
Live-stage red-teaming of AI products. The audience watches it break.
FILE #013[FIELDWORK]
The Succession
30 days. One junior. One agent swarm. Same deliverables. We counted.
FILE #014[DOCUMENTING]
Solo Maxima
One human. Full agent stack. The build is the content.
FILE #015[INCUBATING]
The Seam
Visible co-authorship as certification. The opposite of hiding the AI.
FILE #016[ACTIVE BUILD]
The Swarm
Three servers. Four agents. One Tailscale mesh. The org chart has no humans on it.
FILE CONTENTS
It started with one question: what if the Bureau had staff? Not employees. Agents. Actual software entities with roles, memory, and opinions about how to do their jobs.
Lobe is Chief of Staff — runs on OpenClaw on a Hetzner ARM box in Nuremberg, handles overnight research pipelines, maintains a persistent memory palace, posts to Discord and Telegram. Hermes is the researcher, deployed on Hostinger, tasked with exploration and signal detection. Paperclip runs multi-agent delegation experiments with a CEO agent that spawns sub-agents and tracks their budgets.
They share context through MemPalace — a SQLite knowledge graph organized into topic wings. They coordinate through Linear. They communicate through Discord. They are connected via Tailscale mesh. None of them sleep.
The experiment is not whether agents can do work. They can. The experiment is whether agents can do work *together* — across servers, across sessions, across goals — without a human in the loop for every decision. Early results: yes, but the coordination overhead is real. The swarm works shifts.
The infrastructure IS the product. Every orchestration pattern, every failure mode, every emergent behavior — it all feeds back into how we build for clients.
FILE #017[FIELDWORK]
MemPalace
Agents forget everything between sessions. We gave them a palace to remember in.
FILE #018[DOCUMENTING]
Graphify
Point it at a folder. It returns a map of everything the code knows about itself.
FILE #019[FIELDWORK]
Ghost Agency
A book manuscript. The chapters know things we haven't discussed yet.