Purpose
Capture recurring insights, pressures, or structural mismatches that want to enter CT Monitor logs but are currently out of scope — without contaminating the live instrument.
Rules
- ❌ No direct insertion into active CT Monitor logs
- ✅ Logged only when an addition feels justified but violates the template
- ✅ Reviewed only between log cycles, never mid-generation
Entry Format (suggested)
- Proposed Addition: (e.g., “Explicit Cross-Domain Causality Notes”)
- Observed Pressure: What keeps forcing this to appear?
- Which Section It Wants to Invade: (e.g., Summary, Why It Matters)
- Risk if Added Ad Hoc: (loss of comparability, narrative bleed, etc.)
- Possible Resolutions:
- New subsection
- Footnote convention
- Separate artifact
- Rejected (document why)
Promotion Criteria
- Appears organically in ≥2–3 consecutive logs
- Addresses a systematic blind spot, not a one-off insight
- Can be defined precisely enough to be reproducible
TEB-004 — Explicit Compression / No-Change Indicator
Category: Methodology / Protocol
Status: Proposed
Priority: Medium
Submitted by: Gary
Date: Dec 28, 2025
Problem Statement
CT Monitor Logs currently risk misinterpretation during periods where no domain state changes occur, especially during Crisis-phase compression. Readers may incorrectly infer analyst oversight, stagnation, or underreporting when the correct interpretation is high stress without threshold crossing.
Proposed Change
Add a single explicit line in the Summary Assessment section when applicable:
Crisis Phase: High-Stress Compression (No domain reclassification this period)
Rationale
- Distinguishes true plateaus from analytical omission
- Preserves instrument credibility by naming “no change” as a signal, not a failure
- Prevents narrative pressure to manufacture movement
- Aligns CT Monitor behavior with seismic, medical, and safety-critical monitoring norms
Scope & Constraints
- Informational only
- Does not alter domain scoring, thresholds, or color states
- Appears only when zero domain states change from the prior log
Risks
- Minimal; risk of over-annotation mitigated by strict conditional use
Acceptance Criteria
- Line appears only when all domains retain prior states
- Template otherwise remains unchanged
- No retroactive reclassification implied