About — TriadicFrameworks Prompts
The Prompts system is the structured interface for working with RTT operator grammar, drift‑tensor analysis, coherence anchors, substrate‑tensor behavior, dimensional rails, domain traversal, and multi‑layer synthesis across the TriadicFrameworks ecosystem.
Prompts provide the canonical scaffolding for analysis, teaching, research, diagnostics,
and engine traversal.
They are the primary way users interact with RTT, IPD‑12, the S3 Spine, and the
TriadicFrameworks module architecture.
This page is the front door for understanding the Prompts subsystem.
Purpose of the Prompts System#
Prompts exist to:
- provide structured RTT‑aligned reasoning
- guide users through multi‑layer analysis
- support teaching and research workflows
- unify engines, stacks, modules, and overlays
- maintain drift‑tensor neutrality
- surface coherence anchors
- expose substrate‑tensor transitions
- traverse dimensional rails correctly
- maintain domain neutrality across the six canonical domains
- integrate with the S3 Spine Visualizer
Prompts are the connective tissue between all major TriadicFrameworks components.
What Prompts Are#
Prompts are:
- templates — reusable structured prompt grammars
- stacks — grouped families of related prompts
- modules — applied prompt collections
- engines — RTT and IPD‑12 prompt front‑doors
- UI flows — canonical sequences for teaching and analysis
- overlays — spine‑integrated visual layers
- diagnostics — compact multi‑signal analysis blocks
- worksheets — structured multi‑section analysis tools
- posters — large‑format RTT reference sheets
Prompts define how structure moves, aligns, diverges, or stabilizes across RTT layers.
Canonical RTT Structure#
All prompts follow the nine‑layer RTT structure:
- Identity
- Operators
- Drift
- Coherence
- Regime‑Points
- Substrate
- Dimensions
- Domains
- Synthesis
This structure governs:
- templates
- stacks
- modules
- engines
- worksheets
- posters
- teaching bundles
- diagnostics
Prompts Directory Structure#
/templates/#
Canonical prompt templates (Capture, Analyze, Drift, Coherence, Operator, Domain, Substrate, Teaching, Research).
/stacks/#
Structural groupings of prompt families (structural, diagnostic, operator, substrate, domain, teaching, research).
/ui/#
Unlock logic, dependency graphs, flows, wireframes, output formatting, overlays.
/modules/#
Applied prompt collections for domains, substrates, teaching, research, and examples.
/engines/#
RTT engines (RTT/1 → RTT∞) and IPD‑12 prompt front‑doors.
/examples/#
Example prompt usage across domains and substrates.
Integration with the S3 Spine#
Prompts integrate directly with the S3 Spine Visualizer:
- structural overlays
- drift‑tensor rails
- coherence anchors
- regime‑point basins
- substrate‑tensor transitions
- dimensional rails
- domain nodes
Prompts define how overlays behave and how the spine renders multi‑layer RTT structure.
Integration with RTT Engines#
Prompts are the primary interface for RTT engines:
- RTT/1 — structural identity
- RTT/2 — drift‑tensor
- RTT/3 — coherence anchors
- RTT/12 — regime‑points
- RTT∞ — substrate + dimensional rails
- IPD‑12 — substrate‑aware decision engine
Each engine uses prompts to expose its internal structure.
Integration with Modules#
Modules use prompts to:
- define module identity
- expose operators
- surface drift
- declare coherence
- analyze substrate behavior
- traverse dimensional rails
- evaluate domain alignment
- produce synthesis
Prompts are the backbone of module documentation.
Cross‑Links#
/docs/prompts/templates//docs/prompts/stacks//docs/prompts/ui//docs/prompts/modules//docs/prompts/engines//docs/prompts/examples//docs/spine/— S3 Spine Visualizer/docs/frameworks/ipd_12/— IPD‑12 engine/docs/rtt/— RTT engines
Manifest#
See module.json for the full registry of templates, stacks, engines, modules,
examples, overlays, and navigation structure.