Skip to main content

Astound Digital ยท Dev Factory

The Dev Factory, by Astound Digital.

Astound Digital's governed dev factory on systemprompt.io. Agents take well-specified work from issue to pull request, people make the decisions, and every model call, tool call and dollar is recorded.

Mission

Turn Astound's engineering judgement into a governed software factory: agents take well-specified work from issue to reviewed pull request, people decide what ships, and every hour and dollar is measured.

Three North Stars

Agentic flows

An issue becomes a reviewed pull request without a person typing the code, with a person deciding wherever judgement matters.

Rich context

Every agent step starts with what a senior engineer on that project would already know, and nothing it should not see.

Measurement and reporting

For every piece of work: what it cost, what it replaced, whether it was accepted, and how that compares with before.

How a piece of work flows

This is the shape of core-dev, the one workflow that ships. Which work enters the factory and where people decide are open decisions for the agentic-flows owner.

  1. Issue. A developer or project manager starts a workflow run from a well-specified issue.
  2. Agents. Agent steps analyse the issue, design and build the change, each with a prompt, an output schema and a budget.
  3. Human decisions. People approve, request changes or reject at each decision point. Agents never approve their own work.
  4. Pull request. The approved change is opened as a pull request for review. Nothing reaches a main branch without a person's decision.

What is governed and measured

  • Every model call passes through one gateway to Vertex AI and is recorded with user, model, tokens, cost and latency.
  • Every tool call passes a governance chain (scope check, secret scan, blocklist, rate limit). It currently runs in warn mode: findings are recorded, nothing is refused.
  • Every workflow step, decision and agent run is recorded with its duration and cost, and kept as long-term history.

Where it stands

One workflow ships and has run every step up to opening the pull request against a stand-in for the model. It has not yet run on a real model. Connectors to other systems are off until they are configured. Each North Star has an owner who sets its direction, milestones and targets; the roadmap states what exists and what is parked.

Where to go next