Own the business domain
Do not let provider/session identifiers become business truth.
Developer documentation
Map the journey before the API.
Define the tenant/workspace, business objective, participants, communication, authoritative systems, action and outcome before implementation.
Principles
Use controlled Product contracts and technical specifications for implementation detail.
Preserve correlation
Use execution identity for the business journey while keeping other identities distinct.
Keep policy explicit
Tenant, entitlement, acting capacity, consent and step authority are not interchangeable.
Design for failure
Retry, fallback, handoff and recovery should be bounded and observable.
Keep evidence classified
Observed data, calculated metric, inference, recommendation and approved action remain distinct.