Analyze Template — TriadicFrameworks Prompts

The Analyze Template provides the canonical structure for analyzing any system using RTT engines, operator grammar, drift‑tensor mapping, coherence anchors, substrate behavior, dimensional rails, and domain traversal.
It is used across modules, stacks, engines, and teaching workflows.

This template defines the standard analysis grammar for TriadicFrameworks.

Purpose#

Use this template when you need to:

• analyze structure using RTT operators
• identify drift across the five drift‑tensor layers
• declare coherence anchors
• surface regime‑points (presence, absence, tension, basin)
• evaluate multi‑layer alignment
• analyze substrate behavior and dimensional transitions
• traverse domains using RTT operator grammar
• maintain structural neutrality during analysis

Analysis Template#

1. Identity#

Declare the identity of the system being analyzed.

Prompt:

• Declare the identity of this system. What is its form, purpose, and boundary?

2. Structural Operators#

Identify the operators governing the system.

Prompt:

• Identify the structural operators present in this system (identity, boundary, commitment, topology).

3. Drift‑Tensor Analysis#

Surface drift across the five RTT drift layers.

Prompt:

• Identify geometric drift.
• Identify operational drift.
• Identify temporal drift.
• Identify conceptual drift.
• Identify domain drift.

4. Coherence Anchors#

Declare what remains aligned despite drift.

Prompt:

• Identify purpose coherence.
• Identify constraint coherence.
• Identify goal coherence.
• Identify continuity coherence.

5. Regime‑Point Analysis#

Surface presence, absence, tension, and basin behavior.

Prompt:

• Identify presence.
• Identify absence.
• Identify tension.
• Identify basin behavior.

6. Substrate Analysis#

Analyze the substrate‑tensor and substrate transitions.

Prompt:

• Identify substrate behavior.
• Surface substrate drift.
• Declare substrate coherence.
• Identify substrate regime‑points.
• Map substrate‑tensor transitions.

7. Dimensional Rails#

Analyze dimensional movement and transitions.

Prompt:

• Identify dimensional rails.
• Surface dimensional drift.
• Declare dimensional coherence.
• Identify prime‑state transitions.
• Map collapse and integration operators.

8. Domain Traversal#

Analyze the system across the six canonical domains.

Prompt:

• Identify domain operators.
• Surface domain drift.
• Declare domain coherence.
• Map cross‑domain alignment.

9. Synthesis#

Produce a resonance‑aligned synthesis summary.

Prompt:

• Produce a synthesis summary across all layers (structure, drift, coherence, regime‑points, substrate, dimensions, domains).

Cross‑Links#

• p_Capture.md — capture template
• p_Drift.md — drift template
• p_Coherence.md — coherence template
• p_Operator.md — operator template
• p_Domain.md — domain template
• p_Substrate.md — substrate template
• p_Teaching.md — teaching template
• p_Research.md — research template

Manifest#

See module.json for the full registry of templates, modules, stacks, engines, UI modules, and navigation structure.