Work units

This hub links the records SASE uses to plan, track, review, and settle work.

Beads

• Beads — identities, types, and the data model.
• Bead lifecycles — status, flag, and claim transitions.
• Bead triage — dependencies, follow-up, snoozes, and corroboration.
• Bead mirroring — external issue mirroring.
• Bead artifacts — artifact references on beads.
• Bead attachments — attachment storage and visibility.
• Bead storage — the store, event log, and checkout source of truth.
• Bead pages — generated bead pages.
• Bead CLI — command group overview.
• Bead CLI records — commands that create and change beads.
• Bead CLI queries — list, search, and maintenance commands.
• Reading beads — note, read, and show commands.
• Starting bead work — the sase bead work command.
• Bead TUI integration — plan links and task surfaces.

Plans

• Plans — SDD storage, artifacts, and plan lifecycle.
• Plan format — frontmatter, validation, and decisions.
• Plan commands — CLI and bead integration.
• Plan configuration — configuration and workspace behavior.

Other work records

• Goals — person-owned outcome records.
• Patches — review records for changes.
• ProjectSpec — project metadata and Patch records.
• Work tracking CLI workflows — how CLI work flows connect these records.

Related

• Reference

_[project]: A sase project is a named unit of work registered with SASE. _[workspace]: A sase workspace is a numbered clone of a project's primary repo, managed by the workspace store and tracked in that project's registry.json. _[agent]: A sase agent is an agent session or a single agent that does not belong to a session. _[prompt]: A prompt is the text SASE hands to a provider to start an agent turn. _[macro]: A macro is a reusable prompt triggered with #name in agent prompts. _[Patch]: A Patch is SASE's local unit of change. _[bead]: A bead is one tracked work item in SASE's git-native issue tracker. _[plan]: A plan is a persisted, approved artifact recording the intent behind agent work. _[TUI]: The TUI is SASE's terminal interface for running agents and reviewing results. _[epic]: An epic is an executable multi-phase plan run with sase bead work. _[gate]: A sase gate is a durable, command-backed request for one user decision, created when work must pause for the user. _[monitor]: A sase monitor is a monitor turn that runs one long command under a detached supervisor, so the command outlives the agent that started it. *[stitch]: A stitch is the lightweight ordered change record inside a Patch's STITCHES: section.