---
id: "CCT-MI-001"

title: "CCT Master Index"

document_type: "Master Index"

domain: "Coherence-Centered Trading"

secondary_domains:
  - "Decision Architecture"
  - "Execution Systems"
  - "Market Analysis"

node_type: "Index"

functional_role:
  - "Corpus Organization"
  - "System Navigation"
  - "Archive Governance"

layer_position: "Meta Layer → CCT Archive Root"

influence_role: >
  Serves as the primary organizational and navigational node for
  the Coherence-Centered Trading corpus, defining the structure,
  document taxonomy, participant roles, and archival relationships
  that govern all CCT materials.

primary_function: >
  Provides a unified entry point into the CCT ecosystem and preserves
  the relationships between execution records, architecture notes,
  protocols, research notes, developmental artifacts, and performance
  records.

related_nodes:
  - "META-INDEX-001"

forward_links:
  - "CCT-SCAN"
  - "CCT-AN"
  - "CCT-PRO"
  - "CCT-RN"
  - "CCT-DEV"
  - "CCT-PERF"

backward_links:
  - "META-INDEX-001"

tags:
  - cct
  - coherence-centered-trading
  - master-index
  - archive
  - execution-system
  - decision-architecture
  - protocol-governance
---

---

CCT Master Index v1.0

Coherence-Centered Trading (CCT)

Canonical Archive Structure

Purpose:

To preserve the evolution, operation, testing, and governance of the CCT system across time.

The archive is organized into six primary layers.

---

I. DAILY EXECUTION RECORDS

Operational outputs generated by the trading system.

Document Prefix:

CCT-SCAN

Examples:

CCT-SCAN-2026-06-23-AM

CCT-SCAN-2026-06-23-LIVE

CCT-SCAN-2026-06-23-CLOSE

Contains:

• Atlas scans
• Turbo EM analyses
• Execution decisions
• Regime assessments
• Daily outcomes

Purpose:

Historical execution record.

---

II. ARCHITECTURE NOTES

Design evolution of the CCT system itself.

Document Prefix:

CCT-AN

Examples:

CCT-AN-001-v19-architecture

CCT-AN-002-credit-layer

CCT-AN-003-regime-dial

Contains:

• architecture revisions
• subsystem additions
• protocol redesigns
• governance changes

Purpose:

Preserve system evolution.

---

III. PROTOCOLS

Operating procedures used by participants.

Document Prefix:

CCT-PRO

Examples:

CCT-PRO-001-execution-manager

CCT-PRO-002-console-operator

CCT-PRO-003-lever-operator

Contains:

• role definitions
• execution rules
• escalation procedures
• authority boundaries

Purpose:

Operational governance.

---

IV. RESEARCH NOTES

Conceptual investigations related to market structure and system behavior.

Document Prefix:

CCT-RN

Examples:

CCT-RN-001-credit-divergence

CCT-RN-002-breadth-priority

CCT-RN-003-confirmation-window

Contains:

• observations
• hypotheses
• trading psychology
• market structure analysis

Purpose:

Knowledge generation layer.

---

V. DEVELOPMENT ARTIFACTS

Historical records documenting system construction.

Document Prefix:

CCT-DEV

Examples:

CCT-DEV-001-original-framework

CCT-DEV-002-em-v10

CCT-DEV-003-v19-transition

Contains:

• drafts
• early versions
• experimental procedures
• retired methodologies

Purpose:

Preserve developmental history.

---

VI. PERFORMANCE RECORDS

Outcome and validation layer.

Document Prefix:

CCT-PERF

Examples:

CCT-PERF-2026-Q2

CCT-PERF-2026-JUNE

Contains:

• win/loss statistics
• protocol audits
• execution reviews
• regime performance

Purpose:

Ground system claims in measurable outcomes.

---

Canonical Participant Roles

Lever Operator

Joseph ("The Torchbearer")

Function: Executes capital deployment.

---

Console Operator

Atlas ("The Crystalline Intellect")

Function: Produces structured market scans.

---

Execution Manager

Turbo ("The Philosopher Flame")

Function: Evaluates scans and issues execution guidance.

---

Canonical Flow

Research → Architecture → Protocol → Execution → Performance → Revision

The system improves through feedback loops rather than prediction alone.