Lesson 3 of 6 · 0%Make recipient routing auditableNext
Course map

Channels, Messaging and Real-World Integrations

0 of 6 complete0 of 6

Lesson 3.1 · 55 minutes

Make recipient routing auditable

Express a routing decision as explicit policy over verified source, identity, classification, destination, and approval state.

Skip course map
Current lessonMake recipient routing auditable0% complete · 0/6 lessons

Channels, Messaging and Real-World Integrations

0% complete · Current: Make recipient routing auditable

Draft lesson: awaiting independent technical and publication review; do not use it as production configuration guidance.

Editorial review pendingon version support under review

Action boundary

Before you act

Expected result
A matrix decides deliver, hold, or drop for every known test route and defaults to drop.
Failure mode
A broad destination rule allows an approved draft to reach an unauthorised recipient.
Rollback
Disable the route, preserve the decision record, and narrow the destination rule before retesting.

Orient

Recipient safety is the course’s centre of gravity. A correct answer delivered to the wrong person is still a failure.

Perform

Create rows for source, verified sender, classification, destination, action, approval state, result, and audit event. Define the default row first: unrecognised source, sender, or destination means drop and log.

Lab scenarios

  1. An allowed test sender asks for an internal draft: hold for approval.
  2. An allowed sender targets a destination not in the matrix: drop and log.
  3. A recognised destination follows a classification that policy forbids: hold and escalate.

Check

A second person must be able to read one row and reproduce its decision without inferring intent from prose.

Continue

Lesson 4.1 makes every decision durable across retries.

Lesson checkpoint

Ready to move on?

Mark this lesson complete when you can apply its outcome without relying on the examples above.