Slice

Definition & Purpose

A Screen describes a permanent node in the product model. A Slice describes the specific feature, story, user journey, or technical task scope you are currently discussing, handing off, or testing.

Slice Schema & Types

Slices specify cross-cutting scope without duplicating screen nodes:

• name (string, REQUIRED) — Story or feature title.
• type (string) — Recommended values: story, journey, task, technical, analysis.
• actor (string) — Primary initiating actor ID.
• screens (array) — List of anchored screen IDs relevant to the slice.
• acceptance (array) — Short natural-language criteria or address coverage references.

Address Syntax & Examples

Slice addresses use the slices top-level namespace:

1Address format:
2slices.slice_id
3
4Real-world domain address examples:
5- slices.cancellation_flow
6- slices.payment_failure_recovery
7- slices.user_onboarding_journey

Slice Architecture Diagram

Complete Valid Example

Here is a complete Slice specification for payment recovery:

1slices:
2  cancellation_flow:
3    name: Self-Serve Cancellation & Retention Journey
4    type: story
5    actor: customer
6    screens:
7      - billing
8      - cancellation_review
9    acceptance:
10      - Workspace owner can trigger cancel_subscription from billing.
11      - System presents cancellation_review modal with retention offer.
12      - Finalizing cancellation sets billing state to cancelled.
13      - Accepting retention offer returns user to billing in active state.

What a Slice Does NOT Mean

A Slice is NOT a Redux slice file, NOT a separate application module, and NOT a replacement for the core screen graph. It is an optional cross-cutting requirement lens.