---
type: reference
title: "Pokémon TCG Metanoia Spec 02 — Rule Provenance and Epistemic Evolution"
description: "Timeline and control model for the movement from CLAUDE.md to GEMINI.md and .agents rules, with explicit provenance of operating laws."
tags: [pokemon-tcg, metanoia, provenance, rules, agents, epistemology, handoff]
timestamp: "2026-08-15T03:10:00-03:00"
---

# Pokémon TCG Metanoia Spec 02 — Rule Provenance and Epistemic Evolution

## Rule lineage

Spec 02 records the movement from a `CLAUDE.md`-centered operating contract in the July 23–August 7 period toward `GEMINI.md` and `.agents`-based coordination from August 8 onward. The important fact is not the filename change by itself; it is the evolution of how evidence, tool boundaries, handoffs and failure modes were made explicit.

The project repository's current `AGENTS.md`, `CLAUDE.md` and `GEMINI.md` must be read as live instructions at the time of work. A historical rule document can explain why a constraint exists, but cannot override the current authorized scope.

## Five epistemic laws carried into this project

The suite emphasizes:

1. distinguish observation from inference and hypothesis;
2. preserve provenance through every transformation;
3. prefer explicit failure to silent fallback;
4. keep implementation, design and metaphor in separate layers;
5. stop or delegate when evidence or authority is insufficient.

These laws explain the current Wikifita editorial choices: future RoPEND/MoE material remains visible; database anomalies are not purged; Antigravity reports are labeled; and the Stage 3 mechanism is documented without pretending that a raw transcript proved every causal detail.

## ASD-STE100 and operational clarity

The specification also draws on simplified technical language and controlled instructions. In this project that means naming denominators, source cohorts, reset assumptions, split identity and implementation status in plain terms. It does not mean removing mathematical density from the research documents.

## Directive incidents

The incident table in the source document records failures such as context leakage, unsupported claims, silent fallback and overconfident synthesis. The practical translation for the Pokémon corpus is:

| Failure | Required correction |
|---|---|
| Blueprint presented as shipped | Compare named path and live source before saying “implemented” |
| Tournament number copied without cohort | Preserve game count, opponent set, deck and reset context |
| Handoff summary treated as raw evidence | Trace to code, log, DB or report artifact |
| Data discrepancy hidden by one preferred count | Record all counts and reconcile explicitly |
| Future phase deleted as “not current” | Keep it as deferred/blueprint lineage |

## Primary source

`docs/metanoia/02_rule_provenance_and_epistemic_evolution.md`

## Cross-references

- [[pokemon_tcg_metanoia_suite]] — suite index.
- [[pokemon_tcg_cross_harness_provenance]] — cross-harness rule lineage.
- [[pokemon_tcg_docs_corpus_provenance]] — Git timeline and source roles.
- [[pokemon_tcg_stage3_training_failure_postmortem]] — an incident documented under these laws.