Skip to content

Lantern, a worked example · Review page

Engineering ownership

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 6914e830beab · level L1 · scope examples/scheduling/**

1 slice in this snapshot (1 product, 0 technical). Behaviors with an owning slice: 1 of 1 behavior (links: a slice declares it in implements).

No architecture check supplied

Ownership on this page is as the slice records declare it. Nothing here checks the claims against the source files, imports or layers.

Slices

SLICE-ASMT-SCHEDULE: Student assessment scheduling slice

slice · kind product · status draft · owner team-assessment · domain assessment · examples/scheduling/SLICE-ASMT-SCHEDULE.md · its page

Claim kind Path pattern
source src/features/assessment/schedule/**
backend amplify/functions/schedule-assessment/**
Layer Path patterns
application src/features/assessment/schedule/domain/use-cases/**
external src/features/assessment/schedule/client/**
model src/features/assessment/schedule/domain/models/**
policy src/features/assessment/schedule/domain/policies/**
presentation src/features/assessment/schedule/ui/**

Behaviors without an owning slice

None: 1 of 1 behavior has an owning slice.

Shared resources

1 shared resource declared in the registries.

Resource Path Owner Declared consumers
RES-ASSESSMENT-DATA amplify/data/resource.ts team-platform SLICE-ASMT-SCHEDULE

Architecture check

No architecture check was supplied for this snapshot.