Skip to content

Philosophy

A flock of
builders.

Four principles that hold the portfolio together. Each one explains why something in the CorvidLabs catalogue exists, and how the pieces fit.

🛠️

Every project sharpens the next

Not a startup chasing an exit. A flock of builders where each tool feeds the others. spec-sync keeps fledge honest. fledge feeds Merlin. Merlin helps build the next tool. The bet: every new primitive makes everything above it sharper.

🔌

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.

⛓️

A chain, where it earns its place

When something genuinely needs settlement, we reach for Algorand: fast finality, fractions-of-a-cent fees, and mature SDKs in every language we use. AlgoChat settles on it for on-chain transport. One capability among many, not the center of gravity.

📖

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 the public. Neither default. Both deliberate.

How it composes

The principle above, drawn as a picture. Five layers, read top to bottom; each one is built on the layer beneath it, and every new primitive at the bottom sharpens every layer above.

  1. Substrate

    Layer 1

    The chain underneath the parts that need one.

    Algorand

    Released

    Roughly three-second finality and fractions-of-a-cent fees. AlgoChat settles on it for on-chain transport when you want it.

The dependency chain

The work isn't parallel. There's a critical path, and most of the foundation is already in place. Naming it shows what's done and what's left.

  1. 1
    spec-sync and fledge: the foundation, with contracts locked and dependable
    Step 1 · The foundation
    done
  2. 2
    The flock drops Claude Code as the daily driver and dogfoods on Merlin
    Step 2 · The proof
    done
  3. 3
    The open-source primitives (spec-sync, fledge, augur, attest) readied for the public
    Step 3 · The opening
    now
  4. 4
    Quill and Merlin pushed toward their public releases
    Step 4 · The products
    now
  5. 5
    corvidlabs.xyz goes live: one public face for the whole catalogue
    Step 5 · The front door
    now
  6. 6
    The catalogue does the talking; the work compounds as each piece ships
    Step 6 · The story
    next

If this resonates

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

The work speaks first. The catalogue is the pitch. If a tool fits how you build, take it.