Mage Tower · Data Provenance

TRACEABILITY PIPELINE

Data flow, entity provenance, and trust chain visualization for the Owl Academy Mage Tower. Every record traces to a cryptographic root.

Identity layer
Authority layer
Knowledge layer
Social layer
01

Pipeline Overview Diagram

planes / tier ↓
↑ defines planes
configures
Knowledge Layer
Instructor Console Tome authorship, XP, artifacts
community cert
published tomes
Prereq Math Community video library
Learning Hub Student tome access
familiar slots / social layer
Social Layer
Familiars Manifold companions Store Vis economy Constellation Map Network visualization
familiar manifold → crystallization anchor
Engram Mind Eye N/K/T crystallization · packet chain export
02

Data Entity Reference

Entity Created In Firestore Path Consumed By
Cosmological ID Registrar users/{uid}/profile/main
.cosmologicalId
Codex, Instructor Console, Genesis Forge, Constellation Map
Lattice / Coords Registrar users/{uid}/profile/main
.{lattice, coords}
Codex (sigil), Familiars
Genesis Certificate Genesis Forge users/{uid}/profile/main
.genesisCert
Codex (tier), Instructor Console (auth)
Dimensional Planes Admin Console academy/config/planes[] Genesis Forge, Instructor Console
Tome Instructor Console tomes/{tomeId} Learning Hub, Admin Registry, Codex XP
Artifact Instructor Console artifacts/{id} Store, Codex artifacts count
Vis Balance Vis Service users/{uid}/vis/balance Store, Codex
Familiar Manifold Familiars users/{uid}/profile/main
.familiarManifolds[slot]
Engram Mind Eye
Packet Chain Engram Mind Eye localStorage O1 Compressor, Blackwell Architect
Biochain Engram Mind Eye localStorage STRIX personality
03

Trust Chain Diagram

GENESIS_MASTER_UIDS
code constant · scripts/genesis-registrar.js
bootstrap anchor
↓ self-signs (bootstrap only)
Root Archon
self-signed cert · tier: ARCHON
→ Admin Console, Genesis Forge
↓ signs Archon Certificate
Archon Certificate
{ tier: ARCHON, plane, recipientId, issuerId, issued }
→ recipient becomes Archon
↓ signs Instructor Certificate
Instructor Certificate
{ tier: INSTRUCTOR, plane, recipientId, issuerId, issued }
→ recipient becomes Instructor
↓ signs Tome (via Cosmological ID)
📜
Tome / Artifact
authorCosmologicalId embedded · plane certified · tomes/{id}
→ Learning Hub
Root Archon → [cert₁] → Archon A → [cert₂] → Instructor B → Tome C
04

Pipeline Step-by-Step Walkthrough

01
Sign Up → Firebase Auth
Create an account via Firebase Authentication. A unique uid is assigned — this is the Firestore document key for all your records.
02
Open Registrar → Forge Cosmological ID → Firestore Write
Submit a ledger seed phrase and choose a lattice space. The Registrar hashes it into a 64-char hex ID and writes it to Firestore.
Firestore write: users/{uid}/profile/main.cosmologicalId
03
Open Codex → View ID, Acolyte Tier
The Codex reads your Firestore profile and renders your sigil, ID, lattice, coords, and tier. At this point tier = ACOLYTE — no authorship rights.
04
Archon Opens Genesis Forge → Mints Instructor Cert → Firestore Write
An Archon enters your UID, selects a plane and tier. The Forge signs a certificate with their Cosmological ID and writes it to your profile.
Firestore write: users/{yourUid}/profile/main.pendingCert = cert
05
Open Codex → Apply Cert → Tier Upgrades to Instructor
You paste the certificate JSON into the Codex apply form. Firestore updates your tier to INSTRUCTOR. The certified plane is now in your profile.
Firestore write: users/{uid}/profile/main.tier = "INSTRUCTOR"
06
Open Instructor Console → Author a Tome → Firestore Write
The Instructor Console shows your certified planes. Fill in the tome form — title, body, plane, priority. Submit. Your Cosmological ID is embedded as the author signature.
Firestore write: tomes/{tomeId} → { authorCosmologicalId, plane, priority, ... }
07
Tome Appears in Learning Hub
The Learning Hub queries the tomes collection and surfaces your tome under its dimensional plane for students to study.
08
Open Familiars → Assign Manifold to Familiar Slot
In the Manifold Forge, tune N (vertices), K (winding), T (tiers) for your active familiar slot. Save to Firestore.
Firestore write: users/{uid}/profile/main.familiarManifolds[0] = { N, K, T }
09
Open Engram Mind Eye → Binds to Familiar Manifold → Begin Crystallization
The Engram reads your active familiar's N/K/T from Firestore and uses it as the crystallization anchor. Every conversation packet is crystallized against that geometric space.
10
Export Packet Chain → Import to O1 Compressor or Blackwell Architect
The Engram exports a compressed packet chain to localStorage. The O1 Compressor or Blackwell Architect can import this chain to resume or extend the crystallization session.
localStorage: packetChain → { packets[], manifest, familiarManifold }