Mint · Platform teams
Governed intent without a required stack
Platform leaders need a repeatable way to name change. Application teams need a plan they can review. Mint stops at that plan. Repave, Overpass, Toll, and Dispatch stay optional.
Language siteTalk to OpsDevCode
Problem
Automation intent lives in tickets, READMEs, and scripts. Reviewers cannot tell a plan from an apply. Domain products get asked to become the source of truth for everything.
Benefit
Teams compile the same intent into an offline governed plan. Authority for repositories, infrastructure state, and economics stays with those products when you adopt them. Mint is not a required first product.
Example
A team wants a sandbox marker created the same way every time. Mint compiles local.sandbox.ensure_marker and produces a plan. It does not write the marker and does not call AWS, Azure, or GCP.
Availability
Public preview / alpha. Not production-ready. No mint apply. No hosted Mint SKU.