Skip to content
← Transform overview

TRANSFORM / BUILD FACTORY

Make the change.
Keep the control.

Build Factory (beta) designs and builds automations ready to deploy: a scoped brief, reviewed code and a build your team deploys. Keep the purpose attached.

Beta · enablement and setup required
Build Factory workflowRequirement → brief → reviewed code → ready to deploy. An authored illustration of a fictional handoff project. BLD-014 / SCOPED BRIEFRequire an ownerPaths · Checks · AcceptanceA bounded change, ready for review REVIEWED REVISIONOne change. Its checks.Diff + tests + human approval HANDOFFReady to deployYour team deploys it BETA · YOUR TEAM DEPLOYS
Requirement → brief → reviewed code → ready to deploy
Transform workflow illustration · Fictional Northstar example
01Bounded briefs
02Revision-specific review
03Ready-to-deploy handoff

SEE THE WORK / MAKE A CHOICE

From the brief
to the actual change.

Follow a fictional owner check through scope, code, repair and approval. Make the decisions yourself in the working demo.

Working demo screens · Fictional examples

TRANSFORM / INSIDE THE DEMO

A boundary the team can review.

Read the source, permitted paths, acceptance checks and limits before opening a sample draft.

The brief connects the requested change to the checks that will establish acceptance.

Try the build workflowInteractive example · No sign-up
ProcessScout / Build FactoryDEMO WORKSPACE
Northstar working demo: Read the source, permitted paths, acceptance checks and limits before opening a sample draft.

TRANSFORM / INSIDE THE DEMO

The code and the checks, together.

Inspect a sample diff, a failing check and an independent review finding before deciding what to repair.

Follow the fictional build from setup through repair and approval to a ready-to-deploy handoff.

Try the review gatesInteractive example · No sign-up
ProcessScout / Build FactoryDEMO WORKSPACE
Northstar working demo: Inspect a sample diff, a failing check and an independent review finding before deciding what to repair.
01

MAKE THE WORK READY

The brief is part of the work.

Start with a requirement, an accepted gap or a proposed change. Organize the response into epics and work items, then review the proposed architecture and the conditions for completion.

The readiness view checks where the work came from, what done means, the work contract, the architecture and open questions. It also checks freshness and the required setup. Higher-risk work needs stronger preparation before it can start.

Start with
Requirements, source evidence, a connected repository and the intended change.
Work toward
A work item with a scoped brief, acceptance criteria and a visible readiness decision.
Detail of the Product demo with fictional example data
ProcessScout / Productthe accepted scope a brief starts from · fictional data
02

WORK INSIDE THE BOUNDARY

A branch. A budget. A clear scope.

The approved brief binds the repository, starting revision, permitted paths, required checks and limits. Follow the work on the Control board as the coding engine prepares a draft pull request.

A failed check or requested change can return to the engine for a bounded repair attempt. Work that passes the required scope checks can be saved as a checkpoint, so an authorized person can resume a build that reached its time or credit limit.

Start with
An approved, current brief and an available configured build runner.
Work toward
A reviewable branch and draft pull request, with a timeline of attempts and checks.

One change, inside its boundary

  1. Bounded briefScope, sources and acceptance
  2. Draft changeOn a branch, within budget
  3. Human reviewBefore anything merges
Illustration · fictional example

NORTHSTAR / THE WORKED EXAMPLE

Require an owner before a handoff enters the queue.

A source-backed problem becomes a bounded work item: add an owner check, return incomplete requests and cover the normal and exception paths. Once your team deploys it, a linked measure can show whether handoffs improved. This is an example, not a recorded build result.

Walk through this example

ONE THREAD FROM THE REQUEST TO A READY-TO-DEPLOY BUILD.

  1. 01 / RequirementThe problem and the evidence behind it.
  2. 02 / Work itemThe scope, contract and definition of done.
  3. 03 / Pull requestThe code, checks and approval for this revision.
  4. 04 / Ready to deployBuilt, checked and handed to your team to deploy.
The artifacts stay connected, so the next reviewer can follow the work back to its purpose.
03

REVIEW THE ACTUAL CHANGE

Keep the evidence beside the decision.

An independent reviewer examines the diff. Required tests and checks remain attached to the build, alongside the findings and any repair attempts. The Quality view brings this evidence together across work items.

Approval applies to a particular version of the code. New commits clear an approval that no longer matches; the merge checks run again before the approved revision can move forward. Your organization’s approval policy determines who can make that decision.

Start with
The proposed diff, review findings and results of the required checks.
Work toward
An approval tied to the reviewed revision, or a clear request for further work.

Three checks before approval

  1. Required checksTests and scope, per revision
  2. Independent reviewFindings beside the diff
  3. Your approverApproves this exact version
Illustration · fictional example
04

HAND IT TO YOUR TEAM

Ready to deploy is not deployed.

A merged pull request is a milestone, not a launch. Build Factory prepares the approved revision ready to deploy. Your team deploys it through its own process and environment.

Where your environment reports back, the Releases view can record the environment, revision and how your team confirmed the change. The rollback plan stays with the build, so your team has it if a change needs reversing.

Start with
The approved revision and your team’s deployment and confirmation method.
Work toward
A ready-to-deploy build, with a record that keeps merged, deployed and confirmed distinct.

Build Factory stops at ready to deploy

  1. Ready to deployBuilt, reviewed, handed over
  2. DeployedBy your team, in your pipeline
  3. ConfirmedBy your team, against the brief
Illustration · fictional example
05

CLOSE THE LOOP

Give the change a measure.

Link a change to a relevant outcome measure. Once your team confirms it is live, the value loop can record a baseline and track later readings at the review points you set.

When no measure is linked, the product says so. This makes the next conversation concrete: what evidence would show that the change helped, who will supply it and when should the team review it?

Start with
A change your team has confirmed is live, and a linked outcome or measure.
Work toward
A baseline and follow-up readings connected to the change.
Detail of the Transform demo with fictional example data
ProcessScout / Transformexpected against observed · fictional data

THE PRACTICAL DETAILS

Know where
you stand.

Talk through your workflow
What do we need to get started?

Build Factory is in beta and needs enablement. Setup includes Build roles, a repository, a configured runner, provider credentials, an organization policy and a sufficient credit budget. We can walk through the available setup with you.

Which coding engines can it use?

Claude Code and Codex have implemented runner paths. Additional engines depend on configuration and capability verification; Devin is conditional and Cursor is not currently available through the factory. Engine availability is confirmed during setup.

Does it deploy changes on its own?

No. Build Factory designs and builds automations ready to deploy; your team deploys them. Readiness, risk, approvals and required checks still govern the work, within your organization’s configured policy. A person must resolve work that cannot meet those conditions.

YOUR NEXT CHANGE

See the workflow.
Make it your own.

Try the workflow, or bring one question from your business.

Product view

ProcessScout interactive demo · Fictional Northstar data