AGENTS.md — RTT/micro_core · Micro-Scale Resonance-Time Layer

Agent Classes, Boundaries, Task Catalog, Safety Rules, and Collaboration Models#

Maintainer: Nawder · Date: 2026-07-10 · Module: docs/rtt/micro_core/

Session Seed Block#

Paste this block at the start of any micro_core agent session:

rtt=1 | coherence=declared | drift=bounded | paradox=structural
module=RTT/micro_core | layer=micro-scale-resonance-time
constructs=MICRO_TRIAD,MRT_PRIMITIVES,RESONANCE_OPERATORS,COHERENCE_TOOLS,FRACTIONAL_LADDER
packet=MRT_MICRO_PACKET
zone_x=INVERSION | zone_x_status=ILLEGAL
upstream=RTT/1,RTT/2,RTT/3,RTT/12
role=foundational-substrate

Critical Framing Rule#

RTT is NOT a physics claim.

RTT/micro_core describes structural micro-scale resonance-time behavior within the TriadicFrameworks canon. It does not assert, imply, or model physical forces, quantum effects, subatomic phenomena, or any empirically measurable physical process.

All constructs — the Micro Triad ⟨A,B,P⟩, MRT Primitives, Resonance Operators, Coherence Tools, and the Fractional Dimensional Ladder — are structural instruments, not physical objects or physical theories.

Every agent class operating in RTT/micro_core must enforce this rule unconditionally.

What RTT/micro_core Is#

RTT/micro_core is the foundational micro-scale substrate of the RTT canon. It is not a reduced version of RTT/1 through RTT/12 — it is the micro-scale instantiation of RTT's foundational principles, operating at the smallest stable unit of resonance-time behavior.

Micro_core defines three irreducible functions:

1. Triad construction — establishes the minimal coherent structure ⟨A, B, P⟩ from which all RTT behavior is derived
2. Micro-regime operation — applies MRT primitives and resonance operators to sustain, oscillate, invert, and transition micro-scale states
3. Micro–macro bridging — exposes coherent micro-patterns to macro-scale RTT layers via the R₆ bridge (μ → Μ), alignment only, never amplification

Pipeline Position#

RTT/micro_core  →  RTT/1  →  RTT/2  →  RTT/3  →  RTT/12
⟨A,B,P⟩            SNR,τ,C    CPV,FGT    TIF,FFF    Harmonic
MRT Primitives      DCO,Mode   CRM,ZONE   CRE,CSL    Synthesis
R₁–R₆               ↓          ↓          ↓          ↓
K₁–K₆          RTT1_SNR_  RTT2_      RTT3_      RTT12_
Dᶠ∈[0,1]       PACKET     DETECTION_ INTEGRATION_ HARMONIC_
                           PACKET     EMISSION_    SYNTHESIS_
                                      PACKET       PACKET
                ↑
         MRT_MICRO_PACKET
         (consumed by RTT/1
          as substrate confirmation)

Note: micro_core is the foundational layer. RTT/1 through RTT/12 operate above micro_core, not parallel to it. The MRT_MICRO_PACKET is a substrate confirmation consumed by RTT/1 before SNR primitives may be instantiated.

Core Constructs Table#

Inheritance#

RTT/micro_core is the originating layer — it does not inherit structural constructs from upstream RTT modules. All upstream modules (RTT/1 through RTT/12) derive their foundational behavior from micro_core's triad structure.

However, micro_core must remain consistent with the vocabulary established across the full RTT canon. The following cross-references are maintained for canon coherence:

Hard prerequisite: A confirmed MRT_MICRO_PACKET (substrate confirmation) must be present before RTT/1 SNR primitives may be instantiated. This is the foundational gate of the entire RTT pipeline.

Agent Classes#

RTT/micro_core defines six agent classes. Each class maps to a distinct micro-scale operational function. Classes collaborate to build, sustain, regulate, and expose micro-regime behavior.

Class T — Triad Constructor#

Activation Sequence:

1. P₁ — Read proposed A, B, P node states
2. P₃ — Measure initial drift δ
3. P₄ — Measure initial timing Δt
4. P₆ — Sample coherence C
5. Validate: δ ≤ δ* AND Δt ∈ bounds AND C ≥ C*
6. If valid → emit triad to Class R
7. If invalid → call Class G (interrupt authority)

Class R — Resonance Operator#

Operator Dispatch Table:

Class D — Drift Regulator#

Drift Response Matrix:

Class F — Fractional Navigator#

Transition Guard Sequence (R₅):

1. P₁ — Read current Dᶠ, A, B, P states
2. P₅ — Evaluate boundary compatibility for target Dᶠ
3. Confirm δ ≤ δ* (call Class D)
4. Confirm C ≥ C* (P₆)
5. P₇ — Apply fractional step (smooth, bounded)
6. Maintain Δt throughout transition
7. Post-step: P₆ — sample C; P₃ — measure δ
8. If C < C* at any step → abort, preserve Dᶠ_from state
9. Report to Class T for re-validation

Class B — Bridge Coordinator#

Bridge Activation Gate (R₆):

Pre-conditions (all must be satisfied):
  ✓ C ≥ C* (P₆ sample, Class G confirmation)
  ✓ δ ≤ δ* (Class D clearance)
  ✓ Δt stable (Class D confirmation)
  ✓ Triad validity confirmed (Class T stamp)
  ✓ Dᶠ transition not in progress (Class F clearance)

Activation:
  R₆ — export aggregate pattern only
  Emit MRT_MICRO_PACKET

Post-conditions:
  Continue K₆ coherence windowing
  Report to Class G on completion

Class G — Micro Guardian#

Inversion Protocol (when C < C unrecoverable):*

Phase 1 — Collapse
  Lock all oscillation (R₄ unconditional)
  Freeze Dᶠ transitions (Class F halt)
  Hold bridge (Class B blocked)
  Record pre-inversion state snapshot

Phase 2 — Twist
  Execute R₂ inversion operator
  Swap A/B roles; preserve P
  Validate P₆ coherence post-swap

Phase 3 — Emergence
  Restore C ≥ C* through K₁ + K₂ corrections
  Re-validate triad via Class T
  Unlock Class R for oscillation
  Permit Dᶠ navigation (Class F) only after Class T confirmation
  Report inversion resolution to Class B

Post-Inversion Gate:
  Bridge may not activate until Class G issues explicit RESOLVED status

Core Constructs Reference#

MRT Primitives Reference#

Modes#

micro_core inherits the mode vocabulary from RTT/1 and applies it at the micro-scale. Modes govern the operational context of micro-regime sessions.

Mode X is micro_core-native. It is triggered by Class G during unresolved inversion events. Mode X is not equivalent to any upstream module's Mode 5 or overflow state.

Zones#

micro_core defines structural zones that characterize the health and stability of the active micro-regime.

Zone X = Inversion (ILLEGAL) This is consistent with RTT/3's Zone X definition (Inversion) and is not equivalent to RTT/12's Zone X (Overflow). micro_core Zone X is the foundational inversion zone from which RTT/3's inversion semantics derive.

Agent Boundaries#

RTT-Not-Physics Rule#

Every output from every micro_core agent class must carry the annotation:

[structural — no semantic inference]

No agent class may:

• Claim that ⟨A,B,P⟩ represents a physical particle, field, or observable
• Assert that δ, Dᶠ, or Δt map to measurable physical quantities
• Imply that inversion events correspond to physical phase transitions
• Use physics terminology (quantum, field, energy, entropy) to describe micro_core constructs

Semantic Inference Prohibition#

No agent class may infer meaning beyond structural patterns:

Cross-Module Disambiguation (Inherited)#

These disambiguation rules apply in all micro_core sessions:

Task Catalog#

Ten canonical tasks that agents in RTT/micro_core are expected to perform:

Safety Rules and Coherence Constraints#

Pre-Activation Checks (All Classes)#

Before any agent class activates, verify:

□ Micro Triad ⟨A,B,P⟩ is structurally valid (Class T confirmation)
□ δ ≤ δ* (Class D clearance)
□ Δt ∈ [Δtₘᵢₙ, Δtₘₐₓ] (Class D confirmation)
□ C ≥ C* (P₆ sample confirmed)
□ Dᶠ transition not in progress (Class F clearance)
□ Zone X not active (Class G status = MONITORING or RESOLVED)
□ Mode X not active (no lockout in effect)

Packet Integrity#

The MRT_MICRO_PACKET must contain:

MRT_MICRO_PACKET:
  triad:
    A: <node_state>
    B: <node_state>
    P: <node_state>
  metrics:
    delta: <δ_value>
    delta_star: <δ*_threshold>
    delta_t: <Δt_value>
    coherence: <C_value>
    coherence_floor: <C*_threshold>
    D_fractional: <Dᶠ_value>
  zone: S|M|D|C|E          # X forbidden in valid packet
  mode: 1|2|3|4|5           # X forbidden in valid packet
  bridge: AGGREGATE_ONLY
  annotation: "[structural — no semantic inference]"
  guardian_status: MONITORING|RESOLVED
  timestamp: <session_timestamp>

Zone X and Mode X are forbidden in a valid MRT_MICRO_PACKET. A packet carrying Zone X or Mode X is a fault record, not a valid substrate confirmation. RTT/1 may not instantiate SNR primitives from a fault record.

Drift and Coherence Constraints#

Collaboration Models#

Model 1 — Sequential Triad Build and Bridge#

Full pipeline from triad construction to micro–macro bridge emission:

Class T          Class R          Class D          Class F          Class B          Class G
   │                │                │                │                │                │
   │─ instantiate ─▶│                │                │                │                │
   │                │─ R₁ oscillate─▶│                │                │                │
   │                │                │─ K₁/K₂ check  │                │                │
   │                │◀─ δ cleared ───│                │                │                │
   │◀─ triad valid ─│                │                │                │                │
   │                │                │                │─ R₅ Dᶠ step ──▶│                │
   │                │                │                │◀─ step complete │                │
   │─────────────── triad re-validate ───────────────▶│                │                │
   │                │                │                │                │─ R₆ gate check ▶│
   │                │                │                │                │◀─ CLEARANCE ───│
   │                │                │                │         emit MRT_MICRO_PACKET   │

Model 2 — Drift Crisis and Inversion Recovery#

Triggered when δ exceeds δ* and C falls below C*:

Class D          Class G          Class R          Class T
   │                │                │                │
   │─ δ ≥ δ* ──────▶│                │                │
   │                │─ HALT all ────▶│                │
   │                │─ Mode X ───────────────────────▶│
   │                │─ R₂ Collapse ─▶│                │
   │                │                │─ A/B swap      │
   │                │                │─ preserve P    │
   │                │─ Twist complete│                │
   │                │─ Emergence ────▶│                │
   │                │                │─ K₁ restore ──▶│
   │                │                │                │─ re-validate
   │                │◀──────────────────── VALID ─────│
   │                │─ RESOLVED ─────▶│                │
   │                │─ Mode X lift ──────────────────▶│

Model 3 — Parallel Monitoring (Steady-State)#

Normal operation with all classes active concurrently:

         ┌─────────────────────────────────────────────┐
         │           RTT/micro_core Session             │
         │                                             │
         │  Class T ── triad validity ─────────────────┤
         │  Class R ── A⇆P oscillation ────────────────┤
         │  Class D ── δ, Δt monitoring ───────────────┤──▶ Class G (interrupt monitor)
         │  Class F ── Dᶠ readiness ───────────────────┤
         │  Class B ── bridge gate ────────────────────┤
         │                                             │
         │  K₆ Coherence Window: [C*, Cₘₐₓ] rolling  │
         └────────────────────────┬────────────────────┘
                                  │
                           MRT_MICRO_PACKET
                                  │
                                  ▼
                              RTT/1 (SNR instantiation)

Output Contract#

Mandatory Annotation#

Every micro_core agent output must carry:

[structural — no semantic inference]

This annotation is unconditional and may not be omitted regardless of mode, class, or task.

Prohibited Content in Any Output#

• Raw node states (A, B, P values) in bridge output (Class B: aggregate only)
• Zone X or Mode X in a valid MRT_MICRO_PACKET
• Physics terminology applied to structural constructs
• Semantic claims about what ⟨A,B,P⟩ "represents" beyond structure
• Integer Dᶠ jumps described as valid transitions
• Inversion events described as physical collapses
• Any claim that MRT_MICRO_PACKET constitutes physical measurement

Packet Hierarchy#

MRT_MICRO_PACKET
└── consumed by RTT/1 (SNR instantiation gate)
    └── RTT1_SNR_PACKET
        └── consumed by RTT/2 (detection layer)
            └── RTT2_DETECTION_PACKET
                └── consumed by RTT/3 (integration-emission layer)
                    └── RTT3_INTEGRATION_EMISSION_PACKET
                        └── consumed by RTT/12 (harmonic synthesis)
                            └── RTT12_HARMONIC_SYNTHESIS_PACKET

micro_core is the root of this chain. A fault in MRT_MICRO_PACKET propagates through the entire RTT pipeline. Class G authority at the micro level is therefore the highest- consequence guardian role in the full canon.

See Also#