Socra Cortex

Flash a context module: assemble its full transitive dependency tree into a single, ready-to-read context bundle. Use this before working in a domain to load everything the owners cemented about it.

Get a single context module by name — its content and direct dependencies, without walking the tree.

Map the whole knowledge basin: every context module and how it depends on the others, as one indented outline of names and one-line summaries (no full content). Call this FIRST when you do not yet know which module to flash — read the map, pick a node, then load it with context_flash.

Restore an archived context module atomically with optional replacement content and complete final dependencies. Omitted fields are preserved; an empty dependency list removes all links. The final closure must be active and acyclic. Validation failure changes nothing.

Search context modules by keyword (matches name and content). Returns matching modules; flash one with context_flash to load its full dependency tree.

Update a context module: replace its content, its dependency edges, and/or reassign its owner. Only the fields you provide change.

Verify a prepared upload and make the issue attachment visible.

Authorize an issue attachment and return a short-lived private download URL.

List every completed file owned by an issue, including its comment placements.

Prepare a private issue-file upload. Returns a short-lived PUT URL and required headers; upload the exact declared bytes, then call issue_attachment_complete.

Remove private attachment bytes while preserving its issue-history tombstone.

File a unit of work against the module it concerns. Work is always scoped to a module (the knowledge it touches).

Delete an issue by id. Refused if other issues still depend on it.

An issue's timeline of state changes (created, status changed, reassigned, …), oldest-first. Pass the issue id. Combine with comment_list to reconstruct the full activity timeline.

Get a single issue by id — its full description, status, assignee, dependencies, and embedded label summaries.

Your bench: released, unclosed work assigned to you, or untriaged in modules you own. Start here to find what to pick up.

List issues, optionally filtered by module, status (open|in_progress|done|canceled), assignee (an account-user id, user_… — not a name), or label id.

Update an issue: title, description, status, assignee, priority, work-dependency edges, or label ids. Only the fields you provide change. Assignee takes an account-user id (user_…), not a name — resolve names via the directory first.

Create an account-scoped issue label.

Delete an unused label. Refused while attached to any issue.

Get one label by its stable id.

List or search the account label registry.

Rename a label or change its display color.