How do I Flash a Module for a task?

Ask your connected agent to Flash the narrowest Module(s) relevant to your task, or run socra cortex flash module-name in the CLI for each required Module. Flash returns that Module and every Dependency it needs, with prerequisites first and each Module included once. Read the complete result before acting.

Find the right Module

Use the Account that owns the knowledge. Flash a known target directly. Otherwise ask your agent to search by the task's subject. The CLI search command is:

socra cortex module search --query "your topic"

Use socra cortex map only when Search leaves subjects or relationships unclear.

Search and the map show the Modules you can discover directly. If a candidate's content or direct Dependencies are missing or outdated and needed to choose the target, retrieve them:

socra cortex module get module-name

Replace module-name with the selected name. Then Flash it:

socra cortex flash module-name

A successful CLI response includes the Flash ID, Module count, estimated token count, and assembled content. A connected MCP agent retrieves the same kind of context through its Cortex Flash tool. Opening a Module in the browser is useful for reading it, but does not by itself deliver its full context to another agent's conversation.

Understand what is included

If the selected Module depends on a security Module, and that Module depends on an Account rule, the result includes all three. It does not include other Modules merely because they depend on your selected Module.

Permission to Flash the requested Module includes the whole Dependency closure in that result. It does not grant direct access to edit or independently open those Dependencies. The map can therefore show less knowledge than an authorized Flash returns.

Flash is a recorded retrieval. It does not edit your repository, assign work, or replace your host's instructions. The agent must compare the Module's intended behavior with current implementation and other evidence relevant to the task.

Keep the result useful

Within a task, a successful Flash already supplies every Module in its result. Reuse a successful Flash while the required knowledge remains available in context. Retrieve missing knowledge again when needed. Refresh outdated knowledge before relying on it; Cortex does not replace text already delivered to an agent session.

If Cortex reports an archived Module or invalid dependency chain, ask the Module owner to resolve the reported knowledge problem. Do not remove a required Dependency merely to shorten the response or make the command succeed. If no relevant Module exists, use the task's other evidence.