How do I keep Modules current as my systems change?

Most Module updates can come from the work you already do with your agents. When you explain a changed decision or correct an agent, the agent can find the existing Module and propose an update.

A Module records what should be true and why. The repository and running system provide evidence of the current implementation. Before acting, the agent should flash the relevant Module and inspect that evidence.

When they differ, decide what needs correction:

• If the Module still describes your intended direction, keep it and correct the implementation.
• If your direction changed, approve an exact Module update. Then check the affected systems against the new version.
• If the work exposes missing knowledge that will matter again, add it to the narrowest Module that owns the subject.

An agent can draft changes to the content and dependencies. It shows you the current text and the proposed text before saving anything. The Module owner can approve, revise, or reject the proposal. You can also update Modules directly at cortex.socra.com or with the Socra CLI.

Cortex creates an immutable version each time Module content or dependencies change. A new flash returns the current active version of every Module in the dependency tree. Flash history records which versions Cortex delivered to the agent.

A flash is a snapshot. Cortex does not replace knowledge already loaded into an active agent session. If a Module changes after an agent flashed it, have the agent flash it again before continuing.

Cortex does not continuously scan your repositories or decide that a Module is stale. Give your agents a standing instruction to surface lasting knowledge when they encounter it and propose the exact Module change. If a system changes outside those agents, include the related Module in the review for that change.

When a Module no longer applies, archive it. Cortex preserves its content and history. It blocks the archive while active Modules or Issues still depend on it, or while an enabled Issue Schedule uses it. An archived Module leaves the active knowledge graph and cannot be flashed until it is restored.