Module Format Specification
Module Format
Modules are markdown files containing AI assistant instructions.
File Format
Filename: module_name.md
Location: modules/core/ (global) or overrides/<org-id>/ (overrides)
Format: Markdown
Required Elements
- Title (H1 heading):
# Module Name - At least one paragraph of content
- Valid markdown syntax
Markdown Syntax
Headings:
# Title (H1)
## Section (H2)
### Subsection (H3)
Lists:
- Unordered item
- Another item
1. Ordered item
2. Next item
Emphasis:
*italic* or _italic_
**bold** or __bold__
Code:
Inline `code` with backticks
```python
# Code block
def example():
pass
**Links:**
```markdown
[Link text](https://example.com)
Module Structure
Basic template:
# Module Name
Introduction paragraph.
## Main Section
Instructions here.
## Guidelines
- Rule 1
- Rule 2
- Rule 3
## Examples
Good: Example behavior
Avoid: Behavior to avoid
Using Variables
Insert variables with {{variableName}}:
# Context
You assist {{organizationName}}.
Contact {{teamLead}} at {{escalationEmail}}.
Variables are replaced when constitution is built.
Module Order
Modules appear in constitutions in predefined order: 1. context 2. objective 3. tone 4. safety_rules 5. knowledge 6. examples 7. Custom modules (alphabetically)
Order cannot be changed per organization.
File Organization
modules/
├── core/ # Global modules
│ ├── context.md
│ ├── objective.md
│ └── tone.md
└── versions/ # Version snapshots
└── core/
├── context/
│ └── 20260207015207.md
└── tone/
└── 20260206185423.md
overrides/ # Organization overrides
├── acme-sales/
│ └── tone.md
└── acme-hr/
└── context.md
Last updated: February 2026