How It Works

One pipeline. Three guarantees.

Mortar turns compatibility governance into an executable control path: detect drift, score risk, enforce policy, log every decision.

Insight

1. Generate structural evidence

$ mortar diff --base examples/openapi/v1.yaml --head examples/openapi/v2_breaking.yaml --out diff-report.json
DiffReport written: diff-report.json
Findings: 4
Breaking findings: 2
- removed operation: GET /users/{id}
- changed field type: User.id (string -> integer)

Foresight

2. Produce release authority output

$ mortar score --base examples/openapi/v1.yaml --head examples/openapi/v2_breaking.yaml --policy mortar.policy.yaml --json
{
  "score": 64,
  "classification": "BREAKING",
  "decision": "BLOCK",
  "audit_log": ".mortar/audit/2026-02-19T12-58-03Z.jsonl"
}
exit code: 1

Authority

3. Enforce in pipeline runtime

# .github/workflows/ci.yml
- name: Mortar Gate
  run: |
    mortar score \
      --base examples/openapi/v1.yaml \
      --head examples/openapi/v2_breaking.yaml \
      --policy mortar.policy.yaml

# Result: workflow fails on BLOCK decision

Execution Flow

Those three commands execute this exact pipeline.

`mortar diff` starts Ingest and Diff, `mortar score` executes Score and Decide, and CI policies enforce the final gate while writing the audit trail.

Definition

What is a LIM?

LIM means Large Intent Model: a domain-specific judgment layer that interprets change context and produces structured intent output for governance. The LIM pattern is established in Delta OS and reused in Mortar as the interpretation layer.

Reference: deltaos.dev

Drift evidence engine: diffing.so

Governance Guarantee

AI can analyze risk. Only policy can approve release.

Mortar’s LIM interface supports advanced interpretation, but ship/no-ship authority remains deterministic in the kernel.

$ mortar validate --spec examples/openapi/v1.yaml
Spec valid: OpenAPI 3.0
Paths: 12
Operations: 34
Status: OK

Run Quickstart Create Account