# remnic - Doramagic AI Context Pack > Purpose: pre-work context for the user's host AI. This pack does not prove that the project has been installed, run, or validated. ## Project - canonical_name: `joshuaswarren/remnic` - capability: Open-source memory and context for user-aware agents: scoped memory, provenance, retrieval quality, correction, boundaries, evals, and MCP/HTTP access. - expected_user_outcome: Open-source memory and context for user-aware agents: scoped memory, provenance, retrieval quality, correction, boundaries, evals, and MCP/HTTP access. ## Operating Boundaries - Do not claim that the project has been installed, run, called through an API, or used on local files unless separate evidence proves it. - Project facts must come from repo evidence, Claim Graph, or explicit source references. - When a capability is not verified, mark it as unverified instead of completing it as fact. - publish_status: `publishable` - blocking_gaps: none --- ## Doramagic Context Augmentation The following sections strengthen the repository context for a host AI. Human Manual data is a reading route, and pitfall notes become operating constraints. ## Human Manual Outline Usage rule: this is only a reading route and salience signal, not factual authority. Concrete claims must still return to repo evidence or Claim Graph. Host AI hard rules: - Do not treat page titles, section order, summaries, or importance values as factual project evidence. - When explaining the Human Manual outline, state that it is only a reading route or salience signal. - Capability, installation, compatibility, runtime state, and risk claims must cite repo evidence, source paths, or Claim Graph. - **Overview & System Architecture**: importance `high` - source_paths: README.md, docs/architecture/overview.md, docs/architecture/monorepo-structure.md, docs/architecture/embedded-vs-delegate.md, docs/RENAME.md - **Memory Engine & Retrieval Pipeline**: importance `high` - source_paths: packages/remnic-core/src/orchestrator.ts, packages/remnic-core/src/buffer.ts, packages/remnic-core/src/extraction.ts, packages/remnic-core/src/importance.ts, packages/remnic-core/src/lcm/engine.ts - **Platform Integrations & Plugins**: importance `high` - source_paths: packages/plugin-openclaw/src/index.ts, packages/plugin-openclaw/src/bridge.ts, packages/plugin-openclaw/src/runtime-surfaces.ts, packages/plugin-openclaw/src/openclaw-tools/memory-search-tool.ts, packages/plugin-claude-code/hooks/hooks.json - **Configuration, Operations & Troubleshooting**: importance `high` - source_paths: packages/remnic-core/src/config.ts, packages/remnic-core/src/fallback-llm.ts, packages/remnic-core/src/resolve-provider-secret.ts, packages/remnic-core/src/host-embedding-provider.ts, packages/remnic-core/src/local-llm.ts ## Repo Inspection Evidence - repo_clone_verified: true - repo_inspection_verified: true - repo_commit: `593abb4dbd6c1e2ed173187cd206155b4ced6e41` - inspected_files: `Dockerfile`, `README.md`, `package.json`, `pnpm-lock.yaml`, `docs/ARCHITECTURE.md`, `docs/CONVENTIONS.md`, `docs/README.md`, `docs/RENAME.md`, `docs/admin-console.md`, `docs/advanced-retrieval.md`, `docs/agentic-commerce-demo.md`, `docs/api.md`, `docs/architecture/auth-model.md`, `docs/architecture/binary-lifecycle.md`, `docs/architecture/citations.md`, `docs/architecture/embedded-vs-delegate.md`, `docs/architecture/emo-oeo-split.md`, `docs/architecture/enrichment-pipeline.md`, `docs/architecture/extraction-judge.md`, `docs/architecture/graph-reasoning.md` Host AI hard rules: - Without repo_clone_verified=true, do not claim that the source code has been read. - Without repo_inspection_verified=true, do not write README, docs, or package-file conclusions as facts. - Without quick_start_verified=true, do not claim that the Quick Start path has run successfully. ## Doramagic Pitfall Constraints These rules come from Doramagic discovery, validation, or compilation findings. The host AI must treat them as operating constraints, not background notes. ### Constraint 1: Security or permission risk requires verification - Trigger: Developers should check this security_permissions risk before relying on the project: FallbackLlmClient rejects OAuth-only providers (openai) before runtime auth resolution - Host AI rule: Before packaging this project, run the relevant install/config/quickstart check for: FallbackLlmClient rejects OAuth-only providers (openai) before runtime auth resolution. Context: Source discussion did not expose a precise runtime context. - Why it matters: Developers may expose sensitive permissions or credentials: FallbackLlmClient rejects OAuth-only providers (openai) before runtime auth resolution - Evidence: failure_mode_cluster:github_issue | https://github.com/joshuaswarren/remnic/issues/1478 - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 2: Security or permission risk requires verification - Trigger: Developers should check this security_permissions risk before relying on the project: [Windows] QMD probe fails: launchProcess() uses bare spawn() without shell:true — all qmd launch forms (sh/.cmd/JS) error - Host AI rule: Before packaging this project, run the relevant install/config/quickstart check for: [Windows] QMD probe fails: launchProcess() uses bare spawn() without shell:true — all qmd launch forms (sh/.cmd/JS) error. Context: Observed when using node, windows, macos - Why it matters: Developers may expose sensitive permissions or credentials: [Windows] QMD probe fails: launchProcess() uses bare spawn() without shell:true — all qmd launch forms (sh/.cmd/JS) error - Evidence: failure_mode_cluster:github_issue | https://github.com/joshuaswarren/remnic/issues/1476 - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 3: Installation risk requires verification - Trigger: Developers should check this installation risk before relying on the project: plugin-pi: stale ctx error after session replacement/reload (post-await ctx access in event + command handlers) - Host AI rule: Before packaging this project, run the relevant install/config/quickstart check for: plugin-pi: stale ctx error after session replacement/reload (post-await ctx access in event + command handlers). Context: Observed when using node, macos - Why it matters: Developers may fail before the first successful local run: plugin-pi: stale ctx error after session replacement/reload (post-await ctx access in event + command handlers) - Evidence: failure_mode_cluster:github_issue | https://github.com/joshuaswarren/remnic/issues/1481 - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 4: Installation risk requires verification - Trigger: Project evidence flags a installation risk. Review the linked source before relying on this workflow. - Host AI rule: Reproduce the official install and quickstart path in an isolated environment. - Why it matters: May increase setup, validation, or first-run risk for the user. - Evidence: community_evidence:github | https://github.com/joshuaswarren/remnic/issues/1474 - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 5: Installation risk requires verification - Trigger: Project evidence flags a installation risk. Review the linked source before relying on this workflow. - Host AI rule: Reproduce the official install and quickstart path in an isolated environment. - Why it matters: May increase setup, validation, or first-run risk for the user. - Evidence: community_evidence:github | https://github.com/joshuaswarren/remnic/issues/1476 - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 6: Installation risk requires verification - Trigger: Project evidence flags a installation risk. Review the linked source before relying on this workflow. - Host AI rule: Reproduce the official install and quickstart path in an isolated environment. - Why it matters: May increase setup, validation, or first-run risk for the user. - Evidence: community_evidence:github | https://github.com/joshuaswarren/remnic/issues/1481 - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 7: Configuration risk requires verification - Trigger: Project evidence flags a configuration risk. Review the linked source before relying on this workflow. - Host AI rule: Reproduce the official install and quickstart path in an isolated environment. - Why it matters: May increase setup, validation, or first-run risk for the user. - Evidence: capability.host_targets | https://github.com/joshuaswarren/remnic - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 8: Configuration risk requires verification - Trigger: Developers should check this configuration risk before relying on the project: Day Summary cron job does not reconcile model config on plugin startup - Host AI rule: Before packaging this project, run the relevant install/config/quickstart check for: Day Summary cron job does not reconcile model config on plugin startup. Context: Source discussion did not expose a precise runtime context. - Why it matters: Developers may misconfigure credentials, environment, or host setup: Day Summary cron job does not reconcile model config on plugin startup - Evidence: failure_mode_cluster:github_issue | https://github.com/joshuaswarren/remnic/issues/1474 - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 9: Configuration risk requires verification - Trigger: Developers should check this configuration risk before relying on the project: Day Summary cron timezone is not configurable (uses server timezone) - Host AI rule: Before packaging this project, run the relevant install/config/quickstart check for: Day Summary cron timezone is not configurable (uses server timezone). Context: Source discussion did not expose a precise runtime context. - Why it matters: Developers may misconfigure credentials, environment, or host setup: Day Summary cron timezone is not configurable (uses server timezone) - Evidence: failure_mode_cluster:github_issue | https://github.com/joshuaswarren/remnic/issues/1475 - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 10: Configuration risk requires verification - Trigger: Developers should check this configuration risk before relying on the project: Flush plan: models hallucinate 'memory-candidates/' paths and flush-plan.md grows indefinitely - Host AI rule: Before packaging this project, run the relevant install/config/quickstart check for: Flush plan: models hallucinate 'memory-candidates/' paths and flush-plan.md grows indefinitely. Context: Observed when using node, python - Why it matters: Developers may misconfigure credentials, environment, or host setup: Flush plan: models hallucinate 'memory-candidates/' paths and flush-plan.md grows indefinitely - Evidence: failure_mode_cluster:github_issue | https://github.com/joshuaswarren/remnic/issues/1483 - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.