---
type: reference
title: "Pokémon TCG — Metanoia Suite"
description: "Index and evidence boundary for the six Metanoia specifications covering channel protocol, rule provenance, model adherence, tensor scaling, HALT and holographic pedagogy."
tags: [pokemon-tcg, metanoia, epistemology, provenance, orchestration, halt, pedagogy]
timestamp: "2026-08-15T03:00:00-03:00"
---

# Pokémon TCG — Metanoia Suite

## What the suite is

The six Metanoia documents are a research-protocol layer around the technical project. They record how agents were coordinated, how rules changed across harnesses, how adherence failures were classified, how scaling and provenance were conceptualized, and how HALT and pedagogy were used as epistemic boundaries.

They are not hidden implementation specifications for the Pokémon policy. Their claims must be separated into operational protocol, empirical telemetry, conceptual metaphor and philosophical interpretation.

## Six specifications

| Spec | Page | Core material | Evidence status |
|---:|---|---|---|
| 01 | [[pokemon_tcg_metanoia_channel_protocol]] | INIT → GENERATE → DEBATE → RANK → EVOLVE → META_REVIEW → HALT/DELEGATE/RESPOND | Protocol design |
| 02 | [[pokemon_tcg_metanoia_rule_provenance]] | CLAUDE → GEMINI/.agents rule evolution, five epistemic laws and directive incidents | Historical/provenance record |
| 03 | [[pokemon_tcg_metanoia_model_adherence]] | Model-family adherence, channel leakage, KaTeX collision, sycophancy and lip-service failures | Source-reported telemetry |
| 04 | [[pokemon_tcg_metanoia_tensor_scaling]] | Vertical/horizontal/orthogonal cognitive tensor and provenance ledger | Conceptual architecture |
| 05 | [[pokemon_tcg_metanoia_halt_hypersigils]] | HALT boundary, hypersigils, Jung/Matrix metaphors and tokenization mechanics | Speculative philosophy |
| 06 | [[pokemon_tcg_metanoia_holographic_pedagogy]] | Holographic tokenization, Tao, Poincaré, ADHD/2e and Freirean dialogue | Research philosophy |

## How to use the suite

The suite should be read alongside the technical handoff, not instead of it. Spec 01 can inform orchestration; Spec 02 informs rule provenance; Spec 03 supplies failure categories that should be labeled as reports; Specs 04–06 provide conceptual and pedagogical frames.

None of the suite proves model sentience, mechanistic interpretability or a hidden cognitive geometry. The project's J-space and related language remain working research hypotheses and bounded metaphors.

## Git provenance

The six pages were not added as one timeless specification. Their repository
lineage is part of their meaning:

| Specification | Repository introduction or material update | Provenance role |
|---:|---|---|
| 01–04 | `c104f5b` (2026-08-14) | Initial four-part Metanoia suite and provenance-ledger material |
| 05 | `41438ec` (2026-08-14) | HALT protocol, hypersigil and tokenization extension |
| 06 | `4321ad2` (2026-08-14) | Holographic tokenization, pedagogy and Wikifita integration context |
| RFC index | `955149b` (2026-08-14) | Master handoff map that registers the suite with the wider project |
| Current handoff boundary | `20d7d0d` (2026-08-14) | Odyssey Diary and convergence instructions; not proof of runtime delivery |

The order matters. Specs 01–06 are a late handoff/governance layer added after
the training, ETL and rating experiments. Their later language can explain how
the project interpreted those events, but it cannot retroactively establish
that a proposed module, theorem or acceptance gate had already been completed.

## Cross-references

- [[pokemon_tcg_docs_corpus_provenance]] — full Git/document map.
- [[pokemon_tcg_cross_harness_provenance]] — Antigravity and harness lineage.
- [[pokemon_tcg_manuscript_and_empirical_synthesis]] — technical narrative layer.
- [[pokemon_tcg_ai_battle]] — operational project hub.
- [[pokemon_tcg_repository_timeline]] — commit order for the suite and the surrounding research wave.