Public Release - 2026-06-28

A public evidence system is only credible when every artifact has a visible QA state.

Artifact: full_public_evidence_qa_v1. This note defines a compact QA state for public artifacts, links, claims, boundaries, missing evidence, corrections, ownership, and next action.

artifact link_status claim_status boundary_status missing_evidence needs_correction owner next_action
Full Public Evidence QA v1 public evidence visual.

Artifact

QA is the public ledger of what is solid, what is narrow, and what still needs work.

This object does not certify complete replication or deployment readiness. It classifies the visible state of each public artifact so a reader can distinguish live links, supported claims, boundary statements, missing evidence, and correction needs.

A link can work while the claim still needs review.

Status

A link can work while the claim still needs review.

Link status, claim status, and boundary status are separate fields. A page can resolve correctly while its claim is pending, too broad, missing evidence, or waiting for correction. The QA object prevents those states from collapsing into a single green check.

The owner and next action make public QA operational.

Correction

The owner and next action make public QA operational.

A QA state is not useful if it only names a defect. The owner and next_action fields make the route inspectable: who is responsible for the artifact state, and what concrete change would move it forward.

1

artifact

The public object under QA: page, registry, paper, route, or note.

2

link_status

Whether the public link exists, resolves, and points to the intended object.

3

claim_status

Whether the claim is supported, narrowed, pending, or unsupported.

4

boundary_status

Whether the limits of the claim are explicit and current.

5

missing_evidence

The absent receipt, reproduction, comparison, dataset, or external check.

6

next_action

The next concrete action required to improve or correct the public artifact.