Signal Rail works because material is separated before it becomes noise. Rather than a single undifferentiated space where notes collide with decisions and live work accumulates beside closed history, Signal Rail gives every kind of material a named destination. That destination is determined not by convenience or proximity, but by the nature, stability, and authority of the content. The system spans thirteen files — each governing a distinct level of the project — so that the right question (“what kind of material is this, and where should it live?”) always has a clear answer.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.
The thirteen rails
| Rail | File | What belongs there |
|---|---|---|
| 🚪 Runtime Entry | 00_runtime_entry.txt | Valid entry, minimum read, and reading boundaries. |
| 🧭 Orientation | 01_orientation.txt | Project identity, perimeter, and reading frame. |
| 🧊 Freeze | 02_protocol_freeze.txt | Identity constants that should be hard to reopen. |
| 🔥 Master Working | 03_master_working.txt | Current live state, blocker, active work, and next move. |
| ⚖️ Decision Log | 04_decision_log.txt | Choices already taken, already in effect, and already won against alternatives. |
| 🌱 Latent Ideas | 05_latent_ideas.txt | Important unresolved material that still needs motion or placement. |
| 🧠 Lateral Kernel | 06_ai_to_ai.txt | Agent operating behavior inside a Signal Rail instance. |
| 🧰 Guided Prompts | 07_guided_prompts_test.txt | Guided paths for safer starts, rebuilds, reviews, and routing passes. |
| 🗺️ Surface Map | 08_surface_map.txt | Real technical topology, entrypoints, sensitive surfaces, and minimal runbook. |
| 🔁 Handoff | 09_handoff_reentry.txt | Re-entry support and continuity — not canonical project truth. |
| 🧲 Field Findings | 97_field_findings.txt | Lateral captures during an active pass before routing or discard. |
| 📌 Parking | 98_parking.txt | Useful material that is not active now. |
| 📦 Archive | 99_archive.txt | Closed, historical, duplicate, or no-longer-live material. |
How the rails relate
The thirteen rails fall into three broad groups. The canonical rails (01–05, 08–09) are the authoritative project surfaces — each governs one level and one level only, and no canonical overrides another. The kernel and guidance rails (00, 06, 07) govern how the system is entered and how an agent may operate within it. The lateral rails (97, 98, 99) hold material at various stages of exit: findings still being filtered, useful paths not currently active, and closed history preserved as trace.Reading does not authorize writing. Understanding does not authorize promotion. Entry validity is closed in
00_runtime_entry.txt before any other rail becomes operative.Individual rail pages
Runtime Entry (00)
The entry gate. Governs valid entry, minimum read, false entrypoints, and recovery states.
Orientation (01)
Project identity and reading frame. What the project is, why it exists, and what it accepts.
Protocol Freeze (02)
Hard-to-reopen identity constants. Up to five F-xx entries that define the project’s core.
Master Working (03)
Current live state. Objective, blocker, work in progress, open questions, and next move.
Decision Log (04)
Already-won decisions. D-xx entries recording what beat what and when to reopen.
Latent Ideas (05)
Live unresolved material. The anti-stall buffer for ideas that matter but aren’t ready yet.
Surface Map (08)
Technical topology. Real entrypoints, sensitive surfaces, and the minimal runbook.
Handoff & Re-entry (09)
Session continuity. Snapshots, delta views, and re-entry cards between sessions.
Lateral Files (97 / 98 / 99)
Field findings, parking, and archive — the three lateral support rails.
File Map Reference
Full canonical reference for all Signal Rail files, IDs, and marker contracts.