OpsDevCode

Public previewGoverned automation language

Mint

Governed automation language

Problem
Automation intent without a governed language.
Input
A Mint project, catalogs, and declared realizations.
Outcome
Canonical MintIR and an offline governed plan — not an apply.
Availability
Public preview / alpha. Local install. Not production-ready.
pipx install specmint
# or: uv tool install specmint
Mint
Named source compiled across a cut into a governed plan.

by OpsDevCode

Get startedView sourceBuild an integrationAll products

What Mint does

Mint expresses governed automation intent. It compiles that intent deterministically and offline. It resolves capability, target, and integration realizations. It produces governed plans. It hands lifecycle control to SpecMint. It preserves verification and evidence boundaries — it does not move them into the language.

Mint versus SpecMint

Mint is the language, CLI, SDK, editor, and protocol. SpecMint is the lifecycle runtime and control plane behind Mint. SpecMint is not a customer SKU. SpecMint core is public; the hosted service stays private and is not generally available.

How it fits

Mint is the public entry layer. SpecMint composes the governed lifecycle. Repave, Overpass, Toll, and Dispatch retain capability authority in their domains. Integrations connect external services without taking that authority.

Working quickstart

Install the language CLI, then confirm the executable:

pipx install specmint
# or: uv tool install specmint
mint version

From the language repository, run check, fmt --check, lock --check, compile, inspect, and plan against examples/projects/local-marker, then integrations conformance for local.sandbox. Use the language quickstart for the full copy-pasteable sequence rather than treating this page as captured terminal output.

Integration ecosystem

A capability is the promise Mint and SpecMint understand. An integration is how that promise is realized for a service. A realization binds capability, target, and integration. An executor is the privileged runtime allowed to perform an approved operation. Planning support never grants execution authority.

Read Integration Protocol v0 and authoring plus conformance. A hosted registry is future work.

Safety

Public preview / alpha. The language CLI is installable. There is no mint apply and no default live provider execution. Compilation is deterministic and fail-closed. Not production-ready. Hosted SpecMint stays private.

  • Public preview / alpha — not production-ready.
  • There is no mint apply.
  • No default live provider execution.
  • Deterministic and fail-closed on unsupported required capabilities.

Owns

  • Intent authoring in Mint, with JSON, YAML, and structured Markdown as inputs
  • Deterministic offline compilation to MintIR
  • Capability, target, and integration realization binding
  • Governed plan production without apply
  • Language CLI, SDK, editor, and Integration Protocol v0
  • Conformance for language and integration contracts

Boundaries

  • Repository lifecycle (Repave)
  • Infrastructure state custody (Overpass)
  • Engineering economics (Toll)
  • Cross-domain intelligent experience (Dispatch)
  • Hosted SpecMint as a customer SKU
  • Live provider apply or mint apply

Install MintRead the quickstartLanguage sourceSpecMint sourceBuild an integrationFile an issue