The catalogue / Work in development
Explore what the lab is making, what a release would contain, and how it could fit your work.
The catalogue is taking shape. Releases are being qualified; each offer will identify its actual contents, supported access paths, pricing and terms before becoming available.
Workspaces, business tools and infrastructure. Useful on their own, with a path to make them part of your work.
Our first-party native workspace for terminals, agents and the work around them. Factory access is a planned integration, not an available release.
Engineering workflows assembled from tools, context, execution and checks. Different factories for different kinds of work.
Recipes for changing a system, reviewing a revision or assembling a starter. Each needs its own inputs, permissions, checks and recovery path.
Agent-facing tools, durable work, context, observation and verification. Small components with clear boundaries.
Existing engineering work is being evaluated for independent releases. The goal: a useful component you can inspect, connect and replace.
Applications with source, specifications, schemas, agent context and tests. Start with a system, then make it fit.
A business operations starter for incoming requests, approval rules and a decision history. Explore the proposed adoption experience in the workshop.
Setup, integration, migration and validation around specific software. A concrete deliverable with a finish line.
Bounded services that help a team adopt a named system. Scope, responsibilities, completion checks and support will be defined per offer.
Use / Adopt / Operate
Use a product for its behavior. Adopt a project to integrate and modify it. Decide who operates it and pays for the resources.
The working implementation and its dependencies.
What the system should do, and the data it understands.
Architecture, instructions and supported extension points.
Examples and tests for a meaningful change.
How to run, maintain and recover the named release.
Explicit permissions and responsibilities for that offer.
An individual package, a future Builder Access collection, and a scoped service may have different terms. Hosted usage would be a separate consideration where offered. Source access, redistribution rights and included services will be stated explicitly.
Access follows the work
One product need not require every interface. Each release will identify the paths that actually work.
Terminals, agents and project tools in a first-party native application. Bringing factory state and evidence into Novalis is planned work.
Inspect context, call permitted tools and return changes through documented interfaces. Client access and the executor doing the work have distinct permissions and costs.
A library of systems, projects, runs, packages and connections. Explore the proposed experience with a sample business workflow.
Open workshop preview ↗