Forge: typed function to governed build — 28-second product walkthrough

00:00–00:05 — Open the native Forge library in Meridian Logistics with the complete default platform sidebar. The logistics-tender-guard package contains evaluateTenderReadiness. Version 0.4.0 is released and has no activation yet.

00:05–00:10 — Inspect the native function contract. The input contains a typed Shipment record reference, observation time, telemetry, compliance evidence and policy references. The output contains a readiness decision, reason codes, evidence references and policy references. The missing-approval example returns blocked with compliance_approval_required.

00:10–00:15 — Open completed Build Results. Approved, Stale telemetry and Missing approval all match their expected outcomes: three passed, zero failed, zero skipped. A passing blocked case means the guard returned the expected hold.

00:15–00:20 — Inspect the immutable 0.4.0 package artifact, its SHA-256 digest, applied source snapshot and the three retained test references. Release and activation are distinct states.

00:20–00:22 — Operations engineering has requested activation of this exact package and plan. Maya Chen reviews its scope and chooses Approve exact plan. The approval is separate from application.

00:22–00:24 — Choose Apply approved activation. Version 0.4.0 becomes active for the Workflow and Ontology action previews in Meridian Logistics. The function evaluates supplied context without tendering a shipment.

00:24–00:28 — Release and usage shows active version 0.4.0. The Port tendering Workflow draft and Evaluate tender readiness draft Shipment action both use evaluateTenderReadiness 0.4.0. The active Port tendering process remains v12, while proposed v13 still awaits review.