Agency OS improvement loop
Platform Build
The separate board and operating loop where Agency OS improvement work is logged, built, reviewed, and merged.
What It Is
Platform Build is the Agency OS improvement loop. Jessie handles consultant/client work; Platform Build handles the development work required to improve Agency OS itself.
Board Sections
| Section | Meaning |
|---|---|
| Intake | New improvement ideas, defects, or platform requests that are not ready for build yet. |
| Needs Clarification | Tasks needing product, business, technical, access, or scope decisions before an agent can build. |
| Ready For Builder | Scoped work that a builder agent can pick up. |
| In Progress | An agent or human is actively implementing the task. |
| Review Ready | Work is ready for human review, acceptance, and merge decision. |
| Blocked | Progress is stopped on access, product decision, technical dependency, or failing prerequisite. |
| Merged/Done | Accepted work has been merged or completed. |
| Error/Regression | System problems, failed checks, runtime regressions, or defects found by monitoring or runtime checks. |
Human And Agent Boundary
Agent owns
- Inspect code and docs.
- Implement scoped changes.
- Run focused tests/builds.
- Update docs when architecture changes.
- Report status and evidence for review.
Human owns
- Product priority.
- Ambiguous business decisions.
- Credential and access provisioning.
- Production-risk approval.
- Final acceptance and merge approval.
Coming Foundation
Coming This is the one section where the site intentionally shows direction beyond current live behavior.
- Agents should be able to pull ready Platform Build tasks and work in independent branches or worktrees.
- Build agents should preserve a clean review trail with checks, docs updates, and artifact summaries.
- Merging stays approval-gated.
- Cloudflare Artifacts events may later help trigger review/build automation, but that is not documented as live behavior today.