You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+49Lines changed: 49 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -36,11 +36,60 @@ SQLite hits the sweet spot:
36
36
-**Kanban board** -- Optional HTML report generator for visual task overview via GitHub Pages
37
37
-**Cross-project sharing** -- Optional `project` field scopes entities; omit it to share across all projects
38
38
-**Cross-machine sync** -- Bridge tools push/pull shared entities between machines via a private git repo
39
+
-**Premium runtime boundary** -- The OSS core can gate-load a separate private premium repo via signed entitlement checks, explicit owner approval, audit logging, and local revocation
39
40
-**Drop-in compatible core** -- All 9 tools from `@modelcontextprotocol/server-memory` work identically in `sqlite_memory`, with 41 more tools available from companion servers
40
41
-**Zero required dependencies beyond stdlib** -- Only `fastmcp` is required for MCP protocol; `sqlite3` is Python stdlib. Optional `orjson`, `sqlite-vec`, and `sentence-transformers` add speed and semantic search
41
42
-**Automatic FTS sync** -- Full-text index stays in sync with every write operation
42
43
-**JSONL migration** -- Optionally import existing `memory.json` knowledge graphs on first run
43
44
45
+
## Premium / Enterprise Boundary
46
+
47
+
This repository now includes the **public-core boundary** for a separate premium runtime.
- a public-safe bootstrap template for the separate private repo (`templates/private_premium_repo/`)
56
+
57
+
What is **not** in this OSS repo:
58
+
59
+
- private premium business logic
60
+
- private connectors and ingestion code
61
+
- customer entitlements
62
+
- signing keys
63
+
- proprietary ranking / governance rules
64
+
65
+
**Premium-only capabilities** are for paid, explicitly entitled users only. They are expected to live in a separate private repo and be loaded through the gated runtime only. Typical premium-only modules include:
66
+
67
+
- ACL / RBAC
68
+
- multi-mailbox ingestion
69
+
- partner digests and management summaries
70
+
- advanced ranking / orchestration
71
+
- governance / audit workflows beyond the OSS baseline
72
+
73
+
### Premium-only runtime behavior
74
+
75
+
Private premium extensions are **not loaded by default**.
76
+
77
+
The public runtime will only attempt to mount them when all of the following are true:
78
+
79
+
- a private premium entrypoint is configured
80
+
- a valid entitlement is provided
81
+
- local owner approval is present for protected premium features
82
+
- the entitlement is not locally revoked
83
+
84
+
Without a valid entitlement and local approval path, the premium runtime stays off and private extensions are not mounted.
0 commit comments