ACYCLIC_
Metrik working session

Graham Goudeau

Massachusetts
software builder.

Software engineer. Then CTO. Now founder of Acyclic.

2013
MassachusettsResident since 2013.
2017
Tufts UniversityComputer Science, School of Engineering.
Career
Engineer → CTO → founderBuilt and led production software teams.
Acyclic · Boston, Massachusetts←→ to move
ACYCLIC_
Definition

What a software foundry is

A production system for purpose-built software.

The foundry turns one named operational workflow into one working application.

Each application fits the work. Every application uses the same operating foundation.

01Do not force every workflow into one product.
02Do not create a new operating stack for every application.
Specific applications. Standard operations.
ACYCLIC_
Operating model

The foundry pattern

Each application is specific.
The operating stack is shared.

Application 01

Field workflow

Built around one team and one acceptance journey.

Application 02

Review workflow

Built around a different owner and decision path.

Application 03

Public workflow

Built around a clear service and data boundary.

One operating foundation
IdentityDeploymentMonitoringBackupsSecuritySupportRetirement
Many applications can run without many separate platforms.
ACYCLIC_
Delivery capability

What the foundry changes

Technical delivery becomes a bounded contract.

01

Bounded scope

One workflow. One owner. One clean data boundary.

02

Objective acceptance

A complete user journey defines what “done” means.

03

Fixed terms

A fixed date and price replace an open-ended delivery promise.

Named workflow+Acceptance journey=Guaranteed technical delivery
The guarantee applies to a defined technical boundary.
ACYCLIC_
Working question

Where I can help Metrik

Name one delayed or excluded workflow.

I will define a second delivery lane around it.

01What will stay on paper, email, or spreadsheets?
02Who owns the workflow and accepts the result?
03What data can stay inside a clean boundary?
Next step: I will return a fixed-scope proposal within five business days.
Start with one workflow. Prove the delivery model.