Reference and golden outputs
Definition
A golden or reference output is a Case-scoped example response available on supported review, mapping, or Snapshot surfaces. It can help a reviewer understand intended behavior for that Case, but it is not a global Policy, a saved Harness Version, or a generic customer approval state.
Use this reference only where the product explicitly exposes a golden or reference response. Do not rename every expert answer, reviewed response, or imported candidate output as an “accepted output.”
Fields, states, or lifecycle rules
- Keep the reference response attached to the Case and evidence context that justifies it.
- A candidate Run response does not become a reference response merely because it passed a Rubric.
- Reviewer comments and Contribution rationale remain attributable review input, not output state.
- A reference-output change can require a new Case, Snapshot, or Benchmark Version boundary when it affects governed interpretation.
- Policies and Rubrics remain the reusable correctness standard; a reference output illustrates one Case.
- This page does not define an export format or public output schema.
Related objects
Read reference outputs with Outputs, Cases, Correctness Governance, and Expert Contributions.
Worked example
Case-scoped reference response
A compatibility Case includes a reference response that says the available source does not confirm support and directs the user to an explicit compatibility check. The response illustrates desired behavior for that Case. The reusable requirement still belongs in the applicable Policy and Rubric.
Source confidence
Code-backed: output mapping, Snapshot artifacts, linked Policy Cases, and Contribution review surfaces expose golden or reference responses as Case-scoped evidence with explicit review or overwrite actions. The sources do not establish a universal accepted-output lifecycle.