omo-memory 0.1.14 → 0.1.15

package/docs/adapter-integration.md

@@ -1,6 +1,6 @@
 # Adapter Integration
 
-OMO Memory is the shared local work ledger for OMO adapters. It is host-neutral: lazycodex, omo-on-opencode, lfg, and future adapters all write summaries, decisions, QA evidence, task state, and handoffs to the same project-local SQLite database at `<project-root>/.omo/memory/state.sqlite` by default.
+OMO Memory is the shared local session/work/event ledger for OMO adapters. It is host-neutral: lazycodex, omo-on-opencode, lfg, and future adapters all write summaries, decisions, QA evidence, task state, and handoffs to the same project-local SQLite database at `<project-root>/.omo/memory/state.sqlite` by default.
 
 No full transcript capture by default. Do not store API keys, tokens, `.env` contents, auth files, raw tool logs, auth headers, cookies, or any other secret-bearing material.
 
@@ -118,7 +118,7 @@ During the session, hooks should write concise user-action summaries, task state
 }
 ```
 
-This package is the local MCP-to-SQLite router. It does not scrape host transcripts, store assistant output, or centralize cloud state. Hosts and adapters must call the MCP tools at their own lifecycle points.
+This package is the local MCP-to-SQLite router. It does not scrape host transcripts, store assistant output, or centralize cloud state. Hosts and adapters must call the MCP tools at their own integration points.
 
 Retrieval is opt-in or intent-gated:
 
@@ -142,51 +142,28 @@ Use these tools:
 - `memory_global_scan`
 - `memory_global_migrate`
 - `memory_global_list`
-- `memory_ontology_candidates`
-- `memory_ontology_extract`
-- `memory_ontology_score`
-- `memory_ontology_promote`
-- `memory_ontology_demote`
-- `memory_ontology_supersede`
-- `memory_ontology_recall`
+
 
 CLI updates: normal CLI commands automatically launch a quiet background `npm install -g omo-memory@latest` at most once per day. MCP startup intentionally does not auto-update because stdout/stderr must remain reserved for the protocol. Hosts that need pinned installs should set `OMO_MEMORY_AUTO_UPDATE=0` in the CLI environment.
 
-Global migration is copy/import only. Adapters may scan for existing project-local `.omo/memory/state.sqlite` databases and import them into a user-selected global SQLite file, but they must preserve source DBs and retain source provenance in the global store.
+Global migration is copy/import only. Adapters may scan for existing project-local `.omo/memory/state.sqlite` databases and import their event/session/handoff ledgers into a user-selected global SQLite file, but they must preserve source DBs and retain source provenance in the global store.
 
-Global migration also materializes an aggregate OMO schema view inside the global SQLite file. This lets existing ontology extraction, retention scoring, recall, and OpenTUI graph code operate on integrated cross-project events while `global_*` tables retain source database provenance.
+Global import is an event-log surface, not an ontology, graph, concept-extraction, retention-scoring, or curated durable-memory layer.
 
-Example global second-brain flow:
+Example global event import flow:
 
 ```sh
 omo-memory global scan --root /Users/ilseoblee/workspace
 omo-memory global migrate --root /Users/ilseoblee/workspace --global-db ~/.omo/memory/global.sqlite
-OMO_MEMORY_DB=~/.omo/memory/global.sqlite omo-memory ontology candidates
-OMO_MEMORY_DB=~/.omo/memory/global.sqlite omo-memory ontology score
-bun --version
-omo-memory graph tui --db ~/.omo/memory/global.sqlite --query linaforge
+omo-memory global list --global-db ~/.omo/memory/global.sqlite
+OMO_MEMORY_DB=~/.omo/memory/global.sqlite omo-memory recall --query linaforge
 ```
 
-`graph tui` requires `bun` on `PATH` for the OpenTUI terminal renderer. Other CLI and MCP commands run on Node.
-
-Lifecycle commands:
-
-- `memory_ontology_candidates`: derive candidate terms from concise summaries.
-- `memory_ontology_extract`: explicitly extract candidates from one summary/event.
-- `memory_ontology_score`: recompute deterministic scores and retention classes.
-- `memory_ontology_promote`: curate a concept into durable memory.
-- `memory_ontology_demote`: lower a durable memory's retention class.
-- `memory_ontology_supersede`: preserve the old memory and create a replacement.
-- `memory_ontology_recall`: retrieve ontology-backed memories only for an explicit query.
+Unavailable surfaces:
 
-OpenTUI graph controls:
-
-- `q`: quit.
-- `Up` / `Down`: move selected concept.
-- `Tab`: move to the next concept.
-- `/` or `f`: focus filter input when supported by the terminal runtime.
-
-The graph UI is local terminal UI. It does not require a browser, web server, cloud account, or vector service.
+- `memory_ontology_*` MCP tools are absent.
+- `omo-memory ontology ...` CLI commands are unknown.
+- `omo-memory graph tui` is unknown.
 
 Example session start:
 
@@ -218,59 +195,10 @@ Example QA evidence:
 - Do not read or record `.env`, auth files, tokens, cookies, API keys, bearer headers, or raw secret-bearing logs.
 - Store sanitized summaries and evidence references instead of full logs.
 - Host-specific values may appear only in small redacted metadata payloads and must not require schema branches.
-- Export and purge are explicit lifecycle commands; purge requires explicit confirmation.
-
-## Ontology Schema Boundary
-
-OMO Memory's chronological ledger remains authoritative: sessions, events, and handoffs record what happened in a project. The ontology schema is an additive layer for durable memory derived from that ledger:
-
-- `concepts` stores vocabulary entries such as project terms, practices, tools, and recurring ideas.
-- `relations` stores typed links between concepts, decisions, events, sessions, and handoffs.
-- `durable_memories` stores approved long-term facts, preferences, and working rules.
-- `decision_records` stores important choices with rationale, evidence, status, reversibility, and provenance.
-
-Adapters must treat ontology rows as curated local memory, not as raw capture. Do not write full transcripts, raw logs, `.env` contents, auth files, cookies, bearer headers, or secret-bearing payloads into ontology tables. User-authored text must pass through the same redaction boundary used by event and handoff writes before it is promoted into durable memory.
-
-The ontology layer is intentionally not a new adapter surface by itself. CLI and MCP commands should continue to call shared core functions, and future concept/decision commands must not create host-specific schemas or side databases.
-
-## Retention Scoring Policy (Deterministic Contract)
-
-Retention classification is strictly deterministic. There is no ML, embeddings, or hidden model. A pure function maps explicit signals to a numeric score and then to one of five classes.
-
-Classes (in ascending durability):
-
-- `forget`: score < 30 (or after decay/contradiction). Safe to drop.
-- `temporary`: 30 <= score < 50. Short-term context only.
-- `working`: 50 <= score < 75. Active task/iteration memory.
-- `durable`: 75 <= score < 90. Cross-session value; survives typical decay.
-- `permanent`: score >= 90, or any manually pinned item. Manual pin is a hard override.
-
-Manual pin rule (critical): an item with `manualPin: true` is always classified `permanent` regardless of raw score, age, or frequency. Decay jobs and age-based expiration MUST NOT remove or downgrade pinned permanent memory; only explicit supersede/demote/purge may change it.
-
-### Score Formula (pure, exposed)
-
-Exported constants (see `src/retentionPolicy.ts`):
-
-- `RETENTION_CLASSES = ["forget", "temporary", "working", "durable", "permanent"] as const`
-- `RETENTION_THRESHOLDS = { forget: 0, temporary: 30, working: 50, durable: 75, permanent: 90 } as const`
-- `RETENTION_WEIGHTS = { frequency: 4.5, spread: 7, decision: 12, qa: 10, relation: 4, confidence: 10, recencyBase: 18, recencyPerDay: 0.55, agePerDay: 0.12, ageCap: 22, contradiction: 9 } as const`
-
-```
-score = clamp(
-  frequency * 4.5
-  + spread * 7
-  + decisionWeight * 12
-  + qaWeight * 10
-  + relationDegree * 4
-  + confidence * 10
-  + max(0, 18 - recencyDays * 0.55)
-  - min(22, ageDays * 0.12)
-  - contradictionCount * 9
-, 0, 110)
-```
+- Export and purge are explicit local data commands; purge requires explicit confirmation.
 
-`computeRetentionScore(input)` returns the rounded integer. `classifyRetention(score, manualPin)` returns the class, applying the pin override first.
+## Ledger Boundary
 
-Boundary cases (score, pin=false): 29→forget, 30→temporary, 49→temporary, 50→working, 74→working, 75→durable, 89→durable, 90→permanent. These are verified by the focused contract test.
+OMO Memory's chronological ledger is authoritative: sessions, events, and handoffs record what happened in a project. Adapters should write concise summaries and evidence references to that ledger, then use explicit `recent`, `recall`, `handoff`, `export`, `purge`, and global event import/list operations.
 
-All scoring inputs are derived from ledger signals (event counts, last-seen deltas, project spread from index, decision/qa event types, explicit relation degree, stored confidence, manual pin flag, contradiction markers). No raw transcripts or secrets are inputs.
+OMO Memory does not provide automatic ontology extraction, graph visualization, retention scoring, durable-memory promotion, or OpenTUI workflows. Do not build adapter behavior that depends on those unavailable surfaces.

package/docs/epic-omo-memory.md

@@ -1,12 +1,12 @@
-# Epic: OMO Memory — shared local second-brain DB for OMO adapters
+# Epic: OMO Memory — shared local session/work ledger for OMO adapters
 
 ## Goal
 
-Build a host-neutral local memory layer for OMO so lazycodex, omo-on-opencode, lfg, and future adapters can share task context, durable decisions, and ontology-backed project knowledge across coding-tool sessions.
+Build a host-neutral local memory layer for OMO so lazycodex, omo-on-opencode, lfg, and future adapters can share task context, recorded decisions, QA evidence, event history, and handoffs across coding-tool sessions.
 
 The product ships as both:
 
-- CLI: install, inspect, global migration, ontology lifecycle, graph, search, export, purge, and handoff operations.
+- CLI: install, inspect, global event import, search, export, purge, and handoff operations.
 - MCP server: standard stdio tools for agents and coding tools to explicitly read/write OMO memory.
 
 ## Problem
@@ -23,7 +23,7 @@ Codegraph solves code intelligence, not work/session memory. OMO needs a separat
 - Local-first privacy: no cloud sync and no secret storage by default
 - Adapter-neutral schema: `host` and `adapter` are metadata, not separate products
 - Shared API: CLI and MCP use the same core DB layer
-- Second-brain lifecycle: candidate extraction, deterministic retention scoring, promotion, demotion, supersession, explicit recall, and OpenTUI graph inspection
+- Explicit recall only: no automatic prompt injection, ontology extraction, graph TUI, concept extraction, retention scoring, or durable-memory lifecycle.
 
 ## In scope
 
@@ -32,6 +32,7 @@ Codegraph solves code intelligence, not work/session memory. OMO needs a separat
   - `init`
   - `global scan`
   - `global migrate`
+  - `global list`
   - `session start`
   - `session bootstrap`
   - `event record`
@@ -39,13 +40,9 @@ Codegraph solves code intelligence, not work/session memory. OMO needs a separat
   - `recall`
   - `handoff write`
   - `doctor`
-  - `ontology candidates`
-  - `ontology score`
-  - `ontology promote`
-  - `ontology demote`
-  - `ontology supersede`
-  - `ontology recall`
-  - `graph tui`
+  - `export`
+  - `purge`
+
 - MCP stdio server with tools:
   - `memory_init`
   - `memory_project_context`
@@ -58,24 +55,15 @@ Codegraph solves code intelligence, not work/session memory. OMO needs a separat
   - `memory_global_scan`
   - `memory_global_migrate`
   - `memory_global_list`
-  - `memory_ontology_candidates`
-  - `memory_ontology_extract`
-  - `memory_ontology_score`
-  - `memory_ontology_promote`
-  - `memory_ontology_demote`
-  - `memory_ontology_supersede`
-  - `memory_ontology_recall`
+  - `memory_export`
+  - `memory_purge`
+
 - Privacy guardrails:
   - local-only default
   - no API key/token/env capture
   - explicit purge/export commands
 - Adapter integration notes for lazycodex, omo-on-opencode, and lfg
-- Retention classes:
-  - `forget`: safe to drop after low score or decay
-  - `temporary`: short-term task context
-  - `working`: active project memory
-  - `durable`: cross-session knowledge
-  - `permanent`: manual-pin or high-score knowledge; only explicit demote/supersede/purge changes it
+- Cross-project event import with source provenance through user-selected global SQLite files.
 
 ## Out of scope
 
@@ -83,7 +71,9 @@ Codegraph solves code intelligence, not work/session memory. OMO needs a separat
 - Team sharing by default
 - Full transcript capture by default
 - Vector/embedding search in MVP
-- Browser-only graph UI
+- Ontology/concept extraction
+- Graph UI, graph TUI, and OpenTUI
+- Retention scoring or durable-memory curation lifecycle
 - Automatic prompt injection from the last session
 - Replacing codegraph
 - Host-specific private APIs as required dependencies
@@ -95,21 +85,22 @@ Codegraph solves code intelligence, not work/session memory. OMO needs a separat
 - `omo-memory init` creates or migrates `<project-root>/.omo/memory/state.sqlite`.
 - `omo-memory global scan --root <path>` discovers project-local OMO DBs and reports schema versions.
 - `omo-memory global migrate --root <path> --global-db <path>` copies source DB data into one global SQLite file without mutating source DBs.
+- `omo-memory global list --global-db <path>` lists imported global event history with source provenance.
 - `omo-memory session start --host grok --adapter lfg` records a session for the current project.
 - `omo-memory session bootstrap --host codex --adapter lazycodex` returns a session id and project metadata without injecting recent events.
 - `omo-memory event record --type decision --summary "..."` appends a project/session event.
 - `omo-memory recent` lists recent project events.
 - `omo-memory recall --query "..."` performs explicit query-gated event recall.
 - `omo-memory handoff write --summary-file path.md` stores a handoff summary.
-- `omo-memory ontology candidates` extracts vocabulary candidates from concise summaries.
-- `omo-memory ontology score` recomputes deterministic retention classes.
-- `omo-memory ontology promote/demote/supersede/recall` supports curated durable memory lifecycle.
-- `omo-memory graph tui --db <path> --query <term>` opens an OpenTUI graph with `q` quit, arrow/tab selection, retention class, score, provenance, and detail pane. It requires `bun` on `PATH`; other CLI and MCP commands run on Node.
+- `omo-memory doctor` reports DB path, schema version, and project identity.
+- `omo-memory export` writes explicit local ledger export data.
+- `omo-memory purge --yes` removes local ledger data only after explicit confirmation.
+
 
 ### MCP
 
 - `omo-memory mcp` starts a stdio MCP server.
-- MCP tools can initialize the DB, read project context, record events, list/retrieve explicit memory, write handoffs, migrate global memory, and manage ontology lifecycle.
+- MCP tools can initialize the DB, read project context, record events, list/retrieve explicit memory, write handoffs, export/purge local data, and scan/import/list global event memory.
 - MCP tool responses are structured JSON text.
 - `memory_bootstrap_session` remains write-only/session-only and does not return `recentEvents`.
 
@@ -119,25 +110,14 @@ Codegraph solves code intelligence, not work/session memory. OMO needs a separat
 - DB path can be overridden only by explicit `OMO_MEMORY_DB`.
 - `doctor` reports DB path, schema version, and project identity without leaking sensitive values.
 - Global migration is copy/import only; source project DB mtimes and row counts must remain unchanged.
-- Graph and recall are local-first and explicit; no cloud sync, browser server, raw transcript capture, or embeddings are required.
+- Recall is local-first and explicit; no cloud sync, browser server, raw transcript capture, ontology extraction, graph UI, OpenTUI, retention scoring, durable-memory curation, or embeddings are required.
 
 ### QA evidence
 
-- `npm run typecheck`
-- `npm run build`
-- `npm run check`
-- CLI smoke:
-  - `node dist/cli.js init`
-  - `node dist/cli.js global scan --root <tmp-workspace>`
-  - `node dist/cli.js global migrate --root <tmp-workspace> --global-db <tmp-global.sqlite>`
-  - `node dist/cli.js session start --host grok --adapter lfg`
-  - `node dist/cli.js event record --type decision --summary "smoke"`
-  - `node dist/cli.js ontology candidates`
-  - `node dist/cli.js ontology score`
-  - `bun dist/cli.js graph tui --db <tmp-db> --query smoke`
-  - `node dist/cli.js recent`
-- MCP smoke: start `node dist/cli.js mcp` and verify `tools/list` includes memory tools.
-- Backfill verifier: synthetic Linaforge/omo-memory/lfg/omo-phone DB replicas plus read-only scan of real local DB paths.
+- Focused CLI smoke covers init, global scan/migrate/list, session start/bootstrap, event record, recent, recall, handoff write, export, and purge.
+- MCP smoke verifies `tools/list` includes the core `memory_*` ledger tools plus `memory_global_scan`, `memory_global_migrate`, and `memory_global_list`, and excludes `memory_ontology_*`.
+- Global import smoke verifies source project DBs are copied/imported with provenance and not mutated.
+- Documentation review verifies removed ontology, graph TUI/OpenTUI, concept extraction, retention scoring, and durable-memory curation surfaces are not documented as shipped features.
 
 ## Follow-up issue breakdown
 
@@ -147,8 +127,6 @@ Codegraph solves code intelligence, not work/session memory. OMO needs a separat
 4. Project identity and git metadata
 5. Privacy/redaction/purge/export
 6. Global SQLite migration and source provenance
-7. Deterministic ontology extraction and retention scoring
-8. Durable memory promote/demote/supersede lifecycle
-9. OpenTUI graph visualization
-10. Adapter integration docs for lazycodex, omo-on-opencode, and lfg
-11. QA harness for CLI, MCP, global backfill, and TUI smoke tests
+7. Adapter integration docs for lazycodex, omo-on-opencode, and lfg
+8. QA harness for CLI, MCP, and global import smoke tests
+9. Removal verification for ontology, graph TUI/OpenTUI, concept extraction, retention scoring, and durable-memory curation docs

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "omo-memory",
-  "version": "0.1.14",
+  "version": "0.1.15",
   "description": "Host-neutral local SQLite memory and session ledger for OMO adapters, exposed through CLI and MCP.",
   "type": "module",
   "files": [
@@ -33,16 +33,16 @@
     "start": "node dist/cli.js",
     "prepack": "npm run build",
     "presmoke": "npm run build",
-    "smoke": "npm run smoke:cli && npm run smoke:mcp && npm run smoke:hook",
+    "smoke": "npm run smoke:cli && npm run smoke:mcp && npm run smoke:hook && npm run smoke:legacy",
     "smoke:cli": "node scripts/smoke-cli.mjs",
     "smoke:mcp": "node scripts/smoke-mcp.mjs",
     "smoke:hook": "node scripts/verify-user-prompt-hook.mjs",
+    "smoke:legacy": "node scripts/verify-legacy-schema-compat.mjs",
     "mcp": "node dist/cli.js mcp",
     "issue:epic": "node scripts/create-epic-issue.mjs"
   },
   "dependencies": {
     "@modelcontextprotocol/sdk": "^1.29.0",
-    "@opentui/core": "0.4.2",
     "better-sqlite3": "^12.11.1",
     "zod": "^4.4.3"
   },

package/dist/conceptExtraction.js

@@ -1,188 +0,0 @@
-import { recordMemoryReference, upsertConcept } from "./ontologyCore.js";
-import { redactSecrets } from "./privacy.js";
-// Comprehensive generic/hook stopwords. Keep domain terms out.
-const STOPWORDS = new Set([
-    // from recall + hook words
-    "action",
-    "asked",
-    "current",
-    "help",
-    "memory",
-    "need",
-    "needs",
-    "omo",
-    "please",
-    "prompt",
-    "request",
-    "requested",
-    "session",
-    "user",
-    "want",
-    "wants",
-    "work",
-    "working",
-    // common English + dev noise
-    "the",
-    "and",
-    "for",
-    "with",
-    "from",
-    "into",
-    "about",
-    "this",
-    "that",
-    "these",
-    "those",
-    "start",
-    "now",
-    "test",
-    "run",
-    "check",
-    "fix",
-    "add",
-    "change",
-    "update",
-    "get",
-    "set",
-    "make",
-    "create",
-    "delete",
-    "remove",
-    "show",
-    "list",
-    "use",
-    "using",
-    "via",
-    "task",
-    "todo",
-    "step",
-    "item",
-    "thing",
-    "stuff",
-    "new",
-    "old",
-    "one",
-    "two",
-    "three",
-    "four",
-    "five",
-    "six",
-    "seven",
-    "eight",
-    "nine",
-    "ten",
-    "please",
-    "thanks",
-    "thank",
-    "also",
-    "just",
-    "only",
-    "like",
-    "such",
-    "very",
-    "really",
-    "should",
-    "could",
-    "would",
-    "will",
-    "can",
-    "may",
-    "must",
-    "have",
-    "has",
-    "had",
-    "been",
-    "being",
-    "are",
-    "was",
-    "were",
-    "is",
-    "be",
-    "to",
-    "of",
-    "in",
-    "on",
-    "at",
-    "by",
-    "as",
-    "it",
-    "its",
-    "if",
-    "or",
-    "and",
-    "but",
-    "not",
-    "no",
-    "yes",
-    "all",
-    "any",
-    "each",
-    "few",
-    "more",
-    "most",
-    "other",
-    "some",
-    "such",
-    "than",
-    "too",
-    "very",
-]);
-function normalizeLabel(raw) {
-    return raw.trim().toLowerCase();
-}
-function tokenize(input) {
-    // Preserve hyphenated compounds (local-first), keep alnum _ -
-    const cleaned = input
-        .toLowerCase()
-        .replace(/[^a-z0-9_\-\s]/g, " ")
-        .replace(/\s+/g, " ")
-        .trim();
-    if (!cleaned)
-        return [];
-    return cleaned.split(" ").filter((t) => t.length >= 3);
-}
-export function extractConceptCandidates(summary, _eventType) {
-    if (!summary || typeof summary !== "string")
-        return [];
-    // Never operate on large blobs: caller must pass short summary only.
-    const redacted = redactSecrets(summary);
-    const tokens = tokenize(redacted);
-    const seen = new Set();
-    const out = [];
-    for (const t of tokens) {
-        if (STOPWORDS.has(t))
-            continue;
-        const norm = normalizeLabel(t);
-        if (norm.length < 3)
-            continue;
-        if (seen.has(norm))
-            continue;
-        seen.add(norm);
-        out.push(norm);
-    }
-    return out;
-}
-export function applyConceptExtraction(dbPath, project, sourceEventId, summary, eventType) {
-    const candidates = extractConceptCandidates(summary, eventType);
-    const concepts = [];
-    const references = [];
-    for (const label of candidates) {
-        // upsertConcept will be made idempotent + bump ref_count by label
-        const concept = upsertConcept(dbPath, project, {
-            kind: "term",
-            label,
-            // score/retention left to scorer (Todo 6); default working
-        });
-        concepts.push(concept);
-        const ref = recordMemoryReference(dbPath, project, {
-            sourceType: "event",
-            sourceId: sourceEventId,
-            targetType: "concept",
-            targetId: concept.id,
-            refKind: "mentions",
-            weight: 1,
-        });
-        references.push(ref);
-    }
-    return { concepts, references };
-}