MPLP Lab V2 Baseline Adjudication

ID: ruleset-v2.0.1•Version: 2.0.1

v2 SOURCEactive

Overview

This ruleset defines the adjudication criteria for evidence packs targeting version 2.0.1. It is sourced from the V2 Unified Index.

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

PROV-V2-01
PROV-V2-02
LIFECYCLE-V2-01
LIFECYCLE-V2-02
TRUST-V2-01
DET-V2-01
METADATA-V2-01
PATCH-V2-01

Requirements & Pointers

core-invariants

PROV-V2-01CRITICAL

Substrate Reference Integrity

Manifest must contain a valid substrate_ref with upstream pinning.

PROV-V2-02CRITICAL

Lock Integrity Enforcement

Manifest must contain a valid lock_ref with a non-pending lock_sha256.

LIFECYCLE-V2-01CRITICAL

Trace Artifact Existence

The run must include a valid trace.json artifact with a verdict.

LIFECYCLE-V2-02CRITICAL

Timeline Data Presence

The run must include non-empty timeline events.

TRUST-V2-01CRITICAL

Runner Seal Verification

The run must be sealed with a unique runner image_digest. (Updated in v2.0.1: Hash pinning required)

DET-V2-01CRITICAL

Canonical Determinism Proof

The manifest must record a valid canonical pack root hash.

METADATA-V2-01WARNING

Execution Timestamp Integrity

The run must have a valid UTC execution timestamp.

PATCH-V2-01INFO

Patch Verification

Ensures patch level integrity.