Package the Runtime and Its Trust Boundaries

The curriculum

1. Turn a Request into a Delivery Contract — Free preview

   Define permitted actions, exclusions and evidence for a successful release.

2. Build an API Contract That Can Fail Clearly — Free preview

   Make validation, error responses and retry expectations explicit before connecting a model or an external ticket system.

3. Package the Runtime and Its Trust Boundaries — Sign-in access

   Keep configuration reproducible, secrets out of artifacts and cloud permissions narrower than the service's code surface.

4. Retrieve Only Evidence the Requester May Read — Sign-in access

   Filter evidence before selection and cite only authorized material.

5. Make Approval a Durable State, Not a Button — Free preview

   Bind a review decision to an exact draft revision and reject stale actions after edits or concurrent changes.

6. Bridge Identity and Legacy Systems Without Borrowing Trust — Sign-in access

   Translate older system formats through a narrow adapter while keeping identity, access and status semantics explicit.

7. Measure the Service and Rehearse Recovery — Sign-in access

   Define meaningful success metrics, inspect tail latency and create a failure drill that produces a usable operator handoff.

8. Assemble Relay Room and Defend the Release — Sign-in access

   Integrate the course boundaries into a local portfolio project and present evidence without overstating production readiness.