Signal Rail does not route by convenience. It routes by nature, stability, and authority. This discipline exists because the most common document failures are not caused by missing material — they are caused by material landing in the wrong level. A strong sentence becomes a decision. A live blocker becomes project identity. A temporary solution becomes freeze. A hypothesis enters current work before it has earned its place. Signal Rail prevents each of these by requiring the agent to close what a unit is before deciding where it belongs.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 Routing Order
Routing always follows the same three-step sequence. Later steps cannot be taken before earlier ones are closed.Close what the unit IS
Identify the nature of the material. Is it project identity? A hard constraint? A live working line? A taken decision? An unresolved idea? Technical topology? Continuity only?
Close how STABLE it is
Determine whether the material is settled enough to promote. Has it already won against a real alternative? Is it already guiding live work? Or is it still mobile and unresolved?
Level Destination Rules
| What the unit is | Destination |
|---|---|
| Project identity | 01_orientation.txt |
| Hard-to-reopen constant | 02_protocol_freeze.txt |
| Current live work | 03_master_working.txt |
| Already-won decision in effect | 04_decision_log.txt |
| Live unresolved material | 05_latent_ideas.txt |
| Technical topology / safe entry surface | 08_surface_map.txt |
| Continuity / restart support | 09_handoff_reentry.txt |
| Useful but not active | 98_parking.txt |
| Closed / historical | 99_archive.txt |
Non-Promotion Rules
Safe Hold
If material is still live but unresolved — it matters, but it has not earned a destination yet — hold it in05_latent_ideas.txt. It is better to delay routing than to force wrong promotion. 05 is not permanent archive. It is a governed holding space for material that is still in motion. Entries may be unearthed at any time and absorbed, parked, or left alive as the project evolves.
Classify Units, Not Files
Routing classifies internal units, not whole files. A single file can contain material with multiple different correct destinations. The agent must separate file role from content role before classification. If a working document contains both a live work line and a candidate freeze constant, those are two separate units that must be classified independently before either is promoted. Do not merge contents with different destinations into the same summary.What Signal Rail Prevents
| Failure Signal Rail blocks |
|---|
| A strong sentence becoming a decision |
| A live blocker becoming project identity |
| A temporary solution becoming freeze |
| A hypothesis entering current work too early |
| A handoff note becoming canonical truth |
| A technical map becoming orientation |
| A clean rewrite becoming less true than the messy source |
| A deployed instance being mistaken for the host project |
Convergence vs. Divergence
Every session must report whether the task converged or remained divergent. If converged: promote the material to the right file, or state explicitly why it still remains in05_latent_ideas.txt rather than being promoted.
If divergent: declare divergence, propose the Minimally Viable Path, and do not promote. If more than one valid path remains, do not force a route.
Before promoting any structurally strong unit, test one realistic failure condition. If that failure condition breaks the unit’s claim to the destination, do not promote. If no realistic failure condition breaks it, confidence in its strongest plausible level increases.
Host Canonical Files Describe the Host Project
In host canonical files (
01, 02, 03, 04, 05, 08), describe the host project by default — not Signal Rail. Mention Signal Rail only if it clarifies governance, current live work, or if the host project itself is Signal Rail.Core Concepts
Understand the canonical levels, authority model, and what keeps each rail distinct.
Latent Ideas Rail
Learn how
05_latent_ideas.txt holds live unresolved material safely until it is ready to route.