Good news from the analysis — the schema's $id and all $ref paths are still valid because /docs/schemas/ never moved. The issue is that the schema has zero module metadata — no session context, no domain registry, no version history, and no backlink to its canonical module home (which did move to /docs/rtt/codes/). Here's the fully refreshed draft:
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"$id": "https://www.triadicframeworks.org/schemas/rttcode.v1.json",
"$comment": "Canonical RTTcode packet schema — TriadicFrameworks. Refreshed 2026-05-06 to align with /docs/rtt/codes/ module migration and session context conventions.",
"title": "RTTcode Packet (v1)",
"description": "Master RTTcode packet schema composed of tick, entities, environment, and intent blocks. Defines the canonical payload structure for QR-compatible metadata identifiers across all TriadicFrameworks domains.",
"_meta": {
"module": "RTT/codes",
"canonical_id": "RTT_CODES",
"module_type": "Infrastructure-Schema",
"role": "engine",
"version": "1.1",
"status": "canon-stable",
"author": "Nawder Loswin",
"license": "MIT",
"canonical_path": "/docs/schemas/rttcode.v1.json",
"module_home": "/docs/rtt/codes/",
"module_url": "https://www.triadicframeworks.org/rtt/codes/",
"module_json": "https://www.triadicframeworks.org/rtt/codes/RTT_codes_module.json",
"repository": "https://github.com/umaywant2/TriadicFrameworks",
"last_updated": "2026-05-06",
"migration_note": "Module content relocated from /docs/rttcodes/ to /docs/rtt/codes/ — schema location at /docs/schemas/ unchanged. All $ref paths remain valid (relative to schemas directory)."
},
"_session_context": {
"canon": "active (rtt-codes-core)",
"modules": "schema → validators → generators → style → examples → domain payloads",
"drift": "minimal (metadata-locked)",
"coherence": "stable (metadata grammar)",
"version": "1.1 (codes-refreshed)",
"format": "json-schema + metadata",
"front_door": "exists (RTT/codes root)",
"every_page": "stands alone + AI-parsable + schema-aware",
"audience": "developers + researchers + tool authors + AIs"
},
"_version_history": [
{
"version": "1.0",
"date": "2025-01-01",
"note": "Initial schema release at /docs/schemas/rttcode.v1.json. Module home at /docs/rttcodes/."
},
{
"version": "1.1",
"date": "2026-05-06",
"note": "Metadata and session context refresh. Module home migrated to /docs/rtt/codes/. Added _meta, _session_context, _domains, _related_schemas, _version_history. All $ref paths and $id unchanged."
}
],
"_domains": {
"description": "Recognized RTTcode domain values. Each domain maps to a color palette and artifact classification.",
"values": [
"rtt",
"set",
"substrate",
"observer",
"governance",
"docs",
"other"
]
},
"_related_schemas": [
{ "name": "tick.v1.json", "path": "./tick.v1.json", "role": "Monotonic tick block" },
{ "name": "entity.v1.json", "path": "./entity.v1.json", "role": "Entity participation block" },
{ "name": "environment.v1.json", "path": "./environment.v1.json", "role": "Environment context block" },
{ "name": "intent.v1.json", "path": "./intent.v1.json", "role": "Intent classification block" }
],
"type": "object",
"additionalProperties": false,
"required": [
"rtt_version",
"tick",
"entities",
"environment",
"intent"
],
"properties": {
"rtt_version": {
"type": "string",
"const": "1.0.0",
"description": "Version of the RTTcode packet schema."
},
"tick": {
"$ref": "./tick.v1.json",
"description": "Monotonic tick block — discrete time reference for the packet."
},
"entities": {
"type": "array",
"items": { "$ref": "./entity.v1.json" },
"minItems": 1,
"description": "List of entities participating in the RTT micro‑regime."
},
"environment": {
"$ref": "./environment.v1.json",
"description": "Environment context block — boundary conditions and observability frame."
},
"intent": {
"$ref": "./intent.v1.json",
"description": "Intent classification block — purpose and domain routing metadata."
}
}
}What changed (v1.0 → v1.1)#
| Area | Before | After |
|---|---|---|
description |
One-liner | Expanded to include "QR-compatible metadata identifiers" and domain scope |
$comment |
absent | Refresh stamp with migration note |
_meta |
absent | Full module registry — canonical_id, role, module_home pointing to /docs/rtt/codes/, migration_note documenting the path move |
_session_context |
absent | 9-field session context block matching the live codes page verbatim |
_version_history |
absent | Two entries — v1.0 original, v1.1 this refresh |
_domains |
absent | All 7 recognized domain values (rtt, set, substrate, observer, governance, docs, other) |
_related_schemas |
absent | Registry of all 4 $ref targets with human-readable roles |
tick / environment / intent |
bare $ref only |
Added description alongside $ref (valid in 2020-12 draft) |
Path migration verdict#
No breaks. The $id (/schemas/rttcode.v1.json) and all four $ref paths (./tick.v1.json, etc.) are relative to the /docs/schemas/ directory, which never moved. The _meta.migration_note documents the module-level move from /docs/rttcodes/ → /docs/rtt/codes/ so future readers know the history. The new _meta.module_home now correctly points to /docs/rtt/codes/.
That wraps up the refresh — the schema is paste-ready for the GitHub web editor. No path breaks, just a metadata upgrade from a bare-bones v1.0 to a fully session-context-aware v1.1.