---
title: "Issues and coordination"
canonical: https://workspace.socra.com/docs/cortex/concepts/issues-and-coordination
updated: 2026-10-13
---

# Issues and coordination

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

Modules state what is defined for the system; Issues reconcile code and other artifacts with it. If a design correction changes the shared requirement, the agent updates that knowledge and tracks the implementation work on an Issue. Saving the Module does not prove the code is fixed, and finishing the code does not keep the Module current by itself.

Agents can handle this coordination as part of the work you give them. You do not need to translate every correction into a Module edit and a task yourself. Their actions remain subject to your instructions, approvals and access permissions.

## 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.

Closing an Issue preserves its comments and state-change events. A principal with **Issue admin** capabilities can delete an Issue when no other Issue depends on it. Deletion also removes its comments and events; use `done` or `canceled` to retain the history.

## Dependencies

Issue dependencies describe execution order between units of work. They are separate from [Module dependencies](/docs/cortex/concepts/modules-and-map#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](/docs/cortex/concepts/flashing-context) 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](/docs/cortex/concepts/inbox) 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 and `list` to read the thread oldest-first. With comment permission, you can use `update` to edit your own comments. Editing another author’s comment or deleting any comment requires **Issue admin** capabilities. See [Access and permissions](/docs/cortex/administration/access-and-permissions#module-access).

## Attachments

Attachments are private files owned by an Issue. Follow [Issue attachments](/docs/cortex/guides/issue-attachments) to upload, download, place files in comments, or remove them.

## Labels

Labels classify Issues across Modules within an Account. [Issue labels](/docs/cortex/guides/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](/docs/cortex/guides/issue-schedules) to set a recurrence, control overlapping runs, and pause or remove a schedule.

The [Cortex CLI reference](/docs/cortex/reference/cli#work) lists the command groups for each coordination feature.