the bricks

What is decided

• WCKD is the organisation. It comes first; the products serve it, not the other way round.
• Sovware is the production arm. The legal home for hosted products when they need one: releases, mirrors, security and verification. The code stays open source.
• Autobot and Invincible are separate products joined by one protocol. Neither is a feature of the other.
• Polykrom and PolyCore are central. Polykrom is the object forge; PolyCore is its geometry kernel. PolyCore is measured by what WCKD can make with it, not by parity with OCCT.
• Nightfall is archived. It is reference for PolyCore only; it is not a product or a destination.
• Licensing is per project. Open specifications for formats, AGPL for network services, Apache-2.0 or MIT for libraries and apps, GPL where a dependency requires it. No licence is chosen to lock anyone in.
• The world is open. wckd.world is the first seed, not a definition.

The map

surfaces   Niobium
              │
world      wckd.world — seed 0001
           place · thing · being · event · rule · time
              │
making     Polykrom → PolyCore → Sovware → TinyRex
              │
kernels    Invincible · Autobot
              │
node       your hardware · cloud burst

The map is a dependency sketch, not an org chart. A brick can appear in more than one place; the point is which way it points.

The core bricks

• Invincible — compute. One node, every model, one endpoint, a signed receipt for every call.
• Autobot — agency. Sessions, tools, permissions, memory; one runtime for every surface.
• PolyCore — geometry. Exact B-rep, feature history and watertight tessellation.
• Polykrom — the object forge. Parametric CAD, agent-drivable over MCP, built for parts that can be checked and made.
• Sovware — production and verification. Hosted products, releases, mirrors and security; programs, verifiers, gates and the ledger.
• Niobium — presence. The window, not the state.
• TinyRex — embodiment. The first physical proof that the loop can make a real thing.
• platform — operations. Deployment, runners, secrets and mirrors.
• wckd.world — the first place. One room, one thing, one agent, one event log. A seed, not a hosted world.

The first two bricks

wckd.world/seed-0001 is a draft with two bricks that can be pointed at:

• Place — a named volume with a coordinate system, a view and an owner. The first is one room.
• Thing — geometry, a claim and a place. The first is a bracket modeled in Polykrom, waiting on a Sovware claim.

They are enough to see whether the loop is real. The seed lives in a file you own. It is not a metaverse, a game or a social network.

The missing brick

Every core brick is a tool. The world layer is the state that holds them: places, things, beings, events, rules and time. wckd.world is the first seed of that layer, not the finished thing.

Its name, its shape and even whether it is one service or three are open. What is fixed: it runs on the node, its state is a file you own, and every surface is a view over it.

The contracts

WCKD owns the contract, not every implementation. A project earns its place by owning one seam the others can rely on.

• Compute — model request, route, receipt, identity.
• Agency — session, tool call, permission, event.
• Geometry — feature program, B-rep, history, tessellation.
• Verification — claim, verifier, gate, ledger.
• Presence — entity, place, view, presence.
• World — place, thing, being, event, rule, time.

The loop

Make → verify → place → inhabit. The first three are the core bricks; the fourth is the point.

Separate products, one protocol

Autobot and Invincible are not one product split in two. They are two products that are highly functional together: the phone can drive the node, the node can run the agent, and both share pairing, identity and receipts. Separate repositories, separate releases, separate failure domains. One protocol between them.

The object forge

Polykrom is the app; PolyCore is the kernel. They are central because whatever the world becomes, it will be made of things: parts, machines, furniture, robots, a room. This is where the things are designed, measured, checked and made.

The bar is what WCKD needs to make: exact enough for Polykrom, TinyRex and the objects of the world. OCCT is a reference, not a gate.

Sovware

Sovware is the production arm: the legal and operating home for hosted products when they need one. It runs what WCKD ships, keeps the copies and holds the security policy. It is also the verification kernel: programs, verifiers, gates and a ledger anyone can replay.

Open source is the default. Licences vary by project and integration: open specifications for formats, AGPL for network services, Apache-2.0 or MIT for libraries and apps, GPL where a dependency requires it. Sovware sells production and convenience, not a lock.

Archive

Nightfall is archived. Its kernel and study work is reference for PolyCore only; active development is in PolyCore and Polykrom.

The lab

Smaller experiments — Omnie, Eidolon, Enjin, Mosaic, Sable, Axit — are in the lab. They are not bricks and not on the map until they earn a contract.

Order, not a schedule

There are no dates here, and no plan handed down. One dependency order to discuss:

1. One identity and one event format.
2. One agent runtime contract.
3. One object contract: a PolyCore document and a Sovware claim.
4. One world seed: place, thing, being, event.
5. One view to test the seed.
6. Then the other tools plug in.

The order is a proposal to argue with, not a schedule. The dependencies are the part worth keeping. A project that cannot name its contract and its socket is a library, a fork or a note.

Open questions

• What is the world — its content, tone and purpose?
• Personal first, or visitable from the start?
• One app or two: Autobot and Niobium?
• What does the first room need to be worth returning to?
• What does open source mean for hosted worlds?

These are for discussion, not a roadmap. The bricks are here so the answers can change without rebuilding the stack.