Skip to content

Lantern, a worked example · Record

ADR-ASMT-SEAM: Keep backend access behind the slice seam

An invented example

This Atlas is drawn from the records of an invented product, so it can be published to show what the Atlas shows. A team's own Atlas may contain internal and restricted records and stays inside the organization. The files are authoritative; these pages are a derived view of them.

Snapshot: commit unknown · graph hash 3b31c362b352 · level L1 · scope examples/scheduling/**

Records › Decisions › ADR-ASMT-SEAM

The record

examples/scheduling/ADR-ASMT-SEAM.md · View the file on GitHub

Field Value
ID ADR-ASMT-SEAM
Title Keep backend access behind the slice seam
Type decision
Status draft
Owner team-assessment
Visibility internal
Audiences engineering, product
Revision 1
Format spec 0.2 · profile intentset/decision/0.2

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.

Everything below is derived: the Atlas reads it from this record and the others, and none of it is written in the file.

Linked from other records

The links other records write to this one, read the other way (Core §5).