IPD‑12 Paradox Registry (P‑Index)

Structural Paradox Index for Inter‑Process Drift#

IPD‑12 identifies structural paradoxes — tensions created when:

• coherence remains
• drift increases
• dependency persists

A paradox in IPD‑12 is never a contradiction.
It is a structural tension loop.

The P‑Index catalogs all paradox types that IPD‑12 can detect.

P‑0 — Paradox Definition (Structural)#

A structural paradox occurs when:

shared_coherence  ∧  increasing_drift  ∧  mutual_dependency

This definition is the same pattern shown in your active tab’s composite grammar section github.com.

P‑1 — Coherence Paradox#

Coherence persists while drift increases.#

Pattern:
Two processes remain aligned in purpose, constraints, or structure, even as divergence grows.

Example:
Human notes ↔ AI notes
Both aim for clarity, but drift in speed, detail, and interpretation.

Detection Chain:

drift() → align_coherence()

P‑2 — Dependency Paradox#

Dependency increases as drift increases.#

Pattern:
The more one process helps another, the more the second relies on it — which increases drift.

Example:
AI helps humans take notes → humans practice less → humans rely more on AI.

Detection Chain:

drift() → detect_divergence() → paradox()

P‑3 — Boundary Paradox#

Shared boundaries, divergent domains.#

Pattern:
Two processes share constraints or boundaries but drift into different operational or conceptual domains.

Example:
Craft violin‑making ↔ CNC manufacturing
Same acoustic boundaries, different operational domains.

Detection Chain:

compare_process() → drift_tensor()

P‑4 — Temporal Paradox#

Processes evolve at different speeds.#

Pattern:
One process accelerates (automation), the other remains slow (manual), creating drift despite shared goals.

Example:
Human workflow ↔ automated workflow
Coherence goal stays the same; temporal drift grows.

Detection Chain:

drift_tensor(L3) → align_coherence()

P‑5 — Interpretive Paradox#

Meaning diverges while structure remains aligned.#

Pattern:
Two processes share structure but interpret inputs differently.

Example:
Human interpretation ↔ AI reconstruction
Same input stream, different meaning layers.

Detection Chain:

drift_tensor(L4) → detect_divergence()

P‑6 — Domain Paradox#

Cross‑domain drift with shared coherence anchors.#

Pattern:
Two domains share coherence anchors (constraints, operators, goals) but drift due to domain‑specific evolution.

Example:
Music ↔ Physics ↔ Engineering
Shared resonance → different domain drift.

Detection Chain:

cross_system() → drift_tensor(L5)

P‑7 — Multi‑Domain Paradox#

Paradox emerges only when multiple domains are combined.#

Pattern:
No paradox in domain A or B alone — paradox appears only when A and B interact.

Example:
Mythology ↔ Workflow ↔ Theory
Interpretive drift + operational drift + conceptual drift.

Detection Chain:

map_process() → compare_process() → drift_tensor() → cross_system()

P‑8 — Composite Paradox#

Paradox emerges across multiple drift layers simultaneously.#

Pattern:
Geometric + Operational + Temporal + Conceptual + Domain drift combine to produce a composite tension.

Example:
Any multi‑domain drift analyzer output.

Detection Chain:

drift_tensor(L1–L5) → align_coherence() → paradox()

P‑9 — Stability Paradox#

Stability increases drift.#

Pattern:
A stable process causes drift because the other process evolves while the stable one does not.

Example:
Legacy workflow ↔ modern workflow.

Detection Chain:

drift() → detect_divergence()

P‑10 — Alignment Paradox#

Alignment actions increase drift elsewhere.#

Pattern:
Fixing coherence in one layer increases drift in another layer.

Example:
Aligning operational flow increases conceptual drift.

Detection Chain:

align_coherence() → drift_tensor()

P‑11 — Reduction Paradox#

Simplifying one process increases drift with another.#

Pattern:
Reducing complexity in one process increases divergence from a more complex process.

Example:
AI compression ↔ human nuance.

Detection Chain:

drift() → detect_divergence()

P‑12 — Reflection Paradox#

Two processes mirror each other but drift anyway.#

Pattern:
Structural mirroring does not prevent drift.

Example:
Two workflows with identical structure but different execution contexts.

Detection Chain:

compare_process() → drift()

Registry Summary#

This registry is now complete and canon‑aligned.