An applied software engineering lab

Build the factory.
Make the software yours.

We’re developing software factories, useful applications, and the tools and materials to adapt them with your agents.

ASSEMBLE. INSPECT. MAKE IT YOURS.A PHYSICAL METAPHOR FOR SOFTWARE.
THE ASSEMBLY FLOOR
Build toward bigger ambitions.Drag to rotate. Arrow keys when focused; Home to reset.
THE MACHINERY, UP CLOSE

Every part has a part to play.

Open the blueprint to inspect the pieces. Disassemble the model to see how they fit together.

Hover a blueprint label, or choose a part.
Many factories. Many kinds of work.

A review tool and an application builder need different machinery. Explore the parts above; discover the software below.

01 / What comes out of the lab

Start with a system.
Or just the part you need.

Five connected families of work. Individual releases are being developed and qualified; availability is shown in the catalogue.

02 / A concrete example

The system runs.
Then your agent
makes it fit.

A request-and-approval desk for the way your business works.

Start with incoming requests, approval rules and a decision history. Ask your agent to add a second approval above a chosen amount. Inspect the change and the checks that support it.

Concept preview · An example of the software and adoption experience we’re developing.

Explore the example
↳Request deskConcept
SAMPLE WORKSPACEWork, with a clear next step.
01
Equipment requestOperations · $7,250
Needs approval
02
Supplier onboardingProcurement · Documents attached
In review
A CHANGE YOU COULD ASK FOR

“Require two approvals for requests above $5,000.”

SpecificationChangeChecks
Explore the proposed workflow

A broad field of work

A studio. A workspace.
A whole new system.

Explore all directions ↗

03 / More than a code download

Use the software.
Adopt the project.

Two ways to get value from a system. The available path, exact rights and support will belong to each release.

USE

Get the job done.

Work with a product in its supported environment: a local application, your own infrastructure, or a hosted service where offered.

ADOPT

Make it part of your business.

Take a versioned implementation and the engineering materials your coding agent needs to understand and change it.

Source

The working implementation and its dependencies.

Specifications & schemas

What the system should do, and the data it understands.

Agent context

Architecture, instructions and supported extension points.

Checks & fixtures

Examples and tests for a meaningful change.

Setup & recovery

How to run, maintain and recover the named release.

Rights & support

Explicit permissions and responsibilities for that offer.

Each release will define its contents, supported environment, rights and maintenance responsibilities.

04 / Work where you work

A native workspace.
Your existing coding agent.

Keep your workspace and your agent. We’re developing native and external access paths around inspectable software and clear interfaces.

FIRST-PARTY WORKSPACE / IN DEVELOPMENT

Novalis

A native home for terminals, agents and project work. The planned factory connection brings definitions, artifacts and decisions into the same workspace.

Explore the native direction ↗
EXTERNAL CLIENTS / PLANNED INTEGRATIONS

Bring your agent.

CLI, API and MCP paths for inspecting packages, making permitted changes and returning evidence. Supported clients and execution requirements will be documented per release.

See the access model ↗

05 / Research through engineering

Build. Learn.
Make the next one better.

Applications test the machinery. Field notes explain the ideas, tradeoffs and questions behind the work.

From the lab

Follow the work as it takes shape.

Explore the engineering, read the field notes, or get in touch about a particular system.

Follow the work