How Issues Work

An Issue is the smallest unit of progress in socra. Every Issue follows a lifecycle from creation through completion. When an Issue completes, its content is compiled into the parent Project’s memory.

The Issue Lifecycle

1. Created — The Issue exists with a title. Content and details can be filled in at any time.
2. In Progress — Work happens through content editing and timeline updates. Status moves through Plan, To Do, Working, and Review.
3. Completed — Status is set to Complete. Memory compilation triggers on the parent Project.
4. Archived/Deleted — The Issue is moved to trash or permanently deleted.

Status Reference

Status	Meaning
Plan	Not yet started, in planning phase
To Do	Ready to begin
Working	Actively in progress
Review	Waiting for review
Complete	Finished — triggers memory compilation
On Hold	Paused temporarily
Canceled	Will not be completed

Memory Compilation

When an Issue is marked Complete, your AI Teammate reads the Issue’s content and timeline, then compiles a summary into the parent Project’s memory. This means completed work is never lost — it feeds upward into the Project’s knowledge base.

If the parent Project is nested inside another Project, the compilation cascades upward through the hierarchy.

Issues in the Hierarchy

• Issues live inside Projects or directly under a Space.
• Move an Issue between Projects using ⌘⇧M or the context menu (right-click > Move to).
• Add dependencies between Issues with ⌘D. Dependencies track which Issues block or are blocked by other Issues.

Next Steps

• Create an Issue — Step-by-step guide to add a new Issue.
• Manage Issue Details — Set status, priority, and more.
• How Projects Work — How memory compiles upward through Projects.