Policy

Intake Policy

How evidence packs are received, evaluated, and adjudicated.

Governance Boundary

Non-certification · Evidence-based verdicts only · No endorsement · No execution hosting · Full statement →

1. What the Lab Receives

✓

Evidence Packs

Structured bundles containing manifest, timeline, snapshots, and artifacts.

✗

Source Code or Binaries

The Lab does not execute your code. Evidence is produced externally by you or your tooling.

✗

Framework Adapters

The Lab does not ship or maintain adapters for any framework. Evidence producers are community-maintained.

2. Admissibility Criteria

An evidence pack must meet the following to be evaluated:

REQ-01Valid manifest.json with pack metadata
REQ-02Timeline events with required schema fields
REQ-03Pinned ruleset_version and protocol_version
REQ-04Required artifacts for declared ruleset (varies by ruleset)

See Export Contract for full schema.

3. Status Taxonomy

Each run progresses through these states:

Status	Meaning	UI Behavior
`REGISTERED`	Run is in allowlist; pack may exist but is not closure-complete	Verdict/Recheck disabled
`EVIDENCE_READY`	Pack is closure-complete with `pack_root_hash`	Verdic/Recheck disabled (pending adjudication)
`ADJUDICATED`	verdict.json exists with deterministic `verdict_hash`	Verdict/Recheck enabled; clickable
`NOT_ADMISSIBLE`	Failed admission gates (schema, structure, or integrity)	Verdict shows failure reason
`NOT_EVALUATED`	Deliberately not evaluated (out of scope or deferred)	Grayed out with reason

4. Responsibility Boundary

Lab Responsibility

• Evaluate evidence against versioned ruleset
• Produce deterministic, recheckable verdicts
• Maintain admission gates and reason codes
• Publish adjudication bundles with verdict_hash

Producer Responsibility

• Produce evidence packs externally
• Ensure pack meets admissibility criteria
• Pin correct protocol/schema versions
• Resolve NOT_ADMISSIBLE issues and resubmit

5. Minimal Pack Structure

A minimal evidence pack contains:

evidence-pack/
├── manifest.json        # Pack metadata (run_id, ruleset_version, etc.)
├── timeline.json        # Event sequence with timestamps
├── snapshots/           # State snapshots at key points
│   └── *.json
└── artifacts/           # Domain-specific artifacts (plan.json, etc.)
    └── *.json

See Evidence Producers for working examples.

Browse Runs →View Adjudications →Export Contract →