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.