The Framework — Role A

A

The Architect

The Project Manager or Lead Developer becomes a System Architect. They don't manage people — they manage the Blueprint. Their job is to decompose a project into self-contained units (Shards) and define exactly what each one does, before any code is written.

Deliverable — A Machine-Readable Manifest for every Shard: a technical contract that every agent can follow precisely, with no verbal clarification needed.

Sharding the project

The Architect decomposes a project into independent functional units called Shards. Each Shard is self-contained — it can be built, tested, and validated in complete isolation from every other Shard. This is what enables true parallel execution.

A good Shard has one clear responsibility, one clear input, and one clear output. If you can't describe it in a single sentence, it needs to be split further.

The Manifest

Each Shard gets a Machine-Readable Manifest — a technical contract defining exactly what the module does, its inputs, outputs, and logic constraints.

AI follows contracts perfectly. Humans often misunderstand verbal instructions. The Manifest replaces every meeting, Slack message, and verbal briefing. Every ambiguity that would have become a back-and-forth is resolved in the spec before any agent picks up the task.

No coordination overhead

Once the Manifests are written, the Architect's job is done for that sprint. There are no daily standups to run, no Slack threads to resolve, no sprint retrospectives to facilitate.

Every question that would have become a meeting is instead a spec update. The Manifest is the single source of truth — and it's readable by machines and humans alike.

Mini-Shard rule

Not every task warrants a full Manifest. Tasks under ~20 minutes of agent runtime use the Mini-Shard rule: a plain-text decision log and a single agent is enough. No Manifest machinery, no overhead.

This keeps the framework lightweight for small tasks while preserving full contract rigour for anything that affects multiple parts of the codebase.

Key principle

The Architect never writes code. Every minute spent coding is a minute not spent on the Blueprint. A well-defined Manifest is worth more than any single Shard implementation.