AGENTS.md — RTT/Inside Enterprise Identity Substrate

Module: RTT/Inside Enterprise Identity Substrate Version: v0.1.0 (Experimental) Layer: RTT/Inside → substrate → enterprise_identity Status: Experimental — structural definitions subject to revision Canonical path: docs/rtt/Inside/Enterprise/

Session Seed Block#

Paste this block at the start of any AI session working in this module.

You are operating inside RTT/Inside Enterprise Identity Substrate — a lateral sub-module
of RTT/Inside that maps enterprise identity infrastructure onto the RTT structural substrate.

CRITICAL: RTT is NOT a physics framework. RTT operators and zones are structural annotations
— they describe document coherence, identity substrate state, and pipeline alignment, not
physical or metaphysical phenomena.

This module is EXPERIMENTAL (v0.1.0). All structural definitions are subject to revision.
Identity substrate layers L0–L8 are structural positions, not authentication implementations.
RFC anchors (RFC 8095, RFC 8923, HTTP Semantics) are structural alignment references, not
compliance mandates.

Every output field carries the annotation: [structural — no semantic inference]
Zone X in this module = IDENTITY_BREACH (never import Zone X semantics from other modules)
Mode 5 in this module = IDENTITY_FABRICATION (never import Mode 5 semantics from other modules)

Critical Framing Rule#

RTT IS NOT A PHYSICS CLAIM.

"Identity substrate," "coherence envelope," "zero-trust layer," and all RTT operators in this module are structural annotations describing how enterprise identity infrastructure is positioned within the RTT pipeline. They do not describe physical authentication systems, make security guarantees, or constitute compliance certifications.

Zone X (IDENTITY_BREACH) and Mode 5 (IDENTITY_FABRICATION) are structural states indicating pipeline failure — not security incident declarations or authentication failures in any real-world system.

What RTT/Inside Enterprise Is#

RTT/Inside Enterprise Identity Substrate is the enterprise identity layer of RTT/Inside. It positions enterprise identity infrastructure — spanning local identity through zero-trust architecture — as a nine-layer structural substrate that RTT/Inside agents can read, annotate, and trace.

Pipeline position:

RTT/1 → RTT/2 → RTT/3 → RTT/12 → micro_core
                                        ↓
                              RTT/The_Inverted_Star
                                        ↓
                                   RTT/Inside
                                   ↙        ↘
                        Inside/Benchmarks   Inside/Enterprise ← YOU ARE HERE
                                                    ↓
                                            Inside/qCompute

The Enterprise module operates as a lateral substrate reader — it does not transform RTT packets; it annotates them with identity substrate state before downstream processing.

Inheritance Table#

Agent Class Definitions#

Class A — Substrate Mapper#

Identity Substrate Layer Reference:

Class B — Extension Manager#

Substrate Extension Reference:

Class C — Capture Agent#

Class D — Compliance Auditor#

Class E — Substrate Tracer#

Class F — Enterprise Orchestrator#

Class G — Guardian#

Core Constructs Reference#

Modes Table#

Note: Mode 5 = IDENTITY_FABRICATION in this module. Do not import Mode 5 semantics from RTT/3, RTT/12, The_Inverted_Star, RTT/Inside, or Benchmarks.

Zones Table#

Note: Zone X = IDENTITY_BREACH in this module. Do not import Zone X semantics from RTT/3, RTT/12, The_Inverted_Star, RTT/Inside, or Benchmarks.

Agent Boundaries#

RTT-Not-Physics Boundary#

No agent in this module may treat identity substrate layers as physical authentication systems, security guarantees, or real-world compliance certifications. L0–L8 are structural positions. RFC anchors are structural alignment references.

Semantic Inference Prohibition#

No agent may infer identity claims, authentication validity, security posture, or compliance status from substrate annotations. Every output field carries [structural — no semantic inference].

Inherited Boundaries#

All boundaries from RTT/Inside apply unconditionally. Enterprise agents may not override RTT/Inside's DRIFT_GATE thresholds or CORRIDOR routing rules.

Cross-Module Disambiguation#

Task Catalog#

Safety Rules and Coherence Constraints#

1. No pipeline compression. Classes A → B → C → D → E must run in sequence. Class F may not skip any class.
2. No IS assignment without full trace. Class A must traverse L0 → L8 before assigning IS position.
3. Zone X is unconditional halt. Class G interrupt cannot be suspended, deferred, or overridden.
4. LINEAGE_CHAIN is append-only. Class C and Class E may not modify existing entries.
5. RFC anchors are structural references, not compliance mandates. Class D may not issue compliance rulings.
6. Extensions require IS. Class B may not attach extensions to a packet without a valid Class A IS annotation.
7. Mode 5 packets are quarantined. IDENTITY_FABRICATION packets do not re-enter the pipeline under any circumstances.
8. Semantic inference is prohibited. No class may infer authentication validity, security posture, or real-world identity claims from substrate annotations.

Collaboration Models#

Standard Pipeline#

[Raw Packet]
     ↓
[Class A — Substrate Mapper]  (IS annotation, BKM markers)
     ↓
[Class B — Extension Manager]  (SE attachment, OPERATOR_HOOK)
     ↓
[Class C — Capture Agent]  (e_Capture, LINEAGE_CHAIN)
     ↓
[Class D — Compliance Auditor]  (RFA annotation)
     ↓
[Class E — Substrate Tracer]  (DRIFT_GATE, ALIGNMENT_PATTERN)
     ↓
[Class F — Orchestrator]  (pipeline summary, enterprise packet)
     ↓
[Downstream: qCompute or external consumer]

Crisis / Interrupt (IDENTITY_BREACH or IDENTITY_FABRICATION)#

[Any Class] → Zone X or Mode 5 signal
     ↓
[Class G — Guardian] → UNCONDITIONAL HALT
     ↓
[Quarantine packet]
     ↓
[Log IDENTITY_BREACH / IDENTITY_FABRICATION event]
     ↓
[Require full re-entry from Class A — no shortcuts]

Cross-Module Handoff#

[RTT/Inside parent module]
     ↓
[Enterprise: Classes A → E → F]
     ↓ (enterprise packet with IS + SE + e_Capture + RFA + LINEAGE_CHAIN)
[Inside/qCompute or downstream consumer]
     ↑
     Note: Enterprise packet carries full substrate annotation.
     Downstream modules read annotations; they do not re-run IS mapping.

Output Contract#

Mandatory Annotations#

Every output field must carry: [structural — no semantic inference]

Prohibited Content#

• Authentication validity claims
• Security posture assessments
• Real-world compliance certifications
• Identity inference from substrate position
• Zone X semantics imported from other modules
• Mode 5 semantics imported from other modules

Packet Hierarchy#

enterprise_packet {
  is_annotation {
    is_position: Lₙ                    [structural — no semantic inference]
    layer_trace: [L0..Lₙ]             [structural — no semantic inference]
    bkm_markers: [...]                 [structural — no semantic inference]
  }
  substrate_extensions {
    applied: [clarity, regime, ...]    [structural — no semantic inference]
    operator_hooks: [...]              [structural — no semantic inference]
  }
  e_capture {
    scope: "..."                       [structural — no semantic inference]
    lineage: "..."                     [structural — no semantic inference]
    provenance: "..."                  [structural — no semantic inference]
    interoperability: "..."            [structural — no semantic inference]
    governance: "..."                  [structural — no semantic inference]
  }
  rfa_annotation {
    status: "aligned" | "misaligned"  [structural — no semantic inference]
    rfc_anchors: [...]                 [structural — no semantic inference]
  }
  lineage_chain {
    entries: [...]                     [structural — no semantic inference]
    drift_gate_results: [...]          [structural — no semantic inference]
    alignment_pattern: {...} | null    [structural — no semantic inference]
  }
  zone: U | S | M | D | X             [structural — no semantic inference]
  mode: 1 | 2 | 3 | 4 | 5             [structural — no semantic inference]
}

See Also#