Skip to content

How Socras Work

Socras are where work lives in socra. Most work gets lost in conversation - Socras give it a shape: an owner, a status, and a record. Create one for anything that needs to happen - a task, a bug, a request, a decision - and track it from start to finish. When you mark one Complete, your AI Teammate compiles the work into the parent Journey’s memory so nothing gets lost.

  1. Created — The Socra exists with a title. Add content and details at any time.
  2. In Progress — Edit the content and post to the timeline. Set the status to Plan, To Do, Working, or Review to reflect where the work stands.
  3. Completed — Set the status to Complete. Memory compilation triggers on the parent Journey.
  4. Canceled — Set the status to Canceled. The Socra stays in place, marked as will not be completed. No memory compilation.
  5. Archived/Deleted — Move the Socra to trash, or permanently delete it.
StatusMeaning
PlanNot yet started, in planning phase
To DoReady to begin
WorkingActively in progress
ReviewWaiting for review
CompleteFinished — triggers memory compilation
On HoldPaused temporarily
CanceledWill not be completed

When you mark a Socra Complete, your AI Teammate reads the content and timeline, then compiles a summary into the parent Journey’s memory. This is how Journeys get smarter over time - completed work becomes context, not just history. The work feeds upward. Nothing gets lost.

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

  • Socras live inside Journeys or directly under a Space.
  • Move a Socra between Journeys: right-click it in the sidebar and select Move, or press ⌘⇧M while viewing the Socra.
  • Add dependencies between Socras by right-clicking the Socra and selecting Add Dependency, or by opening it from ⌘K while viewing the Socra. Dependencies track which Socras block or are blocked by other Socras.