A mode in Signal Rail is a permission boundary, not a descriptive label. It defines what the agent is allowed to do during the current session. Only one mode may be active at a time. When a mode changes, what is allowed changes with it. If a closed gate reopens during the task — a write is attempted from a read-only mode, or a structure-level touch is initiated without structure mode — stop treating execution as valid and re-enter through the recovery path before continuing.Documentation Index
Fetch the complete documentation index at: https://mintlify.com/xxyoudeadpunkxx/signal-rail/llms.txt
Use this file to discover all available pages before exploring further.
Mode Reference
| Mode | What it allows | What it does NOT allow |
|---|---|---|
orientation | Reading, minimum read completion, source comparison, uncertainty declaration, frame closure, task clarification | Writing, promotion, structural touches |
reference | Reading specific canonical files in scope | Writing or rewriting |
review | Comparing material, identifying conflicts, surfacing risks | Writing, canonical updates |
ingest | Extracting and classifying units from sources | Writing to 01, 02, or 06; promotion without destination closure |
work | Extracting, classifying, proposing destinations, writing to clear destinations | Touching 01, 02, or 06 without structure mode |
structure | Touching 01_orientation.txt, 02_protocol_freeze.txt, or 06_ai_to_ai.txt | Must be explicitly opened; crossing from another mode requires stop-and-ask |
Default Startup State
Every session starts in orientation mode. Orientation is read-only. Reading does not authorize action. Understanding does not authorize writing. The agent may complete the minimum read, compare sources, declare uncertainty, close the working frame, and clarify the task — nothing more until the mode is explicitly moved.Structure Mode
Structure mode must be explicitly opened. It does not carry over from a previous session or inherit from work mode. Crossing into structure mode mid-task requires a deliberate stop-and-ask, not an internal mode shift. The agent may not assume structure mode is valid because the task seems to require it.The Move Order
The operating procedure in06_ai_to_ai.txt defines a fixed sequence. Steps must be followed in order. Later steps do not authorize skipping earlier ones.
Minimum read
Complete the minimum read before substantive action:
01_orientation.txt, 03_master_working.txt, and any conditional files triggered by the task.Identify source authority
When multiple sources are in scope, identify which carries governing authority for the touched level.
Clarify task
Before extracting or writing, confirm what the task actually requires. Do not infer scope from task volume.
Propose destination
For each classified unit, propose a canonical destination. Do not promote until the destination is clear enough.
Operations Vocabulary
The following named operations come directly from06_ai_to_ai.txt. Each carries a specific meaning in the protocol.
| Operation | Meaning |
|---|---|
read 06_ai_to_ai.txt | Activate the protocol; does not authorize bootstrap or writing |
preserve | Save without losing the right context |
read and rework | Read the material and absorb it into the right canonical container |
absorb | Move content from latent or scattered into one of the live canonical files |
park | Move useful but inactive material to 98_parking.txt |
archive | Move historical or closed material to 99_archive.txt |
unearth | Review entries in 05_latent_ideas.txt and choose: absorb, park, or leave alive |
Stop-and-Ask Conditions
When the agent must stop and ask before continuing
When the agent must stop and ask before continuing
The following conditions all require stopping immediately and asking for clarification before taking any further action:
- Host project is unclear
- Current working object is unclear
- Touched level is unclear
- Mode is unclear
- Authority is unclear
- Scope is unclear
- Live source is unclear
- The append-driven entries contract is unclear on a touched canonical file
- Classification could change meaning or continuity
- Promotion could change structure, authority, or current live state
- Canonicals conflict with each other
- Canonicals conflict with implementation
- More than one valid reading remains after review