Contributed Artifacts
Definition
Contributed Artifacts is the benchmark workspace for inspecting durable material produced through Expert Contributions. It organizes contributed Policies, Rubrics, Cases, and new coverage observations while preserving their relationship to the Contribution and expert work that produced them.
The view is a provenance and reconciliation surface. The final owner of a materialized artifact remains Correctness Governance, Assets, or Coverage Management according to artifact type.
Fields, states, or lifecycle rules
- Policy contributions represent expert-grounded behavior rules or revisions.
- Rubric contributions represent proposed or accepted evaluation criteria tied to specialist judgment.
- Case contributions represent situations supplied or corrected through expert work.
- Coverage observations identify missing, thin, conflicting, or newly important benchmark behavior.
- A coverage observation preserves its source, proposed facet applications, and application status so an operator can distinguish a recorded observation from one incorporated into coverage structure.
- Each artifact should remain traceable to the Contribution, expert, selected evidence, task responses, and checkpoints that support it.
- Contribution completion and artifact governance are separate transitions. Inspect the artifact's owning surface before treating it as active policy, active rubric, benchmark dataset membership, or resolved coverage.
- Reconciliation can accept, revise, route, or leave material unresolved according to the active workflow.
Interpreting contributed material
Use the artifact type to choose the next surface. A contributed policy or rubric belongs in Correctness Governance. A contributed case belongs in the project Assets pool before benchmark selection. A coverage observation belongs in Coverage Management and may motivate a Coverage Story, case construction, or another focused Contribution.
Preserve disagreements. Two experts can contribute conflicting Policy interpretations, and the artifact view should help an operator trace each interpretation rather than merge them into an invented consensus. Materialization should keep the Contribution, activity, checkpoint, expert, and scoped evidence links needed to explain why the artifact exists.
Worked example
Example: contribution provenance
An expert contributes a policy limiting compatibility claims, a rubric for explicit uncertainty, and a new case involving an unsupported adapter. The policy and rubric move to Correctness Governance for their lifecycle. The case enters Assets and is later selected into a benchmark dataset snapshot. All three retain the Contribution as their provenance.
Source confidence
Code-backed: the active Contributed Artifacts workspace exposes policy, rubric, case, and new-coverage groupings. This page preserves the separation between contribution provenance and the lifecycle of each owning artifact.