Scale contradiction holding periods by cascade depth — one week for shallow, one month+ for deep

Why This Is a Rule

The cascade test (Use the cascade test — 'If I resolved this, what else changes?' — to distinguish surface from deep contradictions) classifies contradictions by depth — how many downstream beliefs would change if the contradiction were resolved. But classification without a response protocol leaves you with a diagnosis and no treatment plan. Holding periods bridge this gap: they specify how long to sit with a contradiction before attempting resolution, scaled to the contradiction's structural depth.

The scaling logic is straightforward. A shallow contradiction (1-3 downstream dependencies) has a limited blast radius. You can resolve it quickly because the consequences of a wrong resolution are contained — you'll update a few beliefs. A deep contradiction (10+ dependencies) has system-wide consequences. Resolving it prematurely risks cascading errors through your entire belief network. The incubation period lets your subconscious pattern-matching work on the problem while you accumulate evidence from multiple contexts.

This is Poincaré's incubation principle applied systematically: complex problems benefit from alternating periods of conscious effort and unconscious processing. The holding period creates the conditions for incubation while preventing the premature closure that kills insight.

When This Fires

• After applying the cascade test (Use the cascade test — 'If I resolved this, what else changes?' — to distinguish surface from deep contradictions) and determining a contradiction's depth
• When you feel pressure to resolve a contradiction immediately — check cascade depth first
• During contradiction management when deciding how long to let tensions sit
• When someone asks "have you decided yet?" about a deep contradiction

Common Failure Mode

Applying uniform urgency: treating all contradictions as equally time-sensitive. "I found a contradiction, I need to resolve it today." For deep contradictions, this produces premature, surface-level resolutions that miss the structural insight the incubation period would have revealed. The discomfort of holding a contradiction is the incubation process working — don't short-circuit it.

The Protocol

(1) Apply the cascade test (Use the cascade test — 'If I resolved this, what else changes?' — to distinguish surface from deep contradictions) to determine depth. (2) Set holding period: low cascade (1-3 dependencies) → 1 week. Medium cascade (4-9 dependencies) → 2-4 weeks. High cascade (10+ dependencies) → 1 month or longer. (3) Mark the contradiction in your knowledge system with the holding period end date. (4) During the holding period, capture incubation notes (During a holding period, capture incubation notes on each surfacing — what triggered it, what you noticed — without resolving) without attempting resolution. (5) When the holding period ends, assess readiness: can you articulate the missing variable or synthesis? If yes → resolve. If no → extend (When a holding period expires without clarity, extend it — premature resolution defeats incubation's purpose).