# nlm-memory - 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: `pbmagnet4/nlm-memory` - capability: Local-first non-linear memory OS for AI operators. One index across Claude Code, Codex, Cursor, Windsurf, Hermes, OpenCode, Aider, pi, and more — with an editable timeline. - expected_user_outcome: Local-first non-linear memory OS for AI operators. One index across Claude Code, Codex, Cursor, Windsurf, Hermes, OpenCode, Aider, pi, and more — with an editable timeline. ## 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, src/cli/nlm.ts, src/http/app.ts, src/mcp/server.ts, src/core/scheduler/scheduler.ts - **Recall, Classification & Signals**: importance `high` - source_paths: src/core/classifier/hierarchical-classify.ts, src/core/classifier/prompt.ts, src/core/ingest/reclassify-oversized.ts, src/core/scheduler/scan-once.ts, src/core/recall/recall-service.ts - **Data Storage, Adapters & Supersedence**: importance `high` - source_paths: src/core/storage/sqlite-storage.ts, src/core/storage/pg-storage.ts, src/core/storage/sqlite-fact-store.ts, src/core/storage/pg-fact-store.ts, src/core/storage/sqlite-code-exemplar-store.ts - **Deployment, Configuration & Operations**: importance `high` - source_paths: src/install/setup.ts, src/install/claude-code.ts, src/install/codex.ts, src/install/cursor.ts, src/install/windsurf.ts ## Repo Inspection Evidence - repo_clone_verified: true - repo_inspection_verified: true - repo_commit: `2ccdf75250c03efa77378595737b321c2aae36dd` - inspected_files: `README.md`, `package.json`, `docs/backups.md`, `docs/code-signal.md`, `docs/eval-classifier.md`, `docs/eval-recall.md`, `docs/eval-signals.md`, `docs/hooks.md`, `docs/install-verification.md`, `docs/methodology/candidate-recall-vs-ranking-2026-06.md`, `docs/methodology/re-derivation-rate.md`, `docs/methodology/useful-hit-rate.md`, `docs/methodology-recall-baseline.md`, `docs/plans/2026-05-20-fts5-lexical-recall.md`, `docs/plans/2026-05-20-recall-daemon-wedge-fix.md`, `docs/plans/2026-05-20-recall-hook-design.md`, `docs/plans/2026-05-20-recall-hook-implementation.md`, `docs/plans/2026-05-30-factstore-storage-port.md`, `docs/plans/2026-05-31-pg-adapter.md`, `docs/plans/2026-06-10-supersedence-split.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: 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/pbmagnet4/nlm-memory - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 2: Capability evidence risk requires verification - Trigger: README/documentation is current enough for a first validation pass. - 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.assumptions | https://github.com/pbmagnet4/nlm-memory - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 3: Maintenance risk requires verification - Trigger: Project evidence flags a maintenance 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: evidence.maintainer_signals | https://github.com/pbmagnet4/nlm-memory - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 4: Security or permission risk requires verification - Trigger: no_demo - 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: downstream_validation.risk_items | https://github.com/pbmagnet4/nlm-memory - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 5: Security or permission risk requires verification - Trigger: no_demo - 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: risks.scoring_risks | https://github.com/pbmagnet4/nlm-memory - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 6: Maintenance risk requires verification - Trigger: issue_or_pr_quality=unknown。 - 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: evidence.maintainer_signals | https://github.com/pbmagnet4/nlm-memory - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 7: Maintenance risk requires verification - Trigger: release_recency=unknown。 - 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: evidence.maintainer_signals | https://github.com/pbmagnet4/nlm-memory - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.