← All projects

ODfact

0 comments

What it does

AI Software Company turns a Markdown software specification into a working TypeScript CLI or HTTP API. Instead of asking a single coding agent to build everything, it creates a small AI development organization: a Product Manager converts the specification into testable requirements, a Tech Lead creates an engineering plan, Developers implement the software, QA independently writes adversarial tests, and a Reviewer evaluates the work. Deterministic CI then builds and tests the generated project. If verification fails, the system automatically creates a repair ticket, assigns it to the responsible agent, and repeats review and verification until the project passes or a bounded retry limit is reached.

How the agents run concurrently

After the Product Manager and Tech Lead finish the initial requirements and architecture, three independent Mozaik agents start at the same time: Developer A — Implementation Engineer: implements the main functionality. Developer B — Reliability Engineer: handles validation, edge cases, and error behavior. QA — Adversarial Test Engineer: independently creates tests from the Product Contract without waiting for the implementation. They run as separate Mozaik agent loops and share a typed EngineeringState, which acts as the team's common engineering board. It contains the Product Contract, engineering plan, tickets, ticket status, artifacts, reviews, test results, failures, retries, and execution metrics. Coordination is event-driven rather than controlled by one sequential orchestrator. Agents react to events such as: ticket.claimed → ticket.completed → review.requested → integration.requested → verification File ownership and ticket dependencies prevent concurrent developers from overwriting each other's work. The Reviewer remains read-only. After the concurrent workers finish, it reviews their artifacts, and deterministic CI performs the final build and tests. If CI fails, the Reviewer classifies the failure and creates a bug ticket for the responsible developer, automatically starting another repair cycle.

Comments

No comments yet.

Sign in to like and comment