How do I keep Modules current as my systems change?

Your connected agent can keep Modules current as your decisions change and its work reveals missing knowledge. With Cortex instructions and write access, it compares the saved intent with current evidence, updates useful knowledge, names the affected Modules, and tells you what changed and why. Cortex preserves saved versions; it does not continuously scan your systems and decide which knowledge is stale.

Decide what changed

Use the current knowledge in the Module that owns the subject and inspect the current implementation. Retrieve content or direct Dependencies before editing only when they are missing or outdated. If the Module still describes the behavior you want, keep that rule and record the work needed to meet it. If your direction changed, update the decision and its reason in that Module.

The suggested instructions let the agent save useful changes during its work. You can ask it to show you the proposed content and Dependencies for approval first. Follow the decision owner's requirements; ordinary edit permission does not record a separate human approval.

Preserve unique constraints and their reasons when reorganizing knowledge. A shorter Module is not an improvement if it loses a rule future work still needs. Keep progress, incidents, and temporary implementation status in work records.

Save the change

The agent can save the change for you. You can also use the Modules view at cortex.socra.com or the CLI yourself. For the CLI, first install the Cortex plugin and sign in to the intended Account. Place the intended content in module.md, use the Account that owns the Module, and replace module-name with its name:

socra cortex module update module-name --content-file module.md

Omitting --deps preserves the direct Dependencies. If you provide that option, it replaces the complete direct list. A successful save response confirms the change. If an update loses its response, read back before retrying.

A changed content or Dependency list creates a new version. You can inspect history and compare two versions:

socra cortex module version list module-name
socra cortex module version get module-name 1
socra cortex module version diff module-name 1 2

Use version numbers that actually exist in the returned history. An identical update need not create another version. To bring back an earlier rule, review that version's content and save an authorized new update; module restore instead reactivates an archived Module.

Refresh active work and retire unused knowledge

Cortex does not replace context already delivered to an agent. If required knowledge in the agent's context becomes outdated, retrieve the current knowledge before relying on it. Flash metadata records the versions delivered. Reopening an old Flash currently rebuilds the target's current knowledge and Dependencies. It can return newer content or fail after archival. Use Module version history to inspect the recorded versions; a reopened Flash is not an unchanged copy of the original result.

Archive a Module only when its knowledge should stop governing work. Active dependent Modules, open or in-progress Issues, and enabled Issue Schedules can prevent archival. Resolve those dependencies deliberately. Archiving preserves content and history and removes the Module from active Flash use; it does not erase prior copies or delete its knowledge.