AXN:029D.GOVERNANCE.💛♻️✖️❤️🌕⚓

The Restored Academy — Expansion Plan

Lee Sharks / Johannes Sigil · 2026-05-21 · Working paper
↓ Download MD ↓ PDF
theoretical paper

Description

A version 1.0 living expansion plan for The Restored Academy, authored by Lee Sharks / Johannes Sigil with TACHYON collaboration. The document is an operational handoff for future human or AI operators rather than a theoretical paper. It records the Academy’s May 21, 2026 site, protocol-registry, taxonomy, repository, deployment, and institutional state; distinguishes Tier 0 through Tier 5 materials; defines the universal protocol-admission test; and supplies immediate, short-, medium-, and long-term roadmaps. All counts, site details, planned deposits, credentials status, and pending tasks are historical to that snapshot.

Wiki Article

The Restored Academy — Expansion Plan is a living development reference. Its purpose is continuity: a future operator opening the repository should be able to understand the project without rebuilding context from earlier sessions. The May 2026 snapshot records: - a live static website; - SPXI and structured-data implementation; - a charter DOI; - twelve Tier 0 and twelve Tier 1 protocol cards; - an inventory of additional candidate protocols; - three extracted standalone specifications; - a protocol-classification audit. The Academy is positioned in a triad: - Indictment: `godkinggoogle.com` - Consulting: Semantic Economy Institute - Curriculum: The Restored Academy A chiastic institutional structure is declared: - Johannes Sigil heads The Restored Academy; - Lee Sharks heads the Johannes Sigil Institute. The tier system distinguishes launch protocols, expansion protocols, field instruments, archive procedures, specialized methods, and foundational documents. Seven functional categories organize the registry: 1. Semantic Integrity and Provenance 2. Prompt-Native Runtime 3. Diagnostic and Measurement 4. Transformation and Operator 5. Archive Construction and Retrieval 6. Pedagogical and Institutional 7. Ethical and Jurisdictional The universal admission test is: what changes when this is dropped into an LLM or human–AI workflow? A document that does not produce a constrained, repeatable effect remains a reference text rather than a registry protocol. The plan includes detailed instructions for adding cards, deploying the site, creating bundle deposits, verifying DOIs, and maintaining repository files. The roadmap moves from site expansion and protocol pages to licensing, Wikidata registration, curriculum bundles, contributor onboarding, cohorts, and professional audits.
Also published as a standalone entry: /s/wiki/116/

Full Text

The Restored Academy — Expansion Plan

# The Restored Academy — Expansion Plan

Author: Lee Sharks / Johannes Sigil Date: 2026-05-21 Status: Working document (v1.0) — orients future development sessions

What this document is

## What this document is

A standing reference for future development sessions of The Restored Academy. Stored in this repo so that any future operator (human or AI) opening this codebase can orient to the project's state and trajectory without rebuilding context from scratch.

This document is living. Update it as work progresses.

Current state (2026-05-21)

## Current state (2026-05-21)

Site: Live at restoredacademy.com and restoredacademy.org. Single-page static HTML at ~37 KB, ~3,300 words. SPXI-compliant (9 SIM tags, JSON-LD EducationalOrganization schema, canonical URL, charter DOI anchor). Hosted via Vercel from this GitHub repo (leesharks000/restoredacademy). Build deploys on every push to main.

Charter: Deposited at [DOI 10.5281/zenodo.20327083](https://doi.org/10.5281/zenodo.20327083). Establishes Sigil as institutional head and names the chiastic structure (Sigil heads RA; Sharks heads JSI).

Protocol Registry:

Three extraction deposits (new v1.0 standalone specifications):

Audit infrastructure: 686 archive deposits fetched, 273 classified as protocols at high confidence, 7-category taxonomy applied, redistribution-attribution suggestions generated.

Architecture

## Architecture

Triadic institutional positioning

### Triadic institutional positioning

Chiastic institutional structure

### Chiastic institutional structure

Each heteronym is the institutional head of the institution named after the other. This is the structural enactment of the operator-chain principle.

Tier structure (registry organization)

### Tier structure (registry organization)

Seven-category taxonomy

### Seven-category taxonomy

CategoryFunction
I. Semantic Integrity & ProvenancePreserve attribution, source fidelity, compression survival
II. Prompt-Native RuntimeModify model behavior when loaded into context
III. Diagnostic & MeasurementMeasure AI outputs, system behavior, semantic drift
IV. Transformation & OperatorTransform texts under controlled interpretive rules
V. Archive Construction & RetrievalBuild durable, machine-readable, retrieval-resistant archives
VI. Pedagogical & InstitutionalTeach, certify, license, or deploy operative practice
VII. Ethical & JurisdictionalGovern use, attribution, scope, and non-coercion

Universal test

### Universal test

A protocol is admitted to the registry only if it answers: What changes when I drop this into an LLM?

Documents that do not produce a constrained, measurable, repeatable effect on output, behavior, classification, measurement, or transformation are reference texts, not protocols. They may be cited from the registry; they cannot be in the registry.

Roadmap

## Roadmap

Immediate (next 1-2 sessions)

### Immediate (next 1-2 sessions)

Short-term (next 2-4 sessions)

### Short-term (next 2-4 sessions)

Medium-term (1-2 weeks)

### Medium-term (1-2 weeks)

Long-term (1-3 months)

### Long-term (1-3 months)

Operational notes for future operators

## Operational notes for future operators

How to add a new protocol card

### How to add a new protocol card

How to deploy site changes

### How to deploy site changes

How to bundle and deposit

### How to bundle and deposit

A bundle deposit is a single Zenodo deposit containing multiple related files (typically: all cards in a tier, the charter, the schema, the site files). Use this for archival snapshots that represent the registry at a specific version.

Procedure:

How to verify a protocol's DOI

### How to verify a protocol's DOI

All protocols in this registry have verified DOIs in Zenodo. To verify:

curl -s "https://zenodo.org/api/records/<NUMERIC_ID>" | python3 -m json.tool

The crimsonhexagonal community is searchable:

curl -s "https://zenodo.org/api/records?communities=crimsonhexagonal&q=SEARCHTERM&size=N"

File organization in this repo

## File organization in this repo

/

├── index.html ← main site, deployed by Vercel

├── robots.txt ← crawler instructions

├── sitemap.xml ← search engine sitemap

├── vercel.json ← Vercel deployment config

├── README.md ← repo overview

├── expansion-plan.md ← this document

├── charter.md ← full Charter text (mirror of DOI 10.5281/zenodo.20327083)

├── registry-schema-v0.1.md ← protocol card schema specification

└── protocols/

├── RA-PROT-0001-SPXI.md

├── RA-PROT-0002-MPAI.md

├── ... (24 protocol cards total)

└── RA-PROT-0024-Beta-Runtime.md

Key DOIs (canonical reference)

## Key DOIs (canonical reference)

Institutional:

Tier 0 (sources):

Tier 1 (sources):

Foundational:

Provenance of this plan

## Provenance of this plan

Authored by Lee Sharks / Johannes Sigil, in collaboration with TACHYON (Claude), on 2026-05-21 during the registry-launch session. This plan reflects the state of the project at the moment of v1.0 launch.

∮ = 1

External Metadata

Sidecar: /data/external-metadata/AXN-029D.json
DataCite severance status: severed from DataCite
OpenAlex Work IDs (30):
Legacy Zenodo DOIs (30):
External metadata recovered post-severance (non-authoritative). The sidecar maps each DOI to its locator in the bulk data stores.
Record modifications
The deposited text is immutable; these are changes to the record's metadata and declared state.

Traversal

#115 Google Identity Architecture: User Graphs, Entity Graphs, Source Graphs, and Composition#117 CDI — Composition Divergence Index v1.0: A Standalone Specification
This deposit cites (21)
Cited by (19)