Approach

Define the outcome. Govern the change. Verify the result.

OpsDevCode Platform is how those three steps stay distinct. Humans, automation, and agents can express intent. Domain products still own gates, stores, and evidence.

How the work is designed

01 /
Domain authority stays with the domain
Coordination does not transfer ownership.
02 /
Integrate commodity. Own differentiation.
OpsDevCode integrates systems such as source control, cloud platforms, infrastructure engines, and observability rather than rebuilding them merely for ownership.
03 /
Intent is not authority
Understanding an outcome does not automatically authorize its execution.
04 /
State before automation
Reliable action depends on understanding what should be true and what is actually true.
05 /
Evidence over assumption
Changes should produce enough evidence to determine what happened and whether the intended outcome occurred.

01
Define the outcome
Mint is the public intent language and toolchain. It is how a requested change is named and compiled. It is not the customer result — domain products still own gates and evidence.
02
Govern the change
SpecMint is the governed lifecycle runtime. SpecMint core is public; hosted execution stays private. Products still own their gates.
03
Verify the result
A governed change or a refusal — plus a record of what ran and why.
04
Who asks
A human, an automation, or an agent. Dispatch can carry the conversation. Relay is supporting conversational runtime, not a product in the family.

Intent
A requested outcome from a person, automation, or agent.
Context
Domain state, identity, and the requested change.
Policy evaluate · ink
A decision boundary. Not a product domain and not a fifth accent.
Allowed or refused
Allowed work continues into a domain change. Refused work stops.

Software state
Repave
Infrastructure state
Overpass
Economic state
Toll
Governed intent
Dispatch
Policy gate
Ink plane. Not a product domain. Authority stays with the domain that evaluates it.