Bead artifacts¶
This page describes artifact references attached to bead records.
Artifact References¶
Every bead can carry a refs list: an ordered, deduplicated set of canonical artifact
references. This is distinct from design. design points to the one plan that
produced the bead; refs can point to many supporting artifacts such as research
reports, explicit files, related beads, agents, Patches, stitches, or configured
document roles.
Reference entries are stored without the prompt-time @ sigil:
research:202607/artifact_capture_and_retention/artifact_capture_and_retention.md
file:default:0123456789abcdef01234567
bead:<bead-id>
Write commands parse and normalize references before storing them, deduplicate repeated
entries while preserving first-write order, and do not require the reference to resolve
on the current machine. That matches the durable, cross-machine purpose of the field: a
reference may be valid even when this checkout does not have the sidecar, artifact row,
or agent history needed to resolve it locally. sase bead doctor performs the
resolution audit and reports references with unknown namespaces, missing targets, or
ambiguous targets.
Use typed artifact links, not free-text RELATED: notes, when one bead should carry
relationship context to another:
sase artifact link add bead:<task-id> related bead:<other-bead-id> "<why>"
Use sase bead dep add only when the relationship blocks work scheduling.
Related¶
_[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.