Skip to content

Ring 038: conformance vector schema v2 — add phi_distance and verdict fields #133

@gHashTag

Description

@gHashTag

Ring 038: Conformance Vector Schema v2

Phase: HARDEN | Layer: CONFORMANCE | Parent: #126

Problem

The 34 existing conformance JSON vectors lack two critical fields: phi_distance (for GoldenFloat benchmarking) and verdict (CLEAN/TOXIC). Without these, conformance vectors cannot serve as the benchmark suite for academic comparison with bfloat16/takum.

Goal

Define conformance/SCHEMA_V2.json and migrate all 34 existing vectors to v2 schema, adding phi_distance and verdict fields.

Schema v2

{
  "schema_version": 2,
  "module": "gf16",
  "ring": 26,
  "seal": "sha256:...",
  "cases": [
    {
      "id": "gf16_add_001",
      "input": {"a": 1.618, "b": 0.618},
      "expected": 2.236,
      "tolerance": 1e-6,
      "phi_distance": 0.049,
      "verdict": "CLEAN"
    }
  ]
}

Specs to modify

  • conformance/SCHEMA_V2.json (new - schema definition)
  • All 34 conformance/*.json files (add fields)
  • tests/validate_conformance.sh (validate v2 fields)

Acceptance criteria

  • SCHEMA_V2.json defines the schema
  • All 34 vectors migrated to v2
  • phi_distance field present in all GoldenFloat vectors
  • verdict field is CLEAN for all existing passing vectors
  • Validation script rejects v1-format vectors

Seal requirements

  • seal --save conformance/SCHEMA_V2.json
  • Re-seal all 34 updated vectors

Dependencies


Branch: ring/038-conformance-schema-v2 | Commit: feat(ring-038): conformance vector schema v2 [SEED-38]

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions