Intent
What the user or system wants.
Experimental · Pre-release · Not production ready
Machine Intent Contracts (MIC)
A trust and evidence framework for automated decision-making, regulated workflows, and secure task execution.
Intent → Contract → Verification → Execution → Evidence
What is MIC?
A contract before a sensitive machine action.
MIC describes machine work as a signed, auditable contract.
Instead of allowing automation, AI agents, or backend systems to perform sensitive actions directly, MIC defines what is being requested, what rules apply, what actions are allowed, and what evidence must be produced.
MIC is not an AI model.
MIC is not a workflow engine.
MIC is a trust layer between intent and execution.
How MIC works
Explicit intent. Bounded execution. Verifiable evidence.
Contract
A signed machine-readable request.
Runtime
Validates version, signature, manifest, policy and limits.
Engine
Performs only work explicitly approved by the bundle.
Evidence
Produces a structured, hashable result.
Audit
Records proof of what was requested and checked.
Browser validator
Validate a MIC bundle locally.
Input stays in this browser
Structural validation only.
This browser validator performs structural validation and hashing
only. It does not prove that a runtime binary is safe,
independently audited, or production-certified. Only trust signed
releases from known maintainers.
Example use cases
Designed for work where evidence and control matter.
AI Agent Governance
Require AI agents to request approval through a signed contract before performing sensitive actions.
Regulated Change Control
Verify approvals, rollback plans, change windows and audit requirements before system changes are allowed.
Compliance Evidence
Generate structured evidence that required checks were completed before a regulated decision is accepted.
Explore MIC