Platform features
Our engineers and your team work in one shared workspace that supports each stage of the CLEAR method. It records how your system behaves, holds the specification, runs the build, compares results and controls the release to production. Fabrica is in development, so each feature below shows its current status.
Observation and evidence map
In prototypeLiving documentation and System Specification
In prototypeAgent build board
In developmentProof and reconciliation
In developmentShift controls
In prototypeCost and control
Design principlesData handling and access
Rails firstSupported stacks
Status as of October 2026. A pilot confirms which components are available for your system.
Fabrica connects to your running system through a guided setup and records what it does. Requests, background jobs, queries, errors and report runs are correlated and tagged by release. Paths that haven't been observed yet appear on the map as gaps.
Illustrative example. Names and figures are not from a client system.
A requirement recovered from finance meeting notes.
Observed behavior and owner reviews become requirements written in a structured, testable form. Each one has a stable ID and links back to its evidence and forward to the work that implements it. Approved requirements make up the System Specification, and each approved version is locked. Later changes create a new version.
Business analyst, architect, developer, QA and DevOps agents move work items through declared stages. Your engineers approve plans, merges, configuration and budget, and items waiting on a person are flagged on the board.
Shown with prototype data.
Illustrative proof report.
The rebuilt workflow and the current system are tested against the same specification. Fabrica replays or shadows representative workloads with side effects controlled and compares business outcomes, totals, reports, permissions and performance.
A routing layer in front of the current system moves traffic to the rebuilt workflow by cohort, and each step is gated on evidence. Rollback is a routing change. Data cutover is planned as a separate workstream.
Dashboard from the Fabrica prototype.
A dashboard shows spend by day, item and role, along with sandbox time and the items waiting on a person. Daily and per-item caps pause work before it overruns.
These principles apply from the first assessment. Specific controls are agreed with your technical team before any access is granted.
Observation and analysis use read-only access, agreed with your engineers.
Sensitive payloads are redacted before analysis.
Collection overhead is measured, and collection failures can't affect customer requests.
Code lives in your repository and runs on infrastructure you choose.
Ruby on Rails with PostgreSQL is the first supported stack, because its instrumentation and schema tooling are mature. We can discuss Java Spring, .NET Framework, PHP and Django systems, and an assessment confirms what observation is possible. Read the engineering detail
Tell us about it on a 30-minute call. We'll suggest a first scope and what a technical review would need to confirm.