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.

At the start of every session, two files must be read: 01_orientation.txt gives the identity frame, and 03_master_working.txt gives the live operational picture. This second file is where the project actually lives in the present — its current goal, what is blocking it, what is in motion, and what the next sensible move is. If it is out of date, the session starts from a false position.

​
What it is

03_master_working.txt holds the current live state of the project. It is one of the two mandatory reads every session, alongside 01_orientation.txt. Together they provide the minimum frame: what the project is, and where it stands now. Read 03_master_working.txt as the live layer of the project: what is already in motion and already shaping current work. It does not hold history, proposals, or ideas — it holds only what is true now.

​
What goes here

Each item belongs here because it describes the current, operational state of the project.
  • Current objective — the guiding sentence of the moment; keeps work oriented rather than dispersed
  • Dominant blocker — not every problem, but the one node that is really slowing the project now
  • Live view — where the project is now, in a few dense but readable lines; provides continuity between sessions
  • Work in progress — only lines of work that are actually active and already guiding the project
  • Open items that matter now — only what is about to enter the work or what is blocking the present
  • Real open questions — questions that have real impact; a real open question can change direction, product, or continuity
  • Active risks — only live risks, not abstract fears; shows where the project can deform, slow down, or break
  • Next concrete move — one clear, sensible next action; better than an elegant but fake plan

​
What does NOT go here

The following material does not belong in 03_master_working.txt and should be routed to its correct file:
  • Stable project identity → 01_orientation.txt — describes the project in a durable way, not its present
  • Hard-to-reopen constants → 02_protocol_freeze.txt — belongs to what you do not want to reopen easily
  • Decisions already taken and in effect → 04_decision_log.txt — records what has already won
  • Strong proposals not yet in live work → 05_latent_ideas.txt — not yet part of the current live state
  • Technical maps → 08_surface_map.txt — repos, entrypoints, sensitive surfaces, minimal runbook, critical deps
  • Full history of what happened — 03 is not an archive or a chronicle
  • Infinite backlog or session diary — widens the file without helping read the present

​
File sections

The name of the project this file serves. Closes which project’s live state is being described.
The date of the last substantial update. This is for reading freshness, not for building a full timeline.
One sentence: what the project is trying to achieve now. It should orient work without going too deep into detail.
The node that is really slowing the project now. Not a list of every difficulty — the one that weighs the most today.
Where the project is now in a few dense but readable lines. A line already in use may appear here even if it has not yet become a recorded decision. If you are listing already-closed decisions, you are probably writing in the wrong file.
Only the lines of work that are actually active. If a line no longer has real energy, it should not stay here. If something stops being only an idea and starts guiding the work, it may appear here.
Only what is about to enter the work or what is blocking the present. Do not turn this section into a second notes file.
Questions or openings that have real impact. A real open question can change direction, grammar, product, or continuity. Rhetorical or decorative questions do not belong here.
Only live risks, not abstract fears. This section should show where the project can deform, slow down, or break if no action is taken.
The next concrete and sensible move. One clear move is better than an elegant but fake plan.

​
Session close hygiene

If a session changes the project in a substantial way, update 03_master_working.txt before closing. At minimum, realign these five sections:
  1. Current State — does it still reflect where the project actually is?
  2. Work In Progress — are the active lines still the same?
  3. Real Open Questions — have any been answered or changed?
  4. Active Risks — are the risks still the same or has the balance shifted?
  5. Next Step — is the next move still correct, or did the session change it?
If during the session a choice has already clearly won against a real alternative, update 04_decision_log.txt too.

​
Live anchor hygiene

  • Section titles in 03_master_working.txt are operational anchors for reading, timeline, and maintenance — keep them stable
  • References to D-xx in links to must point only to real decisions
  • Open slots are acceptable while the file is still template-like; once 03 is truly live, empty slots should not remain its normal form
  • Use external reference for useful files or material outside the canonical set; do not widen links to

​
Typical errors

  • Using it as an infinite diary — 03 describes the live present, not everything that has ever happened
  • Treating it as a disguised decision log — decisions belong in 04_decision_log.txt
  • Filling it with vague lines — if a line does not help someone understand the real moment, it should not be here
  • Putting strong ideas here that have not truly entered the work — that belongs in 05_latent_ideas.txt
  • Pretending a line is live just because it feels like the right next move — a line enters 03 when it is already guiding current work, not when it is a promising direction

Build docs developers (and LLMs) love

Get started for freeTalk to us