# Who can approve or change a Module, and what happens when rules conflict?

Company: Socra — Multiply Your Judgment
Canonical URL: https://support.socra.com/articles/art_01m14qm90gmp2avcfpp398gp3p-module-approval-and-conflicts

Each Module has one owner. Only that owner approves the exact words that describe what should be true.

An agent can propose a change and show the owner the exact text before and after. The owner approves or rejects the proposal before the agent saves it.

You decide who else can change the Module:

- The owner always has full access.
- Editors can change the content and dependencies.
- Admins can make those changes, manage access, and transfer ownership.
- Commenters and viewers cannot change the Module.

Cortex checks these permissions when someone tries to make a change. Each saved change to the content, dependencies, or owner creates a new version. The history records who made the change and when.

## When a request conflicts with a Module

The agent surfaces the conflict and asks the owner to decide. The approved rule remains in force until the owner approves an exact change.

If the owner rejects the change, the agent follows the existing rule. Work that requires breaking the rule does not proceed.

## When Modules disagree

The disputed rule belongs to the Module that owns the exact subject. The owner of that Module decides what should be true.

A change that affects more than one Module requires approval from each owner for the text in their Module.

Dependencies control the order in which agents receive knowledge. Cortex provides foundational Modules before the selected Module. A dependency never changes who owns a rule.

## How exceptions work

An exception is a rule with a limited scope. The owner approves that scope and records the exception in the Module that owns the subject.

A one-off request does not change an approved rule. The existing rule applies until its owner approves the exception.

## What Cortex records

Cortex keeps every version of the Module. You can compare changes and restore earlier knowledge. Restoring a version creates a new version, so the history remains complete.

## Article details

- Collection: [Cortex](https://support.socra.com/collections/col_01kzpmz5q2hz8avw3tys0tnx4f-cortex)
- Published: 2026-08-28
- Updated: 2026-08-28
- Canonical: https://support.socra.com/articles/art_01m14qm90gmp2avcfpp398gp3p-module-approval-and-conflicts