The Mage Tower Guide

What Is the Mage Tower?

The Mage Tower is the authority layer that sits above the standard Academy learning experience. It controls who can create knowledge, how that knowledge is trusted, and how it earns XP for students. All content on the Academy — every tome and artifact — carries a cryptographic signature that traces back to this system.

The system has three interlocking parts: a Cosmological Identity (your immutable geometric fingerprint), a Genesis Certificate (cryptographic proof of your tier), and a Dimensional Plane (the content namespace you're authorized to write in).

The Three Tiers

Every user on the Academy occupies one of three tiers. Tiers are cumulative — an Archon has all Instructor capabilities, and an Instructor has all Acolyte capabilities. Promotion is strictly upward; there is no demotion mechanism in the current implementation.

Cosmological ID

Every user has exactly one Cosmological ID — a 64-bit hexadecimal value prefixed with 0x. It is computed deterministically:

CosmologicalId = SHD-CCP(ledgerSeed, latticeSpace)
              XOR
              SHA-256(uid)[0..8]     ← first 8 bytes only

SHD-CCP = Sequential Hyperdimensional Context Compression Protocol
         A 4×4×4 cubic lattice (64 voxels) with φ-weighted axis folding
         and a 32-byte → 64-byte holographic inverse expansion.

Genesis Seed vs Ledger Seed

Validation Certificates

A Validation Certificate is a JSON object cryptographically signed by an Archon using HMAC-SHA-256. It is the only way to prove that someone granted you a tier. No certificate → Acolyte. Tampered certificate → verification fails → Acolyte.

Certificate Anatomy

{
  "issuer":    "0xD4AF37F00BA4C0DE",   // Archon's Cosmological ID
  "subject":   "0x9F00CAFEDEADBEEF",   // Recipient's Cosmological ID
  "tier":      "INSTRUCTOR",            // or "ARCHON"
  "plane":     "dept-IV",              // authoring scope (see Planes)
  "issuedAt":  "2026-06-18T00:00:00.000Z",
  "signature": "a1b2c3...e9f0"         // HMAC-SHA-256 hex
}

HMAC-SHA-256(
  key:  issuerCosmologicalId,
  data: "issuer|tier|plane|subject|issuedAt"
)

Verification Flow

When you apply a certificate in your Codex, this chain runs:

Dimensional Planes

A Dimensional Plane is the namespace within which an Instructor can create tomes and artifacts. Each plane corresponds to one Academy department. An Instructor certified for dept-IV cannot write on dept-X. Archons always receive * (universal) and may write anywhere.

Archon Bootstrap Path

The first Archon cannot receive a certificate from anyone — there is no one above them. This is the bootstrap problem. The system solves it with a Genesis Master Key List: a hardcoded array of Firebase UIDs in scripts/genesis-registrar.js.

// scripts/genesis-registrar.js
export const GENESIS_MASTER_UIDS = [
  "k1E2ylvBlJPMYaCq9SY8muJQx8a2",   // Garrett Hoard — Root Archon
];

Any UID in this list receives implicit Archon authority immediately — even before they create a Cosmological ID or self-sign a certificate. Once they visit Genesis Forge → Self-Sign Archon Certificate, a proper self-signed certificate is written to their Firestore registrar.

Tome Creation

A Tome is a structured knowledge document — the fundamental unit of learning on the Academy. Each tome is stored as a Firestore document at tomes/{tomeId} and carries the author's tier-derived priority, a plane scope, and a status controlling whether it awards XP.

// Firestore: tomes/{tomeId}
{
  "title":           "Clifford Torus Proof",
  "description":     "Demonstrates the flat torus embedding in ℝ⁴",
  "body":            "Full content text or HTML...",
  "dept":            "I",
  "plane":           "dept-I",
  "status":          "active",        // controls XP
  "priority":        "canonical",     // from author's tier
  "creatorUid":      "k1E2ylvBlJPMYaCq9SY8...",
  "creatorGenesisId":"0xD4AF37F00BA4C0DE",
  "creatorTier":     "ARCHON",
  "certificateHash": "a1b2c3d4e5f60708",  // first 16 chars of signature
  "createdAt":       serverTimestamp(),
  "updatedAt":       serverTimestamp()
}

Tome Statuses

Status determines how a tome behaves for students. Only Instructors and Archons can change status via the Admin Console.

Priority Stamping

Every tome is stamped at creation time with a priority derived from the author's tier. When two tomes cover the same topic, priority determines display order. Only Active tomes award XP regardless of priority.

Artifacts

An Artifact is a mastery milestone — a named credential minted when a student completes a required set of tomes. Only the Active tomes in the required list count. Only Instructors and Archons can mint artifacts.

// Firestore: artifacts/{artifactId}
{
  "name":          "Sacred Geometry Mastery",
  "plane":         "dept-I",
  "requiredTomes": ["tomeId1", "tomeId2", ..., "tomeId9"],
  "priority":      "canonical",        // from creator's tier
  "creatorUid":    "k1E2ylvBlJPMYaCq9SY8..."
}

Full Workflow

Path A — Becoming an Acolyte (any user)

Path B — Bootstrapping the Root Archon (one-time)

Path C — Minting a New Instructor (Archon does this)

Path D — Creating a Tome (Instructor or Archon)

Path E — Minting an Artifact

Common Errors

Firestore Setup Checklist

Required steps in Firebase Console before the system is fully functional: