| Problem | Automation intent lives in tickets and scripts, with no governed language. | Repositories drift from the approved path. | Infrastructure change without durable, readable state. | Cost without engineering ownership. | Intent that cannot be proposed or refused with evidence. |
|---|
| Input | A Mint project, catalogs, and declared realizations. | An approved baseline, a repository, and a requested lifecycle change. | Accepted Terraform or OpenTofu state the product already holds. | FOCUS evidence and identified utilization samples. | A request toward a domain product that already owns the work. |
|---|
| Outcome | Canonical MintIR and an offline governed plan — not an apply. | A gated generate, adopt, update, upgrade, observe, or remediate record. | Inventory, proven relationships, impact, drift, and a gated state transaction. | Spend and utilization tied to engineering context — evidence, not an invoice. | A proposal, a confirmation boundary, or a refusal — not a new store. |
|---|
| Availability | Public preview / alpha. Local install. Not production-ready. | Early access. Hosted generate is waitlist and invite. | In development. Hosted custody is enabled per early-access partner. | In development. Spend and waste execution still run in Repave. | Emerging. Public identity exists; the hosted assistant still runs in Repave. |
|---|
| Maturity | 00·Public preview | 01·Early access | 02·In development | 03·In development | 04·Emerging |
|---|
| Next step | Get started | Request early access | Explore Overpass | Explore Toll | Explore Dispatch |
|---|