𝌋

Cadence Playground

TD613 repository membrane — playful first, rigorous when reached for
Law: never let the interface say in prose what interaction should make undeniable
Repo: not loaded

Playground

Voice A
Voice B
Cadence similarity
—
surface pull between the two voices
Recognition pressure
—
how much a reader might feel “this is the same hand”
Opacity drift
—
how much the second voice escapes the first
Personas are cadence attractors, not costumes. They should reveal what persists, not dress it up as mystery.
The browser is not the final epistemic authority. Canonical analysis enters through file import, not browser reinvention.
No canonical analysis loaded.
Repository spine
Document view
Use START_HERE as the jump point.

1. README.md
2. docs/00_FOUNDING_AXIOMS.md
3. docs/04_UI_UX_DOCTRINE.md
4. docs/05_ANTI_DELIVERABLE_LANE.md
5. schemas/analysis_output.schema.json
6. schemas/persona_v2.schema.json

Grammar panel

Academic rigor arrives after recognition, not before.
The panel is tied to the repository doctrine in README.md, docs/00_FOUNDING_AXIOMS.md, docs/04_UI_UX_DOCTRINE.md, docs/05_ANTI_DELIVERABLE_LANE.md, and the two schema anchors named in START_HERE.txt. It teaches through the comparison event first, then lets you reach for the grammar. See fileciteturn39file0.

Recognition afterimage

Repository-integrated doctrine surfaces only after play.
Compare two voices first. The interface should make something undeniable before it starts explaining itself.

Source classes

No silent upgrades.
EXPLORATORY

Browser-born

playable, local, non-canonical
CANONICAL

Core-attested

imported from protected analysis JSON
LEGACY

Incomplete provenance

continuity held, certainty withheld