Model supply is abundant. Strategy is the advantage.
Providers, clouds, gateways, and model releases will keep multiplying. The lasting advantage is knowing how a business uses that supply: what may run, what fits each task, what creates value, and what should change next. Millwork sits above the changing supply. It turns available capabilities into a governed, measurable system.Start with Solver
Millwork is the platform. Solver is the first product. Your application sends the work and its boundaries. Solver selects from the ready options your organization has made available, runs the chosen route, and checks the outcome. When live work completes, its output is stored as the result. The run’s separate receipt records execution evidence. Today, the private-preview journey begins with text models. Solver’s execution model also supports registered agent endpoints and reusable skills where those capabilities are available to your organization.Compose
Give models, agent endpoints, and reusable skills one execution model.
Govern
Put data, cost, time, and allowed actions beside the work.
Verify
Keep the useful output and a separate record of how it happened.
Where the leverage comes from
Millwork model pool
When a Millwork model appears in the live catalog, use it with your
organization key. You do not need to configure the provider key. The run
record keeps the source and billing owner clear.
Ranked routing
Solver keeps options that are ready and permitted, then ranks the eligible
set using the cost preference declared for the run.
Slice-level composition
Solver’s run and receipt formats are ready for work made of several parts.
Dynamic slicing is coming. It is intended to divide one task into bounded
slices, rank each slice, and keep them under one policy and receipt.
Evidence for better decisions
Receipts expose route, recorded usage, checks, and bounded actions so teams
can improve their capability mix and operating rules over time.
The compounding productivity axiom
Every capability a team adds should increase useful work faster than it increases operational complexity. When listed in the catalog, Millwork model access can make new supply easier to add. Ranking chooses among eligible options. Dynamic slicing will let different capabilities contribute to bounded parts of a task. Receipts will record which combinations ran, their usage, and whether configured checks passed. The same policy, lifecycle, and evidence model is reused each time. The system can grow without asking the application team to rebuild control around every new model, agent, or skill.Start small. Stay in control as you grow
Begin with one model and one public task. As the system grows, keep the same way to govern what may run, measure what happened, and compare cost, quality, and reliability using recorded cost, verifier outcomes, and terminal status.Output is one part of the answer
A response tells you what came back. The receipt shows the selected route and checks. On deployment-bound model runs, it can also preserve requested, resolved, and provider-reported model identity. Solver keeps that evidence beside the run. The result contains the useful output. The receipt records how the run happened while keeping the task and output separate. Use the result. Keep the receipt.One run, clearly handled
1
Make options available
Add a model from your live catalog or connect a provider account your
organization already uses. The API calls a registered option an
arm.2
Send the work and its limits
Describe the outcome. Set the allowed data, maximum cost, maximum runtime,
and any response permitted after a check.
3
Solver narrows the field
Solver keeps options that are ready and permitted for every declared data
class, then selects from that eligible set.
4
Solver runs and checks
An eligible option is selected, the work is tracked to a final state, and
the configured output check is applied.
5
Read the result and receipt
Use the output in your application. Keep the separate record of the route,
recorded usage, checks, bounded actions, and, when available, model provenance.
Made for the second day
Solver is for application and agent builders whose product has outgrown a single model call, and for platform teams responsible for access, spend, and run behavior across an organization. Millwork becomes valuable when one model call is no longer enough and the system still needs to stay explainable.Start with one public task
Run a text model through Solver, inspect the output, then read the receipt. The difference is visible in one run.See how Solver works
Follow one task from limits to evidence.
Run a model
Complete one public test task.
Evaluate fit
Compare the preview with your requirements.
Private-preview access is available to approved organizations.
See what is available today.