Intentset
Worked example · decision
| Field | Value |
|---|---|
| ID | ADR-ASMT-SEAM |
| Type | decision |
| Status | draft |
| Owner | team-assessment |
| Visibility | internal |
| Audiences | engineering, product |
Keep backend access behind the slice seam
Context
Frontend and backend resources may live in different directories while serving one product behavior.
Decision
The scheduling client adapts transport into domain results. The backend handler enforces authorization and rules; shared data composition has a technical owner.
Consequences
Ownership stays explicit without moving all cloud resources into a frontend feature. Imports and bundle contents require checking.