UI Flows — TriadicFrameworks Prompts
UI Flows define how users move through the TriadicFrameworks Prompts system.
They specify the canonical sequences for templates, stacks, engines, modules, teaching
bundles, diagnostics, and synthesis workflows.
Flows ensure that the Prompts UI behaves consistently across all engines, stacks, templates, and modules.
This page is the front door for all UI flow documentation.
Purpose#
UI Flows provide:
- Canonical sequencing for RTT workflows
- Navigation rules for templates, stacks, engines, and modules
- Teaching sequences for classroom and self‑study use
- Diagnostic flows for structural, drift, coherence, and substrate analysis
- Synthesis flows for multi‑layer alignment
- UI behavior that matches RTT operator grammar
Flows are the behavioral backbone of the Prompts UI.
Core Flow: RTT Canonical Sequence#
All RTT‑aligned flows follow the same nine‑layer sequence:
- Identity
- Operators
- Drift
- Coherence
- Regime‑Points
- Substrate
- Dimensions
- Domains
- Synthesis
This sequence governs:
- template usage
- stack traversal
- engine presentation
- module layout
- worksheet structure
- poster structure
- teaching bundles
Template Flow#
Templates follow the canonical RTT teaching and analysis sequence:
p_Capturep_Analyzep_Driftp_Coherencep_Operatorp_Domainp_Substratep_Teachingp_Research
Rules:
- Templates unlock in order
- Each template requires viewing or completing the previous
- Teaching and Research templates unlock only after full traversal
Stack Flow#
Stacks follow the structural progression of RTT:
- Structural Stack
- Diagnostic Stack
- Operator Stack
- Substrate Stack
- Domain Stack
- Teaching Stack
- Research Stack
Rules:
- Stacks unlock based on prerequisites
- Each stack supports specific templates and modules
- Teaching and Research stacks require full traversal
Engine Flow#
RTT engines unlock progressively:
- RTT/1
- RTT/2
- RTT/3
- RTT/12
- RTT∞
- IPD‑12
Rules:
- Engines cannot be accessed out of order
- Each engine requires viewing or completing the previous
- IPD‑12 unlocks only after full RTT traversal
Module Flow#
Modules follow a multi‑layer flow:
- Structural Modules
- Substrate Modules
- Domain Modules
- Teaching Modules
- Research Modules
- Applied Modules
- Examples
Rules:
- Modules unlock based on engine + stack + template prerequisites
- Applied modules may require multiple stacks
- Example modules unlock last
Teaching Flow#
Teaching bundles follow the canonical instructional sequence:
- Capture
- Analyze
- Drift
- Coherence
- Synthesis
Rules:
- Worksheets follow the same sequence
- Posters follow the same sequence
- Teaching stacks and templates must be unlocked first
Diagnostic Flow#
Diagnostics follow the seven‑signal RTT diagnostic sequence:
- Identity Signal
- Drift Signal
- Coherence Signal
- Regime‑Point Signal
- Substrate Signal
- Dimensional Signal
- Domain Signal
Rules:
- Diagnostics appear in compact blocks
- Signals must follow canonical order
- No nested lists
Synthesis Flow#
Synthesis flows aggregate all layers:
- Structural
- Drift
- Coherence
- Regime‑Points
- Substrate
- Dimensions
- Domains
- Cross‑Domain Alignment
- Final Synthesis
Rules:
- Synthesis unlocks only after full flow traversal
- Synthesis appears in templates, modules, engines, worksheets, and posters
UI Behavior#
UI Flows determine:
- which modules appear next
- which templates unlock
- which stacks become available
- which engine layers are visible
- which overlays appear in the S3 Spine Visualizer
- how navigation behaves across the Prompts site
Flows ensure that the UI remains consistent with RTT operator grammar.
Cross‑Links#
index.md— UI front‑doorunlock-logic.md— unlock rulesdependency-graph.md— dependency graphwireframe.md— wireframe layoutoutput-format.md— output formattingoverlays.md— spine overlays
Manifest#
See module.json for the full registry of UI modules, templates, stacks, engines,
examples, and navigation structure.