← back to overview/spec § 05 · how — the build

Ten engineers, twenty-six sprints. Coconut Labs' first multi-engineer project.

The previous Coconut Labs projects were solo: kvwarden, mlxd, Minerva Trader, Pancakes. Coconut OS is the first time the lab runs a multi-engineer team. The shape below is by role, not by name — names attach at Sprint 0.

§ 05.1 — roles

The shape of the org.

E1
Tech lead · kernel
Linux fork strategy · merge-window discipline · gatekeeper for kernel/agent + LSM hook
E2
Kernel · agent + cred
kernel/agent/ subsystem · cred-shim · syscall plumbing
E3
Kernel · audit + scheduler
kernel/audit/coconut · per-AID scheduling extensions
E4
Userspace · coconutd
PID 1 · agent supervisor · CBOR IPC on /run/coconutd
E5
Userspace · packaging
coconutpkg · coconut-installer · libcoconut
E6
Platform + CI
kernel-CI · reproducible ISO build · sigstore signing
E7
Compositor
Coconut Shell · Wayland + Smithay · agent-aware WM
E8
Userspace apps
Coconut Center · Coconut Terminal · Display Manager
E9
Security
STRIDE/LINDDUN threat modeling · LSM review · CVE response
E10
Brand + design engineer
Typography · palette · motion · iconography · marketing + docs sites

names attach at Sprint 0 · per-role bios + photos publish at kickoff

§ 05.2 — cadence

Sprints are two weeks. Everything else is consequence.

sprints to v1.0
26
two-week cadence · 52 weeks
parallel projects
3
kvwarden · mlxd · Coconut OS
velocity target
35 pts/sprint
effective allocation across team

The three parallel projects — kvwarden (already shipped to Show HN), mlxd (G3 launch June 2026), and Coconut OS — run concurrently. Running three in parallel from a ten-engineer base is stretched. The founder framed it as the bet of the year, not a comfortable plan.

held back

Specific sprint owners, gating decisions, budget envelope, runway timeline, and hire schedule live in the PLAN + SPRINTS docs. Public preview shows the role topology; assignments and capital plan land with the spec drop.