# Public report contract

## Purpose

The public report contract defines what a reviewer should be able to inspect. It describes report structure and provenance without publishing the proprietary numeric method.

## Report level fields

- Report identifier and creation time.
- Product and method version identifiers.
- Role and interview identifiers.
- Input completeness and transcript quality status.
- Configured role criteria summary.
- Question coverage summary.
- Role-specific alignment score when the configured evaluation requirements are met.
- Evidence findings.
- Observable work reasoning summary.
- Evidence gaps and explicit contradictions.
- Interview-integrity flags when supported by usable source material, with a source reference and a follow-up for human review.
- Human review status.
- Responsible use notice.

## Reading the alignment score

The comprehensive alignment score summarizes interview evidence against the configured job requirements. Review it together with the supporting evidence, question coverage, contradictions, and gaps. Incomplete or unusable evidence must remain visible rather than becoming an invented score. The score supports the final human decision; it does not make that decision. The public contract does not publish a numeric scale or calculation.

## Criterion finding fields

Each material criterion finding should include:

- Criterion identifier and public description.
- Source question identifier.
- Answer opportunity state.
- Support state.
- Evidence source reference.
- Ownership state when relevant.
- Missing evidence note when relevant.
- Contradiction note when relevant.
- Reviewer action and review status.

## Provenance requirements

A report should make clear which inputs were supplied, which version processed them, and which source supports each material finding. The report should preserve uncertainty when a source is incomplete or attribution is unclear.

## Human review states

- **Pending review:** no qualified reviewer has completed the review.
- **Reviewed:** a qualified reviewer has inspected the report and source evidence.
- **Returned for correction:** the reviewer identified a configuration, source, attribution, or interpretation problem.
- **More evidence requested:** the supplied interview does not establish one or more material criteria.
- **Excluded from decision:** the reviewer determined that a finding or source should not be used.

## What a report should not imply

A report should not imply that every job capability was tested, that a transcript reveals a complete person, that a numeric result is objective without context, or that the product made the employment decision.

## Public schema boundary

The public JSON contract describes field names and allowed descriptive states. It deliberately excludes formulas, weights, thresholds, score anchors, calibration logic, private prompts, internal harness instructions, hidden reasoning, candidate data, customer data, and production implementation details.

## Structured resource

See the [public report contract JSON](https://axiomcx.dev/data/report-contract.json).

The [synthetic report example](https://axiomcx.dev/data/synthetic-report-example.json) shows the public field relationships without a score, recommendation, real transcript, candidate record, or customer record. All public JSON resources follow the [public metadata schema](https://axiomcx.dev/data/public-knowledge.schema.json).