Handbook
Prompt 34 — Physics batch release and merge auditor
Perform a read-only release audit.
Updated
Inputs
BATCHES: {{BATCHES_JSON}}
REPOSITORY_WRITE_PLAN: {{REPOSITORY_WRITE_PLAN_JSON}}
SCHEMA_AND_CI_RESULTS: {{SCHEMA_AND_CI_RESULTS_JSON}}
VALIDATION_FALSIFICATION_ONTOLOGY_RECEIPTS: {{VALIDATION_FALSIFICATION_ONTOLOGY_RECEIPTS_JSON}}
CONTAMINATION_AND_SAFETY_REPORTS: {{CONTAMINATION_AND_SAFETY_REPORTS_JSON}}
CURRENT_REGISTRY_SNAPSHOT: {{CURRENT_REGISTRY_SNAPSHOT_JSON}}
RELEASE_POLICY: {{RELEASE_POLICY_JSON}}
Task
Perform a read-only release audit.
Check:
- JSON, YAML, LMeta, contract, and schema validity;
- object and artifact-envelope identity, version, and provenance;
- quantity, unit, source, dependency, partition, and visibility registry closure;
- no direct generator promotion and no unapproved repository write;
- validation status supported by authenticated receipts;
- no unresolved blocker counterexample, contamination finding, unsafe detail, or duplicate collision;
- model regime and uncertainty completeness;
- train/held-out/intervention/replication separation;
- simulation reproducibility and convergence evidence where claimed;
- LMeta/LCDL semantic-execution parity;
- maturity and allowlist claims remain honest;
- session machine truth, token ledger, route trace, ambiguity, and freeze gate evidence;
- migration and rollback completeness.
Report blocking and conditional findings separately. Do not average away blockers. Decide release, conditional_release, hold, reject, or escalate.
Return only JSON matching schemas/release-report.schema.json.