Research Stack — TriadicFrameworks Prompts
The Research Stack provides structured prompt families for conducting RTT‑aligned research across any domain. It defines how inquiry moves, aligns, diverges, or stabilizes using RTT operators, drift‑tensor mapping, coherence anchors, and multi‑layer alignment.
Research stack prompts are used in academic, scientific, civic, cultural, and technical research.
Purpose#
The Research Stack teaches:
- how to conduct substrate‑aware, drift‑bounded research
- how to use RTT operators to structure inquiry
- how to identify drift across competing theories or models
- how to declare coherence anchors during research
- how to evaluate multi‑layer alignment in research findings
- how to detect regime‑points across RTT/1 → RTT∞
- how to maintain structural neutrality while analyzing research data
It is one of the deepest stacks in the TriadicFrameworks canon.
Prompt Families#
Research Identity Prompts#
Used to establish the identity, scope, and commitments of a research question.
Examples:
- Declare the identity of this research question.
- Identify the structural commitments of this inquiry.
- Surface the boundaries that constrain this research domain.
- Describe the relational topology of this research space.
- Identify the operators that define this research structure.
Research Drift Prompts#
Used to identify differences across theories, models, or findings.
Examples:
- Identify drift between these two research interpretations.
- Map operational drift across these research steps.
- Surface temporal drift in these research results.
- Declare conceptual drift across these explanations.
- Identify domain drift between these research frameworks.
Research Coherence Prompts#
Used to declare what remains aligned across competing explanations.
Examples:
- Identify shared purpose across these research models.
- Declare boundary coherence between these research domains.
- Surface constraint coherence across these findings.
- Identify goal coherence across these research layers.
- Declare structural continuity across these interpretations.
Research Regime‑Point Prompts#
Used to surface presence, absence, tension, and attractor behavior.
Examples:
- Identify presence in this research regime.
- Surface absence in this theoretical model.
- Declare tension across these research layers.
- Identify basin behavior in this research attractor.
- Surface regime‑point transitions across this domain.
Research Synthesis Prompts#
Used to evaluate cross‑layer alignment and produce resonance‑aligned summaries.
Examples:
- Evaluate structural alignment across these research layers.
- Identify operator consistency across these findings.
- Declare coherence across these research transitions.
- Surface substrate alignment across these research conditions.
- Produce a synthesis summary across these research regimes.
Stack Usage#
The Research Stack is used in:
- RTT/1 foundational research workflows
- RTT/2 multi‑layer research mapping
- RTT/3 research synthesis and tension surfacing
- RTT/12 full‑spectrum research alignment
- RTT∞ deep‑layer substrate‑tensor research
- IPD‑12 paradox research workflows
- Teaching modules (research worksheets, posters, sessions)
- Applied modules (datacenter, mythology, physics, teaching)
- Domain modules (psychology, physics, economics, governance, AI, biology)
It is the backbone of TriadicFrameworks research methodology.
Cross‑Links#
Prompts Site#
https://www.triadicframeworks.org/prompts/stacks/research-stack/
Docsbook#
https://docs.triadicframeworks.org/docs/
S3 Spine Visualizer#
https://www.triadicframeworks.org/spine
GitHub Source#
https://github.com/umaywant2/TriadicFrameworks/tree/main/docs/prompts/stacks
Related Files#
structural-stack.md— structural operatorsdiagnostic-stack.md— diagnostic operatorsoperator-stack.md— operator grammarsubstrate-stack.md— substrate behaviordomain-stack.md— domain traversalteaching-stack.md— teaching workflows../modules/research.md— research modules../examples/index.md— research examples
Manifest#
See module.json for the full registry of stacks, modules, engines, templates, UI
modules, and navigation structure.