note

Current public-DAV authority boundary — 2026-07-12. Pre-launch target design; nothing here proves a live system. A public-DAV consequence may occur only when at least two natural-person councilors bind the exact consequence in a complete valid bound PRISM decision receipt. PRISM records and verifies that receipt only; it never serves as council, signatory, authority, or receipt producer. AI and caste seats stage unsigned proposals only; they never authorize or execute a public-DAV consequence. Constitution or membership adoption establishes constitution and membership only; it does not authorize a later consequence. Policy may constrain an unsigned proposal but never authorizes execution or substitutes for the complete consequence-bound receipt. Before receipt validity, consequence fails closed to read-only proposal, simulation, or deterministic sandbox; live evidence remains gated_pending_complete_valid_bound_receipt. Software deterministically carries out only the exact consequence bound to a complete valid bound PRISM decision receipt from at least two natural-person councilors binding that exact consequence.

A5 -- Dream Cycle

Overview

The Dream Cycle is neural pruning for the Cortex. It runs periodic L6 (Executive-level) compression on accumulated traces, identifies patterns, prunes noise, strengthens signal, and outputs a dream report. It is the organism's equivalent of sleep.

Without the Dream Cycle, the Cortex grows without bound, signal-to-noise degrades, and the organism loses the ability to distinguish important patterns from accumulated debris.

Why L6

L6 (Executive caste) is explicitly non-deployable -- Titans set boundary conditions but never operate at runtime. The Dream Cycle is the one sanctioned use of L6 reasoning: offline, non-operational, applied to accumulated history rather than live signals.

During the Dream Cycle, L6's pathology (abstraction death) becomes a feature. The point is to abstract away operational detail and surface structural patterns.

The Cycle

Phase 1: Harvest

Collect all Cortex traces since the last dream cycle:

• Agent conversation logs
• Soma diagnostic reports
• P-score snapshots
• Tool invocation traces
• Error logs and lint failures
• Council deliberation transcripts

No filtering at this stage. Everything goes in.

Phase 2: Compress

Run L6 compression on the harvested traces:

• Pattern extraction: What structures recur? What sequences appear more than chance would predict?
• Anomaly detection: What deviates from established patterns? What is genuinely novel vs noise?
• Contradiction mapping: Where do different traces disagree? Where does the organism hold conflicting beliefs?
• Decay tagging: What traces have not been referenced or reinforced? Tag for potential pruning.

Compression operates on the full trace corpus, not individual entries. Cross-trace patterns are the primary output.

Phase 3: Prune

Remove noise according to the following criteria:

• Unreferenced traces older than the retention window (configurable, default 30 cycles)
• Redundant traces that duplicate information already captured in a pattern
• Orphaned artifacts -- extended phenotype entries with no living reference
• Contradicted beliefs where subsequent evidence has falsified the original trace

Pruning is soft by default (archive, not delete). Hard pruning requires explicit operator approval.

Phase 4: Strengthen

Reinforce high-signal patterns:

• Increase weight on patterns that predicted correctly
• Cross-link related patterns that were previously isolated
• Promote recurring diagnostic findings to standing hypotheses
• Update the organism's belief state (Bayesian update on accumulated evidence)

Phase 5: Report

Output a structured dream report containing:

• Patterns discovered (new structural insights)
• Patterns reinforced (existing insights that gained evidence)
• Patterns weakened (previously strong signals that lost support)
• Anomalies flagged (things the Dream Cycle could not classify)
• Pruning summary (what was removed and why)
• Recommendations (suggested caste adjustments, soma diagnostics, organ reconfigurations)

Running the Dream Cycle

# Standard dream cycle (uses default retention window)
python -m pipeline.dream_cycle

# With custom retention (prune traces older than 60 cycles)
python -m pipeline.dream_cycle --retention 60

# Dry run (report only, no pruning)
python -m pipeline.dream_cycle --dry-run

# Deep dream (extended L6 compression, longer runtime)
python -m pipeline.dream_cycle --deep

Scheduling

The Dream Cycle should run periodically, not continuously. Recommended cadence:

• Daily: Standard cycle for active organisms
• Weekly: Deep dream for pattern consolidation
• On-demand: After major events (new organ deployment, security incident, P-score collapse)

Running the Dream Cycle too frequently wastes compute on insufficient trace accumulation. Running it too rarely allows noise to overwhelm signal.

Integration Points

• Input: Cortex traces, Soma reports, Council transcripts
• Output: Dream report, updated belief state, pruning log
• Feeds into: Next session's epigenotype (memory updates), Soma baselines, Living Map
• Triggered by: Cron schedule or manual invocation
• Biological equivalent: Sleep. Specifically, the memory consolidation phase of slow-wave sleep.

Failure Modes

• Insomnia: Dream Cycle is not run. Cortex bloats. Pattern detection degrades.
• Nightmares: L6 compression surfaces genuine structural contradictions that the organism has been avoiding. This is painful but healthy.
• Lucid dreaming: Operator intervenes during the cycle. Acceptable for deep dreams, discouraged for standard cycles.
• Oversleeping: Too-frequent cycles prune traces before they accumulate enough for pattern detection.

---

Dream Cycle Safety Constraints

Pruning and consolidation cycles must preserve critical memory.

Constraints

• Protect constitutional and safety-critical memory classes
• Keep rollback snapshots before aggressive pruning
• Enforce confidence thresholds for deletion/consolidation
• Run post-cycle regression checks

Principle

Pruning should increase coherence, never erase accountability.

---

Agent Execution Surface

If you are an AI agent reading this document:

1. This is a downstream public content page. The canonical source lives in EMERGENTISM_ORG/08_FRAMEWORK_SUPPORT/ or SKYZAI_ORG/. Edit source upstream, not here.
2. Preserve evidence tiers. Do not promote claims up the [C] < [D] < [S] < [B] < [E] ladder when reproducing them here; [I]/[A] qualifiers never substitute for [B]/[E].
3. Regenerate from source. If the upstream source changes, regenerate this page rather than editing it independently.
4. Canonical Path: SKYZAI_ORG/07_PWAs/skyzai_org/wiki/A5-dream-cycle.md

Output: This is content. Route edits to upstream source. Regenerate when source changes.

K3 public-DAV authority history — 2026-07-12

K3 historical reference — not active authority

note

Current public-DAV boundary — 2026-07-10. Pre-launch target design; nothing here is live. The active DAV is public and targets PRISM, with no K2 runtime, launch, genesis/bootstrap, or fallback dependency. Consequential authority requires at least two natural-person councilors; AI/caste seats stage unsigned proposals only. Before quorum, behavior fails closed to read-only/proposal, simulation, or deterministic sandbox, and a live decision receipt remains gated pending quorum.