Run one repository-managed bounded KB Dream evidence pass as the second phase of local maintenance or as an explicit diagnostic. Dream has no independent schedule and never owns Sleep consolidation, ordinary retrieval, or trusted-card maintenance.
Run the repository-managed Khaos Brain organization contribution pass. Use only when a user or automation explicitly asks to export local shareable KB cards into a validated organization repository; no-op in personal mode or unvalidated organization settings.
Run the repository-managed Khaos Brain organization maintenance cycle. Use only when a user or automation explicitly asks to inspect, review, or maintain a validated organization KB repository and this machine has opted into organization maintenance; this is the organization exchange cycle, not ordinary local KB Sleep.
Run the repository-managed automatic local maintenance cycle. Use only for explicit local maintenance or the scheduled KB Sleep automation, not ordinary retrieval or active-task write-back.
Open the local Khaos Brain desktop card browser for human review. Use when the user asks to open, show, view, inspect, or create a human-facing entry for the Khaos Brain UI, desktop app, card browser, or Windows shortcut. Do not use this for AI KB retrieval or feedback; use the predictive KB retrieval workflow for…
Apply one transactional Khaos Brain software update only after the user explicitly requests it in the current conversation. Never activate from UI status, persisted state, a scheduler, install health, or automated assurance.
Retrieve relevant entries from the local predictive knowledge base as a lightweight preflight for repository work. Use route-first retrieval: infer the task direction, then search by domain path and cross-index before relying on flat keyword matching. In Codex, prefer a scout sidecar before non-trivial work and a…
Review Khaos Brain organization KB maintenance proposals, including card-and-Skill bundles, shared Skill safety, evidence quality, privacy boundaries, and GitHub auto-merge readiness. Use as a review lens for approving, rejecting, merging, splitting, or promoting organization KB candidates or organization Skill…
Use to generate canonical bad cases, Cartesian combinations, oracles, coverage shards, and receipts from a declared finite boundary, family seed, payload, transition, model mesh, coverage universe, or observed-problem backfeed.
Use when a locally green FlowGuard model needs topology-grounded future-use hazard review for broad claims, business paths, old/new disposition, side effects, terminals, loops, external boundaries, or parent/child compression.
Use when an existing large script, module, package, command, public API, facade, config surface, or plugin entrypoint split needs model-derived ownership, dependency, compatibility, parity, and release gates.