Single‑Page JSON Schema — TriadicFrameworks

Option A — Single‑Page JSON Schema (Minimal, Complete)#

{
  "RTT-Inside": {
    "Being": {
      "entity_id": "string",
      "type": ["agent", "system", "environment"],
      "time": "timestamp",
      "state": {
        "health": "0..1",
        "stress": "0..1",
        "readiness": "0..1",
        "balance": "-1..1"
      }
    },
    "Knowing": {
      "event_id": "string",
      "time": "timestamp",
      "actor": "entity_id",
      "intent": "string?",
      "decision": "string",
      "action": "string",
      "outcome": "string",
      "affected": ["entity_id"]
    },
    "Meaning": {
      "scope": "entity_id",
      "purpose": "string",
      "success": ["string"],
      "constraints": ["string?"]
    },
    "Time": {
      "scope": "entity_id",
      "signals": {
        "maintenance": "number",
        "drift": "number",
        "recovery": "number",
        "resilience": "number"
      }
    }
  }
}

Minimal Compliance#

A system is RTT‑Inside compatible if it emits:

Being
Knowing
Meaning

Everything else is optional.

Option B — Symbol‑Only Archival Version (Ultra‑Minimal)#

◯ BEING
  └─ state(time)

→ KNOWING
  └─ intent → action → outcome

★ MEANING
  └─ purpose → alignment

⧖ TIME
  └─ drift ↔ recovery

◯ → → ★
  ↑       ↓
     ⧖

Legend#

◯ = Living state
→ = Causal lineage
★ = Purpose / meaning
⧖ = Time / stewardship

No language dependency.
No cultural assumptions.
Pure structure.

Final Archival Note#

This is the smallest stable form of RTT‑Inside.

It survives:

translation
forks
loss of context
loss of technology

It does not instruct.
It reveals.

Updated Apr 29, 2026