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.

Not every important thing is ready to be placed. Some material matters — it has weight, it keeps recurring, it could change something — but it is not yet stable enough for a canonical home. 05_latent_ideas.txt is where that material lives safely. It is not a storage bin for scattered text. It is an anti-stall buffer: it keeps what matters visible without promoting it too early.

​
What it is

05_latent_ideas.txt keeps together what matters but has not yet found the right home. Ideas, sparks, tensions, risks, or useful notes can enter here when they have not yet become live work, a decision, parked material, or archive. It works as an anti-stall buffer: it keeps what matters visible without promoting it too early. Thanks to state, next step, and likely direction, the material here stays readable, recoverable, and absorbable. It also protects the project: routing errors are easier to correct than premature promotions.

​
Flow

Material in 05_latent_ideas.txt follows a progression from entry to exit:
  1. Spark enters as new — it has arrived but is not yet fully understood
  2. Still holds on re-reading → state moves to to review
  3. Direction tightens, destination becomes clearer → state rises to to absorb
  4. Exits toward the right container (03, 04, 08, 98, 99)
If a note keeps weighing on the project, try to say what kind of file it seems to be moving toward. If it stops being alive, move it out.

​
Allowed states

StateMeaning
newIt entered here but is not yet fully understood
to reviewYou know it matters, but not yet enough to move it
to absorbAlmost ready to leave this file — destination is becoming clear
parkedNot being handled now; if it stays out of cycle, move it out of this file
deadNo longer matters as a live note; if you want to keep a trace, move it out of this file

​
What goes here

  • Strong ideas not yet closed — they matter but are not ready for another file yet; keeping them here buys time to clarify
  • Short sparks you do not want to lose — still small but may become useful; collecting them here gives continuity
  • Still-ambiguous nodes — not yet clear enough to move elsewhere; keeping them visible prevents dispersion
  • Useful pieces already known to matter, but without a clear home — 05 exists to hold what weighs on the project without forcing it anywhere
  • Things weighing on the project but not yet clear enough to belong elsewhere — leave them here until they clarify rather than forcing a destination

​
Spark template

Use the spark form for a short trace, a small intuition, or a light grip point. A spark can still be useful even if it is not yet a strong thesis. 
[SPARK]
[short label]
- id: L-xx
- Title:
- Origin:
- Why It Matters:
- Possible Destination:
- Likely Direction:
- State:
- links to:
- external reference:
- Next Step:
- Reopening Trigger:

​
Idea template

Use the idea form when there is already a stronger thesis or a more complete shape. An idea in 05 is not yet a decision — it is something serious that still needs to be clarified, stress-tested, or moved into the right file. 
[IDEA]
[short label]
- id: L-xx
- Title:
- Thesis:
- Why It Is Strong:
- Where It Touches the Project:
- What Is Still Missing:
- Likely Direction:
- State:
- links to:
- external reference:
- If It Matures, Where It Would Go:
- Next Step:
- Reopening Trigger:

​
Entries zone

New latent entries must be inserted only inside the --- ENTRIES START --- and --- ENTRIES END --- marker zone. [TEMPLATE ONLY] in the entries zone is scaffold only and does not count as a live latent entry. Every entry should have at least one state and one next step. Local entries in 05 use only L-xx. Cross-file IDs (D-xx, F-xx, etc.) stay as references in links to, Origin, or body text — they do not become new local IDs here.

​
05 gravity

If an L-xx item repeatedly shows structural relevance — it keeps surfacing, keeps affecting decisions, keeps touching the same parts of the project — it may have gravity toward a specific canonical level. If the material seems to be moving toward a canonical home, state its strongest plausible destination: 01 (identity), 02 (freeze), 03 (live work), or 04 (decision).
Plausible levels 02 and 04 are high-sensitivity. An L-xx note with plausible gravity toward freeze or decision should expect human validation before any promotion. AI-suggested gravity is not authority until the user confirms it. Do not promote based on gravity alone.

​
What does NOT go here

  • Things already in live work → 03_master_working.txt — already part of the live present
  • Decisions already taken and in effect → 04_decision_log.txt — no longer open
  • Technical maps already closed enough → 08_surface_map.txt — repos, entrypoints, sensitive surfaces, minimal runbook, critical deps
  • Things out of cycle but still useful → 98_parking.txt — not weighing now but may matter later
  • History, discarded material, closed material, dead material → 99_archive.txt — no longer part of live work
  • Whole files dropped in without extraction — 05 is for readable notes, not undifferentiated masses; extract the relevant unit first

Build docs developers (and LLMs) love

Get started for freeTalk to us