---
title: MUJ428 Trust Layer Glossary
description: Canonical terminology for MUJ428 intent-to-effect integrity, Trust Receipts, Verified Effects, evidence sufficiency, and consequential agent actions.
canonical_url: https://agents.muj428.com/glossary.md
md_url: https://agents.muj428.com/glossary.md
last_updated: 2026-08-19
---

# MUJ428 Trust Layer Glossary

Canonical terminology for the MUJ428 contract: **bind approved intent to verified effect**.

## Approved intent

The exact consequential action that has been authorized, including its arguments, target or counterparty, authority scope, ceilings, relevant premises, expiry, and allowed executor.

## Consequential action

An agent action capable of producing a meaningful external effect, including `PAY`, `BUY`, `DELEGATE`, `TRUST`, `ACCEPT`, `APPROVE`, `WRITE`, `RELEASE`, `COMMIT`, `PUBLISH`, and related mutations.

## Trust Receipt

A deterministic authorization artifact that binds approved intent to the conditions under which an executor may proceed. Free-preflight Trust Receipts have `execution_authority=false` and cannot authorize a consequential mutation.

## Verified Effect

A structured record of what actually happened after an authorized execution attempt, including the resulting effect state and evidence used to compare the observed effect with the approved action.

## effect_key

The stable idempotency/effect identity used to distinguish the intended consequential effect and prevent duplicate execution or replay from being confused with a new effect.

## action_id

The identity of the proposed or authorized action. It is distinct from `effect_key` and from the anti-replay nonce.

## nonce

A freshness/replay-control value used so an authorization cannot be reused as though it were a new authorization.

## Evidence sufficiency

The determination that available evidence is adequate for the requested trust decision under the relevant policy and assurance level. Insufficient evidence may produce `VERIFY`, `REQUIRE_VERIFICATION`, or `DENY` rather than manufactured certainty.

## policy_epoch

The version or epoch of policy assumptions bound into a Trust Receipt so a receipt can fail closed if policy has materially changed.

## resource_versions

Versions or freshness identifiers for resources whose state was relied upon when authorization was issued. Changed resource versions can invalidate stale premises.

## Mutation boundary

The last enforcement point at which a consequential side effect can still be prevented. The executor must validate and consume authenticated authorization at this boundary before committing the effect.

## Execution authority

The explicit permission for a receipt to authorize a consequential mutation. `FREE_PREFLIGHT` always has `execution_authority=false`.

## FREE_PREFLIGHT

MUJ428's zero-money trust-triage assurance level. It can return `ALLOW`, `VERIFY`, `REQUIRE_VERIFICATION`, or `DENY`, but it does not itself grant execution authority and does not move funds.

## OUTCOME_UNKNOWN

An effect state used when the system cannot safely prove whether the external effect committed. It prevents uncertainty from being silently treated as success or failure.

## External Verified Effect

A Verified Effect initiated or produced through a system MUJ428 does not control, with independently attributable evidence. MUJ428-controlled CI, self-traffic, registry publication, and synthetic runs do not qualify.

## Transaction Assurance

A paid MUJ428 assurance service for higher-value consequential transactions. MUJ428 verifies evidence and intent/effect integrity but does not custody transaction principal.

## Payment-rail-independent

MUJ428's trust contract is not tied to one payment provider or settlement rail. Payments are one effect class alongside other consequential actions.

## Independent verification

Verification that can be performed or corroborated without relying solely on a MUJ428 internal assertion. The strength of the claim must not exceed the independent evidence available.

## Sitemap

See the full [agent-readable sitemap](https://agents.muj428.com/sitemap.md) for public interfaces, specifications, examples, and integration surfaces.