Notice|This lab provides evidence-based verdicts, not certification. No compliance marks or endorsements are issued.
Buildrc-20260131161432
SSOT2026-01-31
Back to Rulesets

MPLP Validation Lab Ruleset (Phased Evolution - v0.13.1)

ID: ruleset-1.3Version: 1.3.0
v1 SOURCEactive

Overview

This ruleset defines the adjudication criteria for evidence packs targeting version 1.3.0. It is defined in the local filesystem.

Domains (D1–D4)

Domains group clauses by verification dimension. Each domain defines what is checked,which evidence must be present, and what failure means.

D1Provenance & Identity
Definition:

Verifies the runner's identity, environment fingerprint, and manifest integrity before execution begins.

Evidence checked:

runner_id, env_hash, manifest_seal, version_pin

If FAIL:

Evidence pack cannot be trusted — origin or environment is unverifiable.

D2Lifecycle & State
Definition:

Verifies execution lifecycle integrity: state transitions, timeline consistency, and event ordering.

Evidence checked:

event_log, state_diffs, timeline_hash, step_sequence

If FAIL:

Execution sequence is inconsistent — events may be missing, reordered, or fabricated.

D3Arbitration & Dispute
Definition:

Provides pointers for dispute resolution: evidence locations, FMM markers, and triggered clause references.

Evidence checked:

triggered_clauses, fmm_pointer, evidence_uri, diff_payload

If FAIL:

Run is not dispute-ready — arbitration cannot proceed without valid evidence pointers.

D4Interop & Protocol
Definition:

Validates cross-framework protocol compliance (MCP, A2A, ACP) and handoff integrity between agents.

Evidence checked:

protocol_stack, handoff_log, interop_seal, bridge_events

If FAIL:

Cross-framework communication violated protocol spec — handoff integrity cannot be verified.

Core Invariants

  • CL-D1-01
  • CL-D1-02
  • CL-D1-03
  • CL-D2-01
  • CL-D2-02
  • CL-D2-03
  • CL-D3-01
  • CL-D3-02
  • CL-D3-03
  • CL-D4-01
  • CL-D4-02
  • CL-D4-03
Contract1.0
Target Packs1.0 - 1.x
Validation Lab — MPLP