Skip to main content
← BUILD 043PROGRAM ARCHIVE
DURABLE BUILD ARCHIVE / STRUCTURED PUBLIC · CERTIFICATION OPEN

BUILD 043
Design an AI Team

A multi-agent team becomes inspectable when roles, direct human supervision, dependencies, escalation, trace, stop controls, capacity, bottlenecks and declared cost remain one topology.

QUESTIONHow can specialized AI agents and people divide work without losing control at the handoffs?
STRUCTURED PUBLIC BUILD ARCHIVE

Research, creation, decisions, audits and plans are publicly structured without claiming that every release gate is complete.

DURABLE-RECORD RULE

This page exists so the durable record does not depend on conversation history. Research, decisions, generated artifacts, audits, limitations, media metadata, plans and canonical source paths are retained here as part of the build itself. A listed repository path proves that an implementation record was retained; it does not independently support a real-world factual claim.

SOURCE-LINK AVAILABILITY

0 of 5 listed retained paths have a public reader link on this archive page. Unlinked paths remain named for traceability but are not represented as publicly inspectable evidence.

01 / RESEARCH + EVIDENCE

What informed the build

AI Team Engine v1data/build-043-engine-v1.json

Versioned member, role, supervision, dependency, control, capacity, bottleneck and cost rules over a synthetic fixture.

RETAINED PATH LISTED · PUBLIC SOURCE LINK NOT AVAILABLE
02 / CREATED

What exists because we built it

Governed Multi-Agent Team Primitive

Reusable orchestration infrastructure for Build 092.

03 / ARCHITECTURE + DECISIONS

Why it works this way

Canon and lineage are frozen

Uses 017, 019, 039, 040, 042; creates cap:043; direct consumer is 092.

AI supervision is explicit

Every declared AI member requires a named human supervisor.

Handoffs are graph constraints

Missing, self-referential and cyclic dependencies block readiness.

Topology readiness is not execution proof

TEAM READY does not establish authority, human attention, performance, cost accuracy, safe coordination or real execution.

04 / AUDIT + RELEASE

How the work was checked

Machine-readable archivedata/build-043-archive-v1.json

State-only replay and exact nonclaims.

RETAINED PATH LISTED · PUBLIC SOURCE LINK NOT AVAILABLE
Privacy/supportdata/build-043-privacy-support-v1.json

Synthetic browser-local team with no real assignments.

RETAINED PATH LISTED · PUBLIC SOURCE LINK NOT AVAILABLE
Freshness/performancedata/build-043-freshness-performance-v1.json

Versioned bounded topology inspection.

RETAINED PATH LISTED · PUBLIC SOURCE LINK NOT AVAILABLE
Browser fixturestests/build043.spec.ts

Supervision gate, repair, export, 320px and accessible topology.

RETAINED PATH LISTED · PUBLIC SOURCE LINK NOT AVAILABLE
05 / PLANS + OPEN THREADS

What this build intentionally leaves forward

Independent release gates

Authenticated browser, physical-device/manual accessibility, hosted CI, multi-agent governance expert review and media certification remain separate.

Future consumer

092 consumes cap:043.

06 / MEDIA

Take the social artifact with you

B-LINKEDIN / CANONICAL FILM

720×900 · 4:5 MP4 · 24 fps · silent-first

CURRENT VERIFIED MEDIA / 30-second film · 116.6 KB

FINAL PROPOSITION / Design the team, not just agents.

SHA-256 c88435a376405e7fa637f27596ba4e0cf78748e860942e6ea2d0452c9dd82a01Reproducible from data/linkedin-film-specs-v1.json with scripts/render-linkedin-films.py. The website—not a chat attachment—is the canonical media source.
07 / CANONICAL SOURCE INVENTORY

The repository files that preserve the implementation record

apps/web/app/100-builds/043/a/TeamLab.tsxapps/web/app/100-builds/043/b/TeamTopology.tsxpackages/release/src/ai-team-engine.tsdata/build-043-engine-v1.jsondocs/builds/043/SPEC.mdtests/build043.spec.ts

These paths preserve the implementation record. Only items with an explicit public reader link are publicly inspectable here. A file path, working interface or internal engine is not independent support for a real-world claim; synthetic propositions and design reasoning remain labeled within the retained record.