Problem
External solver results need a first-class candidate replay artifact that records why a sample was accepted or rejected. The artifact must bind problem hash, compiled model hash, assignment domain, reported energy, solver metadata, and embedding metadata.
Acceptance Criteria
- Define a JSON-compatible replay artifact schema for accepted and rejected candidates.
- Include explicit rejection reasons for hash mismatch, missing variables, unknown variables, energy mismatch, and malformed metadata.
- Add deterministic examples for one accepted candidate and multiple rejected candidates.
- Ensure certificates fail closed when replay evidence is inconsistent.
- Document that local replay is the verification authority.
Boundary
Solver metadata is recorded as evidence supplied by the external tool. Noetheris must not infer hardware embedding quality locally.
Problem
External solver results need a first-class candidate replay artifact that records why a sample was accepted or rejected. The artifact must bind problem hash, compiled model hash, assignment domain, reported energy, solver metadata, and embedding metadata.
Acceptance Criteria
Boundary
Solver metadata is recorded as evidence supplied by the external tool. Noetheris must not infer hardware embedding quality locally.