Buildable artifact · stage 4

Specialist factory report card

A run directory that binds target, data, candidate, frozen evaluation, packaging evidence, resource measurements, and a terminal ship/retry/reject decision.

Readiness
runnable lab
Kind
decision artifact
Workload
metadata lifecycle is light; model evaluation may require approval
Stage
Build the ruler

Artifact contract

A run directory that binds target, data, candidate, frozen evaluation, packaging evidence, resource measurements, and a terminal ship/retry/reject decision.

This decision artifact is classified as runnable lab. Workload guidance: metadata lifecycle is light; model evaluation may require approval.

Build

Create a factory run and populate its declared evidence contract.

Modify

Version targets, gates, and policies without rewriting completed evidence.

Tune

Change thresholds only before the candidate is scored, with rationale recorded.

Prove

Run the same frozen evaluator on baseline and candidate, including regression slices.

Package

Compile the complete run into a public before/after report and terminal decision.

CLI surface

  • Run: posttrainllm factory-run
  • Run: posttrainllm eval-gate
  • Run: posttrainllm eval-compare

How to read this dossier

This canonical page separates the retained repository decision from the material that informed it. A source may describe an external claim, historical measurement, local observation, or planned procedure; those evidence classes are not interchangeable. Follow the provenance links before reusing a number or method.

Status and disposition describe what PostTrainLLM retained when this record was indexed. They are not a live product promise, a newly run benchmark, or permission to restart historical work. Unknown or unmeasured fields remain unknown rather than being treated as zero.

To reuse the record, first name the exact claim you need and trace it to the linked source. Then check whether the original environment, model revision, data split, evaluator, hardware, and budget match the proposed use. If they do not, treat the record as a hypothesis or design reference and run the smallest fresh comparison that can falsify it. Preserve negative outcomes and regressions beside any improvement; a local win on one slice does not silently become a general capability claim.

Source provenance

The normalized record comes from docs/learn/artifact-journey.json. The links below are the tracked evidence and explanatory sources preserved with the record.