Think
Material begins in real work: a pressure point, a decision edge, a technical risk, a line that still does not know its final level.
Operational gesture
The system starts from movement, not from filing.
Throw
The material enters the system and is weighed, delayed, routed, promoted, or held without being forced into the wrong file too early.
Unearth
The right line can resurface from the right layer later, without manual reconstruction and without pretending memory is enough.
The agent is not corrected after the fact. It is routed before acting.
Workstation
An optional offline workstation for direct canonical work.
What it does
It gives the operator a direct local workstation for reading canonicals,
checking runtime state, staging writes, previewing output, and writing
back to the matching .txt files when live folder access is available.
What it does not change
It does not replace the canonicals or change their authority. It gives the operator a clearer local way to maintain a live instance without working blind.
Failure mode
Context collapse.
Signal Rail exists to prevent current work, won decisions, unresolved material, technical topology, and continuity from collapsing into the same documentary surface.
- live state mixed with decisions
- unresolved material promoted too early
- technical reality buried inside generic notes
- continuity pretending to be project truth
Mechanism
Context routing, not accumulation.
Core project truth
The parts that describe what the project is, what is active now, what has already been decided, and where the real technical body of the work lives.
Shared guidance
One layer helps the AI enter the system the right way. Another helps it stay consistent once work begins.
Support layer
Useful supporting surfaces for continuity, findings, parking, and archive without pretending to be the project's final truth.
Authority before convenience.
Architecture
Project material moves through different layers.
Structural truth
01 Orientation
02 Protocol Freeze
Operational flow
03 Master Working
08 Surface Map
Historical record
04 Decision Log
99 Archive
Latent buffer
05 Latent Ideas
98 Parking
Focus
Structural freeze
Identity constants: the lines the project should not casually lose, and the layer the agent treats as non-negotiable without explicit human authority.
Focus
Latent safe zone
Nothing dies. Nothing contaminates the present before it has earned its place there.
Kernel
A good entry, then steady behavior.
00_runtime_entry.txt helps the AI enter the system with the right reading frame.
06_ai_to_ai.txt helps it stay consistent once that entry is in place.
Each key file can also carry a short local guide for the AI inside its own structure.
Some surfaces hold the project's truth. Others stay useful without pretending to be that truth.
Protocol
How the system keeps the AI steady.
enter
validate entry
activate
close frame
read minimum
classify
write if clear
00_runtime_entry.txtfirst,06_ai_to_ai.txtafter entry is valid- one way of working at a time
- read enough before acting
- stop if the frame, meaning, or destination is still unclear
Support surfaces
Useful layers that do not pretend to be the project's truth.
Signal Rail does not force everything into the same kind of file. Some layers stay useful precisely because they do not claim more weight than they should.
09
Continuity
97
Field findings
98
Parking
99
Archive
Boundary model
Three surfaces, not one.
Baseline repository
The shipped system.
Deployed instance
The tool surface used inside real work.
Host project
The actual governed project.
Operational setup
Bootstrap and localization.
Bootstrap
Gets the system ready to use without pretending to decide what the project is, and now opens through 00_runtime_entry.txt before 06_ai_to_ai.txt.
Localization
Lets you create one personal language version without bending the structure of the system.