Skip to main content
⚠️ Draft — Non-authoritative content (noindex)
INFORMATIVEDRAFTnone
Truth Source: Repository schemas and tests are authoritative.

Ruleset Reference

[!IMPORTANT] Non-Normative Document

This document is informative only.

[!NOTE] Verified Source Model This page is a Documentation-surface first projection of the same upstream source model currently bound to Validation Lab /rulesets and /rulesets/[ruleset_id]:

The ruleset surface is therefore an aggregate V1/V2 projection, not a manifest-only page.

What is a Ruleset?​

A ruleset is a versioned adjudication line used by Validation Lab to evaluate evidence packs. The current Lab ruleset surface has two verified source lines:

  • a V1 manifest line under data/rulesets/
  • a V2 bundle line under public/_data/v2/rulesets/
Key Principle

Same evidence + same ruleset identity = same verdict hash.

That determinism claim is enforced by the Lab's ruleset and adjudication model, not by docs prose.

Current Version Domains​

The ruleset surface currently exposes several distinct version domains:

DomainWhere It AppearsCurrent Verified Expression
Ruleset identityV1 manifests, V2 bundlesruleset-1.x, ruleset-v2.x.y
Ruleset compatibilityV1 manifestsevidence_pack_contract, min_pack_version, max_pack_version
Protocol pinV1 manifestsprotocol.version
Validation Lab release identitybroader Lab governanceseparate from ruleset identity
Legacy Label Note

Older Lab materials may still mention pack-v0.x labels. For the current verified ruleset source model, the V1 manifests now express compatibility through evidence_pack_contract, min_pack_version, and max_pack_version.

Current V1 Manifest Inventory​

The current V1 manifest line in Validation_Lab/data/rulesets/ contains:

RulesetStatusLineDeclared Compatibility
ruleset-1.0activeLegacy lifecycle guaranteesevidence_pack_contract: 1.0, min_pack_version: 1.0, max_pack_version: 1.x
ruleset-1.1draftFour-domain adjudicationevidence_pack_contract: 1.0, min_pack_version: 1.0, max_pack_version: 1.x
ruleset-1.2draftSemantic invariant adjudicationevidence_pack_contract: 1.0, min_pack_version: 1.0, max_pack_version: 1.x
ruleset-1.3activePhased evolution lineevidence_pack_contract: 1.0, min_pack_version: 1.0, max_pack_version: 1.x

Current V2 Bundle Inventory​

The current V2 index in Validation_Lab/public/_data/v2/rulesets/index.json publishes:

Ruleset BundlePublication State in Current IndexClause CountNotes
ruleset-v2.0.0Indexed7Current bundle bound directly to the Lab /guarantees route
ruleset-v2.0.1Indexed8Later V2 bundle published in the current index

The V2 line is bundle-backed rather than manifest-backed. When the Lab detail route resolves a V2 ruleset, it does so through the unified loader and the corresponding bundle file.

How to Read the Ruleset Surface​

Use the current source model this way:

  • Use the V1 manifest line when you need manifest-declared status, protocol pinning, and compatibility fields.
  • Use the V1 requirements files when you need the detailed legacy requirement set for a V1 ruleset.
  • Use the V2 index and bundle files when you need the current V2 bundle inventory and clause payloads.
  • Use Lab Site: Rulesets when you need the live aggregate projection as rendered by the Lab surface.

Ruleset Governance Boundary​

Ruleset governance remains in Validation Lab, not in the Docs surface. This page is a first projection of the verified ruleset assets; it does not supersede:

  • the unified ruleset loader,
  • the V1 manifest and requirements files,
  • or the V2 bundle files currently consumed by the Lab routes.