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.

The Signal Rail bootstrap is a two-file Windows utility that copies all canonical files from the baseline kit into a target directory of your choice. It handles directory creation, optional pre-fill of the project name and date, and safe overwrite prompting when an existing instance is detected — so you start with a clean, correctly structured instance without having to copy files by hand.

​
What the bootstrap does

Running the bootstrap copies all 17 canonical files into a target folder and performs two optional customizations:
  • Date pre-fill — writes today’s date into the - date: field in 03_master_working.txt automatically
  • Project name pre-fill — if you supply a name at the prompt, it is written into the - project name: field in both 01_orientation.txt and 03_master_working.txt
All other file contents are copied verbatim from the baseline kit.

​
Prerequisites

Before running the bootstrap, confirm both of the following are true:
  • init_signal_rail.bat and init_signal_rail.ps1 are in the same folder — the .bat file checks for the .ps1 file at startup and exits immediately if it is missing
  • PowerShell can execute scripts in your environment — the .bat file invokes PowerShell with -ExecutionPolicy Bypass, so per-machine restrictions are bypassed for this run without changing your system policy
No other dependencies are required.

​
Running the bootstrap

1

Launch the bat file

Double-click init_signal_rail.bat in File Explorer, or open a Command Prompt, navigate to the folder, and run:
init_signal_rail.bat
The console window opens with the SIGNAL RAIL BOOTSTRAP header and then waits for your input.
2

Paste the target directory

At the prompt:
Paste the target directory:
Enter the full path to the folder where the Signal Rail instance should be created. The folder does not need to exist — the script will create it. If you press Enter without typing anything, the operation is cancelled.
3

Enter an optional project name

At the next prompt:
Host project name (optional):
Type the name of the host project if you want it pre-filled, or press Enter to skip. If provided, the name is written into 01_orientation.txt and 03_master_working.txt.
4

The script copies the canonical files

PowerShell runs the bootstrap logic. Each canonical file is copied from the source folder to the target. After copying, the script applies any date or project name customizations, then reports the result — created, overwritten, skipped, and customized file lists.
5

Review the completion output and follow the recommended next steps

The console displays recommended next steps after a successful run. Review them before closing the window. The next section describes what they mean.

​
What the script copies

The bootstrap deploys exactly these 17 files: 
00_runtime_entry.txt
README.txt
AI_TO_AI__DEPLOYED_INSTANCE_SIGNAL_RAIL.txt
01_orientation.txt
02_protocol_freeze.txt
03_master_working.txt
04_decision_log.txt
05_latent_ideas.txt
06_ai_to_ai.txt
07_guided_prompts_test.txt
08_surface_map.txt
09_handoff_reentry.txt
97_field_findings.txt
98_parking.txt
99_archive.txt
init_signal_rail.bat
init_signal_rail.ps1
This includes the bootstrap scripts themselves, so the deployed instance can re-bootstrap from its own folder if needed.

​
Existing files behavior

If any canonical files are already present in the target directory, the script detects them before copying and asks: 
Existing Signal Rail files were found. Do you want to overwrite them? (yes/no)
  • no — all detected existing files are skipped. Only missing files are created.
  • yes — all canonical files are overwritten with the baseline versions. Customizations made after a previous bootstrap will be lost.
The script accepts only yes or no. Any other input causes the prompt to repeat.

​
Completion output

After a successful run, the script reports four categorized file lists and a set of recommended entry points: 
Signal Rail bootstrap completed in: <your target path>
Files created: <list>
Files overwritten: <list>
Files skipped: <list>
Files customized: <list>

Recommended initial bootstrap:
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.
Follow these steps before doing any substantive work in the instance. The entry sequence in steps 1 and 2 is not optional — reading 00_runtime_entry.txt first, then 06_ai_to_ai.txt, is the required path to a valid session opening.

​
Manual copy alternative

Manual copy is a valid alternative to the bootstrap. Copy the same 17 files listed above into your target folder using any file manager or shell command.
00_runtime_entry.txt
README.txt
AI_TO_AI__DEPLOYED_INSTANCE_SIGNAL_RAIL.txt
01_orientation.txt
02_protocol_freeze.txt
03_master_working.txt
04_decision_log.txt
05_latent_ideas.txt
06_ai_to_ai.txt
07_guided_prompts_test.txt
08_surface_map.txt
09_handoff_reentry.txt
97_field_findings.txt
98_parking.txt
99_archive.txt
init_signal_rail.bat
init_signal_rail.ps1
A manually copied instance is fully valid, but it must still preserve the required file names, marker structure, canonical roles, and entry flow. The bootstrap does not enforce behavior the manual copy does not — it only automates the copy step and applies date and project name pre-fills.

​
Localization

If you need a non-English instance, use the SR Localization Kit to create a separate localized copy before deploying. Do NOT localize the baseline kit in place. The baseline must remain clean so it can be reused to bootstrap future instances without carrying over localized content.

​
Safety rule

The script will refuse to run if the target directory you enter matches the folder containing the bootstrap scripts (the Signal Rail source folder). This prevents overwriting the baseline kit with itself. Always choose a different target folder — typically a subfolder of or sibling to the project you are governing.

Build docs developers (and LLMs) love

Get started for freeTalk to us