Skip to content

Delivery

Delivery is the terminal phase of a work item's lifecycle in matic — the point at which execution outputs are normalized, validated, and published to their intended audience. Every delivery runs through mandatory validation (grounding, coverage, regression) and can be halted by baseline-violation gates that only a recorded HITL decision may release. The artifacts, previews, and validation records produced here become the persistent, git-native record of what shipped and why.

Produce Artifacts

Normalize raw execution outputs into the canonical produced content that previews, validation, and publication all consume. → produce-artifacts

Previews

Human-perceivable renderings of artifacts, generated during validation and surfaced at HITL checkpoints for reviewer decisions. → previews

Validation

Orchestrates the three mandatory checks — grounding, coverage, regression — along with probes, diff review, reviewer requests, and the validation record itself. → validation

Baseline Violation Gate

A hard delivery block triggered when a protected baseline regresses; non-retryable, releasable only by an explicit HITL decision record. → baseline-violation-gate

Partial Delivery

Authorized shipment of an incomplete work item when coverage_mode is partial and an intentional_floor_reduction decision is on record. → partial-delivery

Deliver Step

Post-validation publication: PR merges, deploys, notifications, and archival of the delivery record under the work item. → deliver-step