Software factory

  1. 01Intake
  2. 02Requirement
  3. 03Design
  4. 04Work order
  5. 05Build
  6. 06Testing
  7. 07Sign-off
  8. 08Memory

Turns a business request into an approved work order. The instance is mapped, a versioned technical design is written, blast radius is calculated, and a named person reviews the design before anyone builds.

Book a working session Next: SDLC automation

In the workspace

One workspace. Every part of delivery.

The workspace that turns a request into an approved work order. Projects, intake, work orders, and artifacts share one context.

What it covers

Intake through work order.

Four gates. A request comes in as plain language. It leaves as build tasks and test tasks, written from the same obligations, against a design a named person has signed.

01

Intake

A plain-text business request, taken from the channel it was said in. No template required. The platform decomposes it into detailed, testable functional requirements.

02

Requirement

Obligations are written so they can be tested. Conflicts are flagged before design is locked. Requirements sit in the same workspace as the application they will change.

03

Design

A full technical design document, versioned and kept current as the work changes. Dependency, impact, and blast radius are calculated from the actual record of the environment, not reconstructed in a workshop.

Gate 1

Design Authority Review

A named human approves the design before any build begins. The gate cannot be turned off. The record shows who approved, and against which version of the design.

04

Work order

Task orders for build and test, written together from the obligations. SDLC automation executes them. Nothing is built against an unapproved design.

Also in this workspace

Application Explorer sits beside the work order.

Each application as its own workspace, with data model, logic, security views, and Ask Gene against that application’s record. Ask Gene is present on every screen. It carries the context of whatever was opened.

Why this exists

Blast radius before a line is built.

Today, requirements sit in queues and nobody can see what a change will break until it breaks. The factory holds design intent and current state together, so blast radius is known before build starts.

The risk in AI-assisted delivery is not that a model produces something wrong. It is that no one can prove what changed, why, on whose authority, and whether it was tested. Gate 1 is the first half of that proof.

Software factory ends at the work order. SDLC automation takes the approved design into the instance. Organizational Memory files what this pass learned.

Handoff

The work order is the handoff.

A named reviewer signs the design. SDLC automation executes that work order in the instance.

Next: SDLC automation Book a working session