Software Factory

What you'll see

The fictional company's app on one side and the engineering control room on the other. A ticket moves through each stage, and each stage shows its real output:

What it is built on

A planned public demo of a ticket-to-reviewed-change workflow. The underlying Factory tooling exists locally: it moves a job through stages, runs independent reviewers, freezes acceptance criteria once the first milestone passes, and takes owner approval outside the coding session. No public demo or public source yet.

• A stage can only advance when its gate passes; the session can only request approvals, which the owner grants or denies on a separate channel.
• A grant is bound to content: if criteria, review, demo checklist or handoff change after approval, the gate closes until re-approved.
• Acceptance criteria and checks are frozen once milestone 1 passes; changes go through an explicit revise or change-request path.
• Independent reviewer runs are recorded with the binary that executed them.

The rules it will run under

• Visitors choose from prepared tickets. Free text is a suggestion, never a command that runs code.
• Work happens in a throwaway copy, with budget and time limits enforced on the server.
• Nothing merges without an authorized human approval, and nothing reaches production.
• When a live run isn't possible, a recorded real run plays, labelled as a recording.

The measurement that comes with it

A planned controlled comparison of the same model working four ways: on its own, with the knowledge base, with the harness, and with both. It will count tickets fully verified per dollar and per hour. It is a design today. Results will appear here only after the runs are done and checked.