Domain: Nightly consolidation (sleep)

Entrypoint: `POST /api/admin/consolidate`

Scheduler: pg_cron + pg_net in Postgres (`scripts/ensure-sleep-cron.mjs`), default 0 2 * * * in CONSOLIDATION_CRON_TZ (UTC unless set).

Sleep phases

Phase	Analog	Jobs
DeepSleep	Slow-wave / declarative + pruning	`salience_compute`, `ontology_prune`, `repair_canonical_entity_types`, `dedup_canonical_entities`, `repair_entity_relations`
REM	Integration + procedural	`community_detection`, `community_summaries`

Orchestrator: `src/lib/server/consolidation/runner.ts`

Per-user work runs inside withDbUser so RLS applies.

Awake vs asleep

Awake: capture enrichment, retrieval reconsolidation (salience bumps on access), ontology profile refresh every 10th thought.
Asleep: nightly consolidation above; salience decay/open-loop floors recomputed from elapsed wall-clock time (not per-run ticks). Idempotent global run tracked in consolidation_run.

Community contract

Community detection clusters over ENTITY_RELATES graph edges only (edgePolicy: entity_relates_only); co-mention edges are visualization support, not clustering input.
Level semantics are fixed:
- L3 leaf = tight operational groups
- L2 = sub-domain thematic lanes
- L1 = domain-level structure
- L0 root = broad worldview partitions
Before writing communities, detection computes graph-health diagnostics (components, isolation ratio, relation density) and marks low-confidence runs when relation structure is too weak.

Environment

Variable	Required	Purpose
`ADMIN_CONSOLIDATION_KEY`	Yes (for cron)	`X-Admin-Key` on consolidate endpoint
`DATABASE_ADMIN_URL`	Yes (for cron bootstrap)	Superuser URL for pg_cron schedule + run ledger
`CONSOLIDATION_INTERNAL_URL`	Yes (compose)	App URL reachable from DB (`http://app:3000`)
`CONSOLIDATION_CRON_SCHEDULE`	No	Cron expression (default `0 2 * * *`)
`CONSOLIDATION_CRON_TZ`	No	IANA timezone for schedule + run-night idempotency (default `UTC`)

Manual trigger

curl -sf -X POST "$ORIGIN/api/admin/consolidate" \
  -H "X-Admin-Key: $ADMIN_CONSOLIDATION_KEY" \
  -H "Content-Type: application/json"

Single user:

curl -sf -X POST "$ORIGIN/api/admin/consolidate" \
  -H "X-Admin-Key: $ADMIN_CONSOLIDATION_KEY" \
  -H "Content-Type: application/json" \
  -d '{"userId":"USER_ID"}'

Follow-ups (not implemented)

ontology_proposal generation from clustering
Declarative fact merging
Stale community summary refresh when community.updatedAt > summary.generatedAt
Persist graph edge fingerprint at detection time for finer staleness (same entity IDs, rewired edges)