lilmgenius/paperthin

mandela

Audit any eval, metric, experiment, or benchmark for leakage — does external ground-truth enter independently, or are the model, scorer, and designer just confirming a result no outside truth ever produced?

Ver código-fonte
Documento original do Skill

Renderizado do repositório de origem, preservando títulos, exemplos, código, tabelas, links e imagens.

Audit a validation for leakage: does outside ground-truth actually enter, or is everyone confirming a result no one independently produced?

Goal

The name is the Mandela Effect — a whole population confidently remembers something that never independently happened; a leaky validation is the same shape. Walk the 8 patterns below. mandela checks one thing: whether a validation is independent, or whether the designer, model, and scorer are only confirming each other.

Workflow

  1. Identify the validation (eval / metric / experiment / holdout / "how we'll know"). Name its components — what plays model, scorer, designer, dataset.
  2. Ask the core question: does external ground-truth enter independently?
  3. Test the validation against all 8 patterns below (some apply only to certain components — a human subject, a scorer); report only the ones that fire, each by name.
  4. Give the independent-ground-truth fix for each hit.

The 8 leakage patterns

  1. Recall, not reason — a memorized answer recited instead of one actually derived; the system already knows the result it is supposedly computing.
  2. Wrong null hypothesis — an ablation that removes a surface label but not the underlying signal the system actually exploits, so the "control" still leaks.
  3. Shared hallucination — two components verifying each other; circularity reported as a number.
  4. Tautology — a scorer grading buckets it drew itself.
  5. Verifier = designer — a private, unreproducible recipe in a holdout's clothes.
  6. Shared-pool bias — train and holdout drawn from one labeler pool, so one bias enters both sides.
  7. Frame injection — a question that hands the subject the hypothesis.
  8. Demand characteristics — measured subjects who know they're being measured.

Rules

  • Subtlety that bites twice: you can blind the output value and still leak the collection recipe.
  • Read-only — name the leak and the independence fix; don't rewrite the experiment.
  • For a high-stakes validation, you may add one independent fresh-context auditor (N=1) handed only the validation design, not this session's reasoning, to re-run the 8-pattern taxonomy blind; the default remains same-session and read-only.

Verification

Turn mandela on this audit:

  1. Run patterns #3–#5 on yourself: are you a scorer grading buckets you drew (Tautology, #4)? is the verifier the designer (#5)? is your verdict a shared hallucination with the design's own claims (#3)?
  2. Could a reader who didn't run the audit reach your verdict from the cited evidence alone — independent ground-truth?
  3. The report names the root, not a laundry list.
do mesmo repositório

Mais Skills

Todos os Skills
lilmgenius
Comunidade

shower

Cold-read the artifact you're focused on from a fresh, zero-context sub-session to confirm it stands on its own — a shower-thought reset for accumulated session bias. Use when a long session has worn away your fresh eyes and you can no longer tell whether the artifact in focus is clear to someone with no prior context; before a handoff, publish, or merge; or when you want a clean-room comprehension smoke test. Spawns a separate context-free reviewer; it diagnoses, it does not fix.

instalações
1
GitHub Stars
1,1 mil
Atualizado
27 de set.
lilmgenius
Comunidade

re0-plan

Open a paperthin iteration's casebook before re0-loop's first turn — seeded with real content the moment the folder exists, never an empty directory. User-invoked, paperthin-only: assumes the full skill package installed. Run when opening a new build cycle in this repo.

instalações
1
GitHub Stars
1,1 mil
Atualizado
6 de set.
lilmgenius
Comunidade

re0-release

Walk a pending change through this repo's shipping and releasing checklist end to end, then tag and publish once confirmed. User-invoked: run it when you've decided to ship.

instalações
1
GitHub Stars
1,1 mil
Atualizado
6 de set.
lilmgenius
Comunidade

re0-upgrade

Bring your installed paperthin skills up to the full current catalog in one step: retire what's been renamed, add every skill you don't have yet, and refresh the rest, all shown and confirmed before anything changes.

instalações
1
GitHub Stars
1,1 mil
Atualizado
6 de set.