Skip to main content

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.

Getting Signal Rail running takes two steps: creating an instance in the directory you want to govern, and opening a session with a correct entry path. There are two ways to create the instance — a Windows bootstrap script that handles everything automatically, or a manual copy if you prefer full control. Either way, the session entry sequence is the same.

​
Two ways to create an instance

Windows bootstrap

Run init_signal_rail.bat to scaffold a full instance with auto-patching for date and project name.

Manual copy

Copy the canonical files yourself. The copied instance must preserve file names, marker structure, and entry flow.

​
Windows bootstrap

The init_signal_rail.bat launcher is the fastest way to create a Signal Rail instance. It prompts for a target directory and an optional project name, then delegates the real bootstrap logic to init_signal_rail.ps1.
1

Run the launcher

Open a Command Prompt window in the Signal Rail source folder and run:
init_signal_rail.bat
The launcher prints the bootstrap title and checks that init_signal_rail.ps1 is present before continuing.
2

Enter the target directory

When prompted, paste the full path to the directory where you want the instance created:
Paste the target directory: C:\Projects\my-project\signal-rail
The target must not be the Signal Rail source folder itself. The script will refuse to overwrite its own source.
3

Enter a project name (optional)

When prompted, type the host project name, or press Enter to skip:
Host project name (optional): My Project
If provided, the project name will be auto-patched into both 03_master_working.txt and 01_orientation.txt (see auto-patching below).
4

Confirm any existing files

If Signal Rail files already exist in the target directory, the script asks whether to overwrite them:
Existing Signal Rail files were found. Do you want to overwrite them? (yes/no)
Entering no skips all existing files and creates only the ones that are missing.
5

Bootstrap completes

The script copies all canonical files and reports what was created, overwritten, skipped, or customized. A summary of recommended next steps is printed to the console.

​
The 17 canonical files

init_signal_rail.ps1 copies exactly 17 files into the target directory:
FileRole
00_runtime_entry.txtRuntime entry manual — valid entry and minimum read
README.txtHuman-readable overview of the instance
AI_TO_AI__DEPLOYED_INSTANCE_SIGNAL_RAIL.txtInstance marker file
01_orientation.txtProject identity, perimeter, and reading frame
02_protocol_freeze.txtHard-to-reopen identity constants
03_master_working.txtCurrent live state, blocker, and next move
04_decision_log.txtAlready-won decisions already in effect
05_latent_ideas.txtLive but unresolved material
06_ai_to_ai.txtLateral kernel — agent operating behavior
07_guided_prompts_test.txtGuided paths for safer starts, rebuilds, and routing
08_surface_map.txtTechnical topology, entrypoints, and sensitive surfaces
09_handoff_reentry.txtRe-entry support and continuity
97_field_findings.txtLateral capture during an active pass
98_parking.txtUseful but not active material
99_archive.txtClosed, historical, or no-longer-live material
init_signal_rail.batWindows bootstrap launcher
init_signal_rail.ps1Bootstrap logic script

​
Auto-patching

After copying the files, init_signal_rail.ps1 applies two automatic patches:
  • Date patch — today’s date in yyyy-MM-dd format is written into the - date: line of 03_master_working.txt.
  • Project name patch — if a project name was provided, it is written into the - project name: line of both 03_master_working.txt and 01_orientation.txt.
Auto-patching only occurs when the file was created or explicitly overwritten in the current run. Skipped files are not patched.

​
First session startup

Once the instance exists, open an AI chat with access to the instance directory and follow the mandatory read order before any substantive action.
1

Read 00_runtime_entry.txt

This is the runtime entry manual. It governs valid entry and correct system reading. The agent must read this file before anything else.
Read 00_runtime_entry.txt
2

Read 06_ai_to_ai.txt

This activates the lateral kernel. The kernel governs how the agent reads, stops, asks, routes, and writes inside the instance.
Read 06_ai_to_ai.txt
Reading 06_ai_to_ai.txt activates the protocol. It does not authorize bootstrap, classification, or writing on its own.
3

Read 01_orientation.txt

Orientation establishes the project identity, perimeter, and reading frame. The default startup mode is orientation, which is read-only.
Read 01_orientation.txt
4

Read 03_master_working.txt

The master working file holds the current live state of the project: where it is now, what is active, what is blocking it, and what the next move is.
Read 03_master_working.txt

​
Closing the minimum frame

After the mandatory read, the agent must close the minimum frame before any substantive action is allowed. The five items that must all be closed are:
Frame itemWhat it closes
Host projectThe real project being governed — not Signal Rail itself
Working objectThe specific thing being worked on this session
Active modeThe permission boundary for this session (orientation, review, work, etc.)
Source scopeWhich files or sources were explicitly indicated for this session
AuthorityWho can confirm freeze, live state, and source conflicts
If any of these is unclear, the agent stops and asks. It does not proceed by guessing.

​
Initial bootstrap actions

When the instance is brand new and the canonical files are still template-like, fill these two files first before treating the instance as live:
1

Fill 01_orientation.txt

Describe the host project — what it is, why it exists, its core direction, accepted trade-offs, and main boundaries. Do not describe Signal Rail here unless Signal Rail is itself the host project. Do not put current live work, decisions, or technical topology in this file.
2

Fill 03_master_working.txt

Write the current live state of the project: the dominant blocker, what is actively being worked on, and the next sensible move. Do not use this file for proposals, ideas, or decisions not yet in effect.
The 07_guided_prompts_test.txt file provides the New project bootstrap guided path for opening a blank or near-blank instance safely. Use it when you need the agent to ask the minimum questions before writing anything to canonicals.

​
Recommended next steps

After bootstrap, the console output from init_signal_rail.bat shows these recommended steps:
  1. Read 00_runtime_entry.txt first.
  2. Read 06_ai_to_ai.txt after entry is valid.
  3. Close host project, working object, and mode.
  4. Fill 01_orientation.txt and 03_master_working.txt first.
  5. Continue from the textual system and use the canonicals by level.
  6. Use 97_field_findings.txt only when you want to keep lateral findings readable before routing or discarding them.

Core Concepts

Understand rails, levels, authority, and the write gate before your first session.

Bootstrap overview

Compare the Windows installer and manual copy approaches in detail.

AI agent operation

How the agent reads, stops, routes, and writes under Signal Rail governance.

Guided prompts

Safer guided paths for bootstrap, source rebuild, and routing passes.

Build docs developers (and LLMs) love

Get started for freeTalk to us