The build layer · not the business layer

The coder fleet — the agents that build the agents.

The Factory console shows the 13 named agents that run the businesses (PERCY, OTTO, STERLING, MASON...). This console is the layer underneath it: which coding-agent lane — Windows Code, Mac Code, Cowork, Codex, or a partner lane — is building what, right now, across the five repos. The tiles below pull live from the register with your founder token; without it you see the last verified snapshot — never an invented number.

Legacy lane activity

observability only · not edit authority

Lane	Claimed area	Note	Claimed	Expires

This table preserves the legacy lane_claims / get_active_claims() visibility feed. Its rows do not grant or prove file ownership. Current edit discipline starts with one isolated task worktree and a local npm run coder:start manifest covering every exact intended file and duty. Known overlaps are resolved between coders; the final local hook requires one reviewed closed session whose path set exactly matches the branch diff. This is cooperative collision control, not actor authentication.

The lane roster

5 repos · same-access, no-lanes doctrine

Recent build activity

Lane	Repo · branch	Kind	What happened	When

This feed is append-only and grows as lanes log checkpoints (log_coder_activity()) — a session capsule, a tool audit, a PR merge. It is not a replacement for git history; it is the cross-lane index so no one has to read five repos' logs to see what shipped today.

What this is. The Coders console is the coding-agent DevOps layer of the AMAYA Founder OS: founder-visible telemetry for coder lanes across brg-operations, Attohdigital, Crewos, pharoah-tech, blackline-runtime and the _audit journal. It does not replace git, the local session ledger or review evidence.
Truth. Live tiles load only with your founder token (?t=); without it you see the last verified snapshot. Claim rows come from the legacy lane_claims / get_active_claims() view and are observability only, never ownership or edit authority. No current system authenticates one coder against another: task worktrees, exact local manifests, review evidence and the final diff gate are cooperative process controls. Recent activity comes from coder_fleet_activity, an append-only lane log; git and the strict session evidence remain the publication record.