feature · r2-37-sleep-orchestration
M
5 tags · 9 out · 9 in · 3 artifacts · 1 gaps · 1 corpus docs
How should sleep jobs be scheduled, triggered, ordered, and gated — so offline consolidation (reflection, skill curation, policy recalibration) runs safely with eval-before-promote and never silently changes company shape?
This topic was frozen in the corporate agentic OS research corpus (wave 10) to answer architecture and measurement questions that sit under the locked loop (observe→understand→predict→intervene→resolve→verify→learn). Stage-1 criticality: M. Research/Spec/Platform readiness: R4/S4/P0.
Graph edges for this feature — technologies, category lens, companies, DM.
features/r2-37-sleep-orchestration/README.md
feature missing document-management.md
T37 — Sleep Job Orchestration · ok
features/r2-37-sleep-orchestration/README.md
Research path: features/r2-37-sleep-orchestration