Skip to content

🪶 Philosophy

A workshop that
compounds.

Six principles that hold the portfolio together. Each one explains why something in the CorvidLabs catalogue exists. And why a few things don't.

🛠️

Workshop that compounds

Not a startup with an exit. Every project sharpens the next. fledge feeds Merlin. spec-sync keeps fledge honest. AlgoChat ships inside corvid-chat. The bet: this compounds faster than competitors can catch up.

🔌

Plugin architecture is the moat

Most tools have a fixed surface. fledge has a plugin protocol. spec-sync validates contracts across every CorvidLabs language with one shared format. Merlin's tool surface is composable: change a plugin, change what the agent can do. Plugin-architecture-as-moat is the central technical bet.

🛡️

BYO content

corvid-recipes got archived. Scraped external sites, legal grey, broke every time someone tweaked anti-bot. Lesson: don't build anything that wraps someone else's data. fledge wraps your project. Merlin proxies to whatever LLM you bring. AlgoChat owns its protocol. corvid-chat owns its server.

⛓️

Algorand-native

Fast finality, low fees, carbon-negative, mature SDKs in every language we touch. USDC tips at $0.001 and 3-second confirmation only work on a chain shaped like this. NFT memberships, USDC payments, on-chain identity, server registries. All first-class, not bolted-on.

📖

Open source where it makes sense

Tools that benefit from outside adoption go public. fledge, the swift-* family, every AlgoChat impl. Methodology-shaped tools stay private until they're ready for outside hands. Neither default. Both deliberate.

🐦‍⬛

Small team, force-multiplied

Four humans (Leif, Tofu, Kyn, Gaspar) plus an agent runner per task. 100 public repos, 57 more private during dogfooding. Small team, big surface, kept honest by automation.

The content-discipline filter

Don't build anything that wraps another company's content or depends on scraping their data.

Applied to every new project idea. Would have killed corvid-recipes before any code shipped. Rejects: Twitter mirror, Reddit scraper, recipe wrapper, any product where someone else's terms-of-service is your single point of failure.

The 2026 dependency chain

The work isn't parallel. There's a critical path. Naming it makes the next move obvious.

  1. 1
    Sub-agent plugin lands in Merlin
    Step 1. Load-bearing
  2. 2
    Merlin handles one real work-task end-to-end
    Step 2. The gate
  3. 3
    Drop Claude Code as the daily driver
    Step 3. The freedom
  4. 4
    Dogfooding budget frees up
    Step 4. The time
  5. 5
    corvid-chat dogfood + polish
    Step 5. The proof
  6. 6
    corvid-chat launches publicly
    Step 6. The story
  7. 7
    Marketing co-conspirator scales the moment
    Step 7. The amplifier

If this resonates

Fork a repo. File an issue. Open a PR.

The work speaks first. Marketing comes when corvid-chat ships. Until then, the catalogue is the pitch.

Browse projects GitHub org Join Discord →