Surface Notice|Validation Lab is the public evidence adjudication surface for MPLP. It publishes evidence-based verdict views, not certification, compliance marks, or execution hosting.
Snapshotrc-20260131161432
Inventory Date2026-01-31

Standards

Evaluation Methodology

METHOD-VLAB-01v0.17.0 Sealed

A bounded, non-certifying method for adjudicating evidence packs under explicit ruleset identities.

⚠

Non-Certification & Non-Endorsement

The Validation Lab evaluates evidence packs, not live systems. We issue verdicts under a selected ruleset identity, not certifications of quality, safety, or protocol truth. A PASS verdict means the submitted evidence satisfied that ruleset's current criteria.

01. How to Read a Verdict

Evidence maturity classifications and cryptographic guarantees.

📊 How to Read This Table

Reproduced

Real evidence pack with verifiable hash/seal

Can download, re-run locally, compare hash

✓ Reproduced = downloadable pack + deterministic recheck + hash matches release seal

Simulated

Synthetic evidence pack (not from real execution)

For demo/coverage only, not dispute-ready

Dispute Ready

FAIL verdict with evidence pointers to triggered clauses

Arbitration-ready: clause + evidence + FMM pointer

Declared

Manifest/metadata only, no downloadable evidence

Cannot be independently verified

Domain Labels (D1, D2, D3, D4)

d1Provenance: Identity, environment, provenance integrity
d2Lifecycle: Execution lifecycle, state transitions
d3Arbitration: Dispute resolution, evidence pointers
d4Interop: Cross-framework protocol compliance

Host vs Interop

Host= Orchestration framework running the agent (LangGraph, CrewAI, etc.)
Interop= Protocol stack used for cross-framework communication (MCP, A2A, ACP)

02. Current Public Lab Model

Two coexisting adjudication lines, kept distinct on public Lab surfaces.

LEGACYV1 LG Line

Legacy V1 Lab guarantees come from governance/LIFECYCLE_GUARANTEES.yaml and are adjudicated under ruleset-1.0 at presence-level strength.

V2Clause Bundle Line

V2 public bundles are exposed under public/_data/v2/rulesets/ and displayed as clause IDs. They coexist with the legacy V1 line and must not be collapsed into one doctrine.

Historical teaching families such as D1–D4, pack-v*, and ruleset-1.1/1.2 remain lineage context only. They are not the primary public teaching model for the current aggregate V1/V2 Lab surface.

03. Evaluation Object

The Lab evaluates an evidence pack plus a selected ruleset identity.

The Evidence Pack is the Lab's input bundle. It is a portable adjudication input, not a protocol-definition artifact and not a certification object.

  • ✓
    Evidence Pack ContractUse the public contract page for the contract boundary and compatibility story.
  • ✓
    Ruleset IdentityEvery verdict must be read through the selected validation_ruleset_version.
  • ✓
    Version DomainsKeep protocol version, schema bundle version, ruleset identity, and Lab release version distinct.
  • ✓
    BoundaryProtocol invariants and protocol meaning remain repo/docs truth; Lab adjudicates submitted evidence only.
reading order
1. Read the evidence pack contract
2. Read the pinned ruleset identity
3. Read the adjudication output
4. Recheck the verdict hash locally
5. Do not infer protocol meaning from Lab UI copy alone

04. Self-Audit Path

Independent recheck path without trusting the Lab UI.

1. Select Run

Find a run in the /runs index and inspect its evidence bundle.

2. Check Ruleset

Verify the evaluation logic matches the Ruleset ID claimed by the evidence pack.

3. Verify Record

Find the release record in /releases and compare the published hash.

4. Local Hash

Run a local hash recheck on the pack. Matching the published record confirms projection integrity, not runtime quality.

Start HereBrowse RunsetsEvidenceAll RunsVerificationRelease Records