Editorial review pendingon version support under review
Action boundary
Before you act
- Expected result
- A test-only inventory names every actor, data class, recipient class, action, owner, and stop condition.
- Failure mode
- The team connects credentials before it can name the external side effect or its owner.
- Rollback
- Do not connect the channel; return the request to the owner with the missing decisions.
Orient
“Connect our chat” is not a requirement. It is an unbounded side effect waiting for a destination. Inventory the path first.
Perform
For one synthetic workflow, make a table with: source/provider, stable sender identity, message data class, intended recipient class, permitted action, approval requirement, retention owner, and disable owner. Mark any unknown as a stop condition.
Check
A reviewer should be able to answer: who can trigger this, what leaves the system, who receives it, and who can stop it? If any answer is “the integration,” the inventory fails.
Lab
Use a fictional request: “triage test support messages to a test team.” Identify one prohibited recipient class (for example, an external customer) and write the default-deny rule.
Continue
Only after the inventory is complete may you define provider identities and permissions in Lesson 2.1.
Lesson checkpoint
Ready to move on?
Mark this lesson complete when you can apply its outcome without relying on the examples above.