Skip to content
Workspace
Docs

Issues and coordination

An Issue records a gap or task against the Module whose knowledge and ownership it affects.

Issue state

An open Issue can remain active until the work reaches a terminal state. Completed work uses done. Work that will not be completed uses canceled with a resolution comment.

Cortex preserves closed Issues as durable work history. Ordinary Issue operations do not erase the Issue, its comments, or its state-change events.

Dependencies

Issue dependencies describe execution order between units of work. They are separate from Module dependencies, which describe knowledge required for understanding.

Use Issue dependencies only when one Issue must complete before another can proceed. Do not use them only to express that two Issues concern the same initiative.

Timeline

The Issue timeline combines two records:

  • Immutable IssueEvents record state changes such as creation, assignment, and status changes.
  • Authored comments record decisions, evidence, progress, and resolution context.

This distinction preserves both what the system recorded and what collaborators explained.

Agent use

An agent reads an Issue to understand the requested work, then flashes the Issue's Module when the task requires that knowledge. Assignment does not preload Module content into the agent session.

Inbox

The Cortex inbox lists work released to the authenticated principal. Cortex inbox behavior explains routing, dependency checks, pagination, and watching changes.

Comments

Comments are authored progress updates on an Issue. Use socra cortex comment create to add one, list to read the thread oldest-first, and update or delete only for a comment you wrote.

Attachments

Attachments are private files owned by an Issue. Follow Issue attachments to upload, download, place files in comments, or remove them.

Labels

Labels classify Issues across Modules within an Account. Issue labels explains how to apply labels, filter work, and manage label names and colors.

Schedules

Issue schedules create ordinary Issues from a recurring template. Follow Issue schedules to set a recurrence, control overlapping runs, and pause or remove a schedule.

The Cortex CLI reference lists the command groups for each coordination feature.