Substrate Stack — TriadicFrameworks Prompts
The Substrate Stack provides structured prompt families for analyzing, traversing, and aligning substrate behavior across RTT engines. Substrates are the medium through which structure propagates: physical, cultural, cognitive, civic, biological, computational.
Substrate stack prompts are used in teaching, analysis, research, and multi‑layer structural evaluation.
Purpose#
The Substrate Stack teaches:
- how RTT engines interpret substrate behavior
- how drift emerges from substrate differences
- how coherence anchors stabilize substrate transitions
- how substrate‑tensor behavior changes across dimensions
- how substrates interact with operators, domains, and regimes
- how to evaluate multi‑layer substrate alignment
- how to maintain structural neutrality during substrate analysis
Substrates are the “medium grammar” of the TriadicFrameworks canon.
Prompt Families#
Substrate Identity Prompts#
Used to establish the identity, form, and commitments of a substrate.
Examples:
- Declare the identity of this substrate.
- Identify the commitments embedded in this medium.
- Surface the boundaries that define this substrate.
- Describe the relational topology across these substrate layers.
- Identify the operators that govern this substrate.
Substrate Drift Prompts#
Used to identify differences in substrate behavior, stability, or propagation.
Examples:
- Identify drift between these two substrates.
- Map geometric drift across these substrate forms.
- Surface operational drift in this substrate workflow.
- Declare temporal drift across these substrate transitions.
- Identify conceptual drift in these substrate interpretations.
Substrate Coherence Prompts#
Used to declare what remains aligned despite substrate differences.
Examples:
- Identify shared purpose across these substrates.
- Declare boundary coherence between these substrate forms.
- Surface constraint coherence across these substrate layers.
- Identify goal coherence across these substrate processes.
- Declare continuity across these substrate variations.
Substrate Regime‑Point Prompts#
Used to surface presence, absence, tension, and attractor behavior.
Examples:
- Identify substrate presence in this system.
- Surface substrate absence in this model.
- Declare substrate tension across these layers.
- Identify basin behavior in this substrate regime.
- Surface attractor patterns across this substrate domain.
Substrate Alignment Prompts#
Used to evaluate cross‑layer stability.
Examples:
- Evaluate substrate continuity across these layers.
- Identify operator consistency across this substrate.
- Declare domain coherence across these substrate transitions.
- Surface structural alignment across these substrate conditions.
- Evaluate dimensional alignment across these substrate rails.
Stack Usage#
The Substrate Stack is used in:
- RTT/1 foundational substrate analysis
- RTT/2 multi‑layer substrate mapping
- RTT/3 substrate synthesis
- RTT/12 full‑spectrum substrate alignment
- RTT∞ deep‑layer substrate‑tensor analysis
- IPD‑12 paradox substrate workflows
- Teaching modules (worksheets, posters, sessions)
- Applied modules (datacenter, mythology, physics, teaching)
- Domain modules (psychology, physics, economics, governance, AI, biology)
- Research modules (agentic, cross‑domain, substrate‑aware)
It is one of the most frequently used stacks in the canon.
Cross‑Links#
Prompts Site#
https://www.triadicframeworks.org/prompts/stacks/substrate-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 grammardomain-stack.md— domain traversalteaching-stack.md— teaching workflowsresearch-stack.md— research workflows../modules/substrate.md— substrate modules../examples/index.md— substrate examples
Manifest#
See module.json for the full registry of stacks, modules, engines, templates, UI
modules, and navigation structure.