Author a context module

Author a context module

A module is a persistent, named, versioned specification of what should be. Its content stays upstream from the code and other artifacts that consume it.

Find the owner first

Search before you propose a new module:

socra cortex module search --query "topic"
socra cortex map

Update the existing owner when one module already owns the concept. Create a new module when the concept has a distinct durable identity.

Write the specification

Keep the content abstract. State the interface, rules, constraints, and reasons that future work must honor. Leave implementation logs, file paths, incident history, and copied source code out.

Add a dependency when a reader must understand another module first. Dependencies form a directed comprehension graph. Cortex rejects cycles.

Get exact approval

Show the owner the exact proposed content and dependency changes. Wait for clear approval of that text before you write. Owners must understand every sentence in the modules they own.

After approval, create or update the module:

socra cortex module create --name example --content-file module.md --deps foundation
socra cortex module update example --content-file module.md --deps foundation

Read the result back and flash it to verify the full context:

socra cortex module get example
socra cortex flash example