Converge Assessment & Publish Report

Objective

Join all assessment branches, publish one complete supervisory verdict, and release the project assessment lock.

Required inputs

For the same run ID: Assessment Run Record, Variable Assessment Evidence, Ticket Action Record, Delivery Throughput Snapshot, and Required-Artifact Coverage Report.

Procedure

1. Verify every required input exists, validates, and uses the same run ID, Charter version, iteration ID, and snapshot boundary.
2. If any branch is missing, stale, schema-invalid, or has an unresolved side-effect error, mark the run incomplete; do not publish a success verdict or release an ambiguous partial report.
3. Create ITERATION_ASSESSMENT.md containing:
   - run/snapshot identity and input versions;
   - executive verdict: Green | Yellow | Orange | Red | Unknown;
   - per-variable prior/current band, evidence, ticket action, owner, and gating policy;
   - throughput and cycle-time findings;
   - artifact-coverage findings;
   - active observe | pause_new_work | block_release signals;
   - required next actions with owner and due/decision point;
   - errors, Unknowns, and confidence/provenance limitations.
4. Derive the overall verdict from declared Charter policy. Never average away a Red, Unknown, or gating signal.
5. Update RUN.md to complete with output checksums/links and end time; release the lock.
6. Notify the Delivery Manager and the RIN/MIN execution context through the destinations in the Huginn contract.

Completion evidence

The report is reproducible, internally consistent, complete for all branches, explicit about Unknowns and gates, linked to stable tickets, and the run record is complete with the lock released.