dream-state

Dream State — hosted memory review

Use the current app model for assessment, MCP tools for data operations and the app's own scheduler for requested recurring runs. No external LLM API key, separate model service or operating-system cron is needed. Runs consume the host app's normal usage. This workflow does not call the native server-side Dream State engine, retag identity documents or merge graph nodes. Report the operations actually performed instead of claiming the native engine ran.

Preview

1. Establish the project/topic/space the user wants reviewed. An ambiguous cleanup request means preview. Do not fan out across all projects.
2. Use kumiho_memory_retrieve for at most five relevant items initially, with the specified project and space filters. Inspect returned published revisions with kumiho_get_revision_by_tag before judging duplicates or contradictions.
3. Report candidate pairs, their krefs, evidence and uncertainty. Age alone is not a reason to retire a memory; distinguish proposals, accepted decisions and later corrections. Keep useful differences and provenance visible.
4. Preview performs reads only. Do not call space profiling merely to preview: that tool can persist results. No consolidation, decomposition, tagging or retirement is authorized by a preview request.

Apply approved changes

Show the exact changes and obtain authorization for each affected item unless the user already supplied those exact changes. Native published-item safeguards are not automatically supplied by this manual path, so do not use a broad "clean up" request to authorize bulk retirement. Never retire all copies of information.

• Use kumiho_memory_reflect for a user-approved correction with relevant source_krefs, revises set to the corrected memory's kref, its memory type and language, the subject restated, and discover_edges: false, so it becomes a new revision of that memory. If you cannot tell which memory to revise, save it normally; a result that is a separate item leaves the old memory recalled until its approved retirement. Omit session ID initially and follow a returned session_required ID for this conversation only.
• Use kumiho_deprecate_item only for the specifically approved item kref and report the result. Retirement excludes it from normal recall; it is not permanent erasure. Do not clear chat buffers or run unexposed tools as a substitute.