# gnosem - Doramagic AI Context Pack > Positioning: a pre-install experience and judgment asset. It helps the host AI get off to a good start, but it does not mean the project has already been installed, run, or validated. ## Sufficiency Principle - **Sufficiency over compression**: The AI Context Pack should be sufficient for the host AI to understand the project's value, capability boundaries, entrypoints, risks, and evidence sources before starting work; it may be layered, but it does not aim for the shortest possible summary. - **Compression policy**: Compress only noise and duplication, never context that affects judgment or the quality of the work. ## How the Host AI Should Use This You are reading the AI Context Pack that Doramagic compiled for gnosem. Treat it as pre-work context: help the user understand who it fits, what it can do, how to start, what must be verified after install, and where the risks are. Do not claim that you have already installed, run, or executed the target project. ## Claim Consumption Rules - **Fact source**: Repo Evidence + Claim/Evidence Graph; the Human Wiki only supplies salience, terminology, and narrative structure. - **Minimum status for a fact**: `supported` - `supported`: May be used as a project fact, but the answer must cite the claim_id and evidence path. - `weak`: Usable only as a low-confidence lead; the user must be asked to keep verifying. - `inferred`: Usable only for risk notes or open questions; must not be packaged as a project fact. - `unverified`: Must not be used as fact; state clearly that evidence is insufficient. - `contradicted`: Must show the conflicting sources and must not force a single version on the user's behalf. ## Who It Fits Best - **Developers already using host AIs such as Claude/Codex/Cursor/Gemini**: The README or plugin config mentions multiple host AIs. Evidence: `README.md` Claim: `clm_0002` supported 0.86 ## What It Can Do - **Command-Line Startup or Install Flow** (Verify after install): The project documentation contains runnable commands; real use requires running them in a local or host environment. Evidence: `README.md` Claim: `clm_0001` supported 0.86 ## How to Start - `npx gnosem-install` Evidence: `README.md` Claim: `clm_0003` supported 0.86 - `curl -sX POST https://gnosem.dev/signup \` Evidence: `README.md` Claim: `clm_0004` supported 0.86 - `curl -sX POST https://gnosem.dev/mcp \` Evidence: `README.md` Claim: `clm_0005` supported 0.86 ## Continue-or-Stop Decision Card - **Current recommendation**: Needs admin / security approval - **Why**: Continuing may involve secrets, accounts, external services, or sensitive context; get admin or security approval first. ### 30-Second Read - **What to do now**: Needs admin / security approval - **Minimum safe next step**: Run Prompt Preview first; if credentials or an enterprise environment are involved, get approval before trialing - **Do not trust yet**: Tool permission boundaries cannot be trusted before install. - **Continuing will touch**: Command execution, Local environment or project files, Environment variables / API keys ### What You Can Trust Now - **Target-audience signal: Developers already using host AIs such as Claude/Codex/Cursor/Gemini** (supported): Backed by a supported claim or project evidence, but that still is not the same as real install results. Evidence: `README.md` Claim: `clm_0002` supported 0.86 - **Capability exists: Command-Line Startup or Install Flow** (supported): You can trust that the project contains signals of this capability; whether it fits your specific task still needs trial or after-install verification. Evidence: `README.md` Claim: `clm_0001` supported 0.86 - **There are Quick Start / install-command signals** (supported): You can trust that the docs mention a startup or install entrypoint; do not run it directly in your primary environment because of that. Evidence: `README.md` Claim: `clm_0003` supported 0.86 ### What You Cannot Trust Yet - **Tool permission boundaries cannot be trusted before install.** (unverified): MCP/tool projects usually touch files, the network, the browser, or external APIs, so permissions and logs must be checked for real. - **Real output quality cannot be trusted before install.** (unverified): Prompt Preview can only show how it guides you; it cannot prove result quality in the real project. - **Host AI version compatibility cannot be trusted before install.** (unverified): Host loading rules and version differences across Claude, Cursor, Codex, Gemini, and others must be verified in a real environment. - **That it will not pollute your existing host AI's behavior cannot be trusted directly.** (inferred): Skill, plugin, and AGENTS/CLAUDE/GEMINI instructions may change the host AI's default behavior. - **Safe rollback cannot be assumed by default.** (unverified): Unless the project clearly provides uninstall and recovery instructions, verify in an isolated environment first. - **After a real install, is it compatible with the user's current host AI version?** (unverified): Compatibility can only be verified in the actual host environment. - **Does the project's output quality meet the user's specific task?** (unverified): The pre-install preview can only show flow and boundaries; it cannot replace real evaluation. - **Do the install commands require network access, permissions, or global writes?** (unverified): This affects install risk in both enterprise and personal environments. Evidence: `README.md` ### What Continuing Will Touch - **Command execution**: Package managers, network downloads, the local plugin directory, project config, or the user's home directory. Why: Running the very first command can already change your environment; decide whether it is worth running first. Evidence: `README.md` - **Local environment or project files**: Install results, plugin caches, project config, or local dependency directories. Why: The write scope and rollback path cannot be proven before install and need isolated verification. Evidence: `README.md` - **Environment variables / API keys**: Project entry docs explicitly showing API key, token, secret, or account credential configuration. Why: If a real install needs credentials, use test credentials first and go through a permission/compliance review. Evidence: `README.md` - **Host AI context**: The AI Context Pack, Prompt Preview, Skill routing, risk rules, and project facts. Why: Importing context affects the host AI's later judgment, so avoid packaging unverified items as facts. ### Minimum Safe Next Steps - **Run Prompt Preview first**: Use a pre-install interactive trial to judge whether the way of working fits; it needs no authorization or environment change. (applies when: Applies to any project, especially when output quality is unknown.) - **Trial-install only in an isolated directory or a test account**: Avoid letting install commands pollute your primary host AI, real projects, or home directory. (applies when: When there are signals of command execution, plugin config, or local writes.) - **Do not use real production credentials**: Once an environment variable / API key enters the host or toolchain, it can create account and compliance risk. (applies when: When environment signals like API, TOKEN, KEY, or SECRET appear.) - **After install, verify just one minimal task**: Verify loading, compatibility, output quality, and rollback first, then decide whether to use it deeply. (applies when: When moving from a trial into a real workflow.) ### Exit Plan - **Preserve the pre-install state**: Record the original host config and project state so you can later judge whether it is recoverable. - **Record the install commands and written paths**: Without clear uninstall instructions, you at least need to know which directories or configs to clean up manually. - **Be ready to revoke test API keys or tokens**: If test credentials leak or are misused, you can cut losses quickly. - **If there is no rollback path, do not enter your primary environment**: No rollback is a blocker before continuing; do not proceed on trust or luck. ## What Can Only Be Previewed - Explain who the project fits and what it can do - Demonstrate a typical conversation flow based on project docs - Help the user decide whether it is worth installing or researching further ## What Must Be Verified After Install - Actually installing the Skill, plugin, or CLI - Running scripts, modifying local files, or accessing external services - Verifying real output quality, performance, and compatibility ## Boundary & Risk Decision Card - **Mistaking the pre-install preview for a real run**: The user may overestimate how much configuration, permission, and compatibility verification the project has already done. Mitigation: Clearly separate prompt_preview_can_do from runtime_required. Claim: `clm_0006` inferred 0.45 - **Command execution will modify the local environment**: Install commands may write to the user's home directory, the host plugin directory, or project configuration. Mitigation: Run in an isolated environment or a test account first. Evidence: `README.md` Claim: `clm_0007` supported 0.86 - **To confirm**: After a real install, is it compatible with the user's current host AI version?. Why: Compatibility can only be verified in the actual host environment. - **To confirm**: Does the project's output quality meet the user's specific task?. Why: The pre-install preview can only show flow and boundaries; it cannot replace real evaluation. - **To confirm**: Do the install commands require network access, permissions, or global writes?. Why: This affects install risk in both enterprise and personal environments. ## Pre-Work Working Context ### Loading Order - First read how_to_use.host_ai_instruction to establish the boundaries of this pre-install judgment asset. - Read claim_graph_summary to confirm facts come from the Claim/Evidence Graph, not the Human Wiki narrative. - Then read intended_users, capabilities, and quick_start_candidates to judge whether the user is a match. - When you need to carry out a concrete task, check role_skill_index first, then evidence_index. - For real install, file modification, network access, performance, or compatibility questions, turn to risk_card and boundaries.runtime_required. ### Task Routes - **Command-Line Startup or Install Flow**: State that this is an after-install capability first, then give a pre-install checklist. Boundary: Must be verified after a real install or run. Evidence: `README.md` Claim: `clm_0001` supported 0.86 ### Context Scale - Total files: 50 - Important-file coverage: 40/50 - Evidence index entries: 40 - Role / Skill entries: 6 ### Handling Insufficient Evidence - **missing_evidence**: State that evidence is insufficient and ask the user for the target file, a README section, or after-install verification records; do not fill in facts. - **out_of_scope_request**: State that the task is beyond the current AI Context Pack's evidence scope and suggest the user check the Human Manual or verify after a real install. - **runtime_request**: Provide a pre-install checklist and command sources, but do not run commands for the user or claim they have been run. - **source_conflict**: Show the conflicting sources side by side, mark them as unverified, and do not force a single version. ## Prompt Recipes ### Fit assessment - Goal: Judge whether this project fits the user's current task. - Expected output: A fit conclusion, key reasons, evidence citations, what can be previewed before install, what must be verified after install, and a next-step recommendation. ```text Based on the AI Context Pack for gnosem, ask me 3 necessary questions first, then judge whether it fits my task. The answer must cover: who it fits, what it can do, what it cannot do, whether it is worth installing, and where the evidence comes from. Every project fact must cite evidence_refs, source_paths, or a claim_id. ``` ### Pre-install experience - Goal: Let the user feel the core workflow before installing, while avoiding packaging the preview as real capability or a marketing promise. - Expected output: An experience script with boundary labels, an after-install verification checklist, and a cautious recommendation; with no real-run promises or strong marketing language. ```text Treat gnosem as a pre-install experience asset, not an already-installed tool or a real runtime environment. Output exactly four parts: 1. Ask me 3 necessary questions first. 2. Give an "experience script": use the three labels [Previewable before install], [Must verify after install], and [Insufficient evidence] to show how it might guide the workflow. 3. Give an after-install verification checklist: list which capabilities can only be confirmed after a real install, real host loading, and a real project run. 4. Give a cautious recommendation: only "worth researching/trialing further", "add information before deciding", or "not recommended to continue"; do not endorse the project. Hard boundaries: - Do not claim you have installed, run, executed tests, modified files, or produced real results. - Do not write promise-like phrasing such as "auto-adapts", "guarantees passing", "perfect fit", or "strongly recommend installing". - If you describe how it works after install, you must use a conditional such as "if installed successfully and the host loads the Skill correctly, it might...". - The experience script may only be written as "example lines / hypothetical flow": use "might ask / might suggest / might show", not "has written, has generated, has passed, is running, is generating". - Prompt Preview does not hand out install commands; if the user is ready to trial, only prompt them to read Quick Start and the Risk Card first and to verify in an isolated environment. - Every project fact must come from a supported claim, evidence_refs, or source_paths; inferred/unverified items can only be risks or open questions. ``` ### Role / Skill selection - Goal: Pick the best-matching asset from the project's roles or Skills. - Expected output: A list of candidate roles or Skills, each with an applicable scenario, evidence paths, risk boundary, and whether after-install verification is needed. ```text Read role_skill_index and recommend 3-5 of the most relevant roles or Skills for my target task. For each recommendation, state the applicable scenario, likely output, risk boundary, and evidence_refs. ``` ### Risk pre-check - Goal: Identify environment, permission, rule-conflict, and quality risks before installing or adopting. - Expected output: A checklist of environment, permission, dependency, license, host-conflict, quality risk, and unknown items. ```text Based on risk_card, boundaries, and quick_start_candidates, give me a pre-install risk pre-check list. Do not run commands for me; only explain what I should check, why, and what impact a failure would have. ``` ### Host AI kickoff instruction - Goal: Turn the project context into a host AI instruction for the start of a conversation. - Expected output: A pre-work instruction with clear boundaries and clear evidence citations, suitable to copy to a host AI. ```text Based on the AI Context Pack for gnosem, generate a pre-work instruction I can paste to my host AI. This instruction must obey not_runtime=true and must not claim the project has been installed, run, or produced real results. ``` ## Role / Skill Index - Indexed 6 role / Skill / project-doc entries. - **What it is** (project_doc): Cross-vendor AI memory over MCP. One memory store. Every model. Claude, ChatGPT, Gemini, Kimi, Cursor, Windsurf — anything that speaks MCP. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `README.md` - **Gnosem brand assets direction 2B — "Seal"** (project_doc): Gnosem brand assets direction 2B — "Seal" Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `brand/README.md` - **gnosem-install** (project_doc): One-command installer for Gnosem https://gnosem.dev — cross-vendor AI memory over MCP. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `cli/README.md` - **projmap** (project_doc): Where your projects live, so every AI you use can find them. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `projmap/README.md` - **gnosem** (project_doc): Official Python client for Gnosem https://gnosem.dev — hosted, cross-vendor MCP memory for AI agents. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `sdk-python/README.md` - **@gnosem/client** (project_doc): Official TypeScript client for Gnosem https://gnosem.dev — hosted, cross-vendor AI memory over MCP. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `sdk-ts/README.md` ## Evidence Index - Indexed 40 evidence entries. - **What it is** (documentation): Cross-vendor AI memory over MCP. One memory store. Every model. Claude, ChatGPT, Gemini, Kimi, Cursor, Windsurf — anything that speaks MCP. Evidence: `README.md` - **Gnosem brand assets direction 2B — "Seal"** (documentation): Gnosem brand assets direction 2B — "Seal" Evidence: `brand/README.md` - **gnosem-install** (documentation): One-command installer for Gnosem https://gnosem.dev — cross-vendor AI memory over MCP. Evidence: `cli/README.md` - **projmap** (documentation): Where your projects live, so every AI you use can find them. Evidence: `projmap/README.md` - **gnosem** (documentation): Official Python client for Gnosem https://gnosem.dev — hosted, cross-vendor MCP memory for AI agents. Evidence: `sdk-python/README.md` - **@gnosem/client** (documentation): Official TypeScript client for Gnosem https://gnosem.dev — hosted, cross-vendor AI memory over MCP. Evidence: `sdk-ts/README.md` - **Package** (package_manifest): { "name": "gnosem-install", "version": "0.1.0", "description": "One-command installer for Gnosem — cross-vendor AI memory over MCP. Detects and configures Claude Desktop, Claude Code, Cursor, Windsurf, and Zed.", "keywords": "gnosem", "mcp", "model-context-protocol", "ai-memory", "claude", "chatgpt", "cursor", "windsurf", "zed", "installer" , "homepage": "https://gnosem.dev", "repository": { "type": "git", "url": "https://github.com/gnosem/gnosem", "directory": "cli" }, "bugs": "https://github.com/gnosem/gnosem/issues", "license": "MIT", "author": "CUETV LLC", "bin": { "gnosem-install": "bin/gnosem-install.js" }, "files": "bin/", "README.md" , "engines": { "node": " =18" } } Evidence: `cli/package.json` - **Package** (package_manifest): { "name": "@gnosem/projmap", "version": "0.1.0", "description": "projmap — where your projects live, so every AI you use can find them. Indexes source project paths into Gnosem so any MCP client Claude, ChatGPT, Cursor can query for them.", "keywords": "gnosem", "mcp", "ai-memory", "projects", "index", "cli", "cross-vendor", "claude", "cursor", "chatgpt" , "homepage": "https://gnosem.dev", "repository": { "type": "git", "url": "https://github.com/gnosem/gnosem", "directory": "projmap" }, "bugs": "https://github.com/gnosem/gnosem/issues", "license": "MIT", "author": "CUETV LLC", "bin": { "projmap": "bin/projmap.js" }, "files": "bin/", "README.md" , "engines": { "node": " =18" } } Evidence: `projmap/package.json` - **Package** (package_manifest): { "name": "@gnosem/client", "version": "0.1.0", "description": "Official TypeScript client for Gnosem — hosted, cross-vendor AI memory over MCP. Zero runtime deps, native fetch, Node 18+.", "keywords": "gnosem", "mcp", "ai-memory", "memory", "sdk", "client", "typescript", "claude", "chatgpt", "cursor" , "homepage": "https://gnosem.dev", "repository": { "type": "git", "url": "https://github.com/gnosem/gnosem", "directory": "sdk-ts" }, "bugs": "https://github.com/gnosem/gnosem/issues", "license": "MIT", "author": "CUETV LLC", "type": "module", "main": "dist/index.js", "types": "dist/index.d.ts", "exports": { ".": { "types": "./dist/index.d.ts", "import": "./dist/index.js" } }, "files": "dist/… Evidence: `sdk-ts/package.json` - **License** (source_file): Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files the "Software" , to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: Evidence: `LICENSE` - **License** (source_file): Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files the "Software" , to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: Evidence: `sdk-python/LICENSE` - **License** (source_file): Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files the "Software" , to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: Evidence: `sdk-ts/LICENSE` - **Server** (structured_config): { "$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json", "name": "dev.gnosem/gnosem", "title": "Gnosem", "description": "Cross-vendor AI memory over MCP. One semantic store, readable and writeable from every MCP client.", "version": "1.0.0", "repository": { "url": "https://github.com/gnosem/gnosem", "source": "github" }, "websiteUrl": "https://gnosem.dev", "remotes": { "type": "streamable-http", "url": "https://gnosem.dev/mcp" } } Evidence: `server.json` - **0001 Add Plan** (source_file): ALTER TABLE users ADD COLUMN plan TEXT NOT NULL DEFAULT 'free'; ALTER TABLE users ADD COLUMN stripe customer id TEXT; ALTER TABLE users ADD COLUMN subscription id TEXT; ALTER TABLE users ADD COLUMN subscription status TEXT; ALTER TABLE users ADD COLUMN subscription period end INTEGER; CREATE INDEX IF NOT EXISTS users stripe customer idx ON users stripe customer id ; CREATE INDEX IF NOT EXISTS users subscription idx ON users subscription id ; Evidence: `migrations/0001_add_plan.sql` - **0002 Add Content Optimized** (source_file): ALTER TABLE memories ADD COLUMN content optimized TEXT; ALTER TABLE memories ADD COLUMN content bytes INTEGER; ALTER TABLE memories ADD COLUMN optimized bytes INTEGER; Evidence: `migrations/0002_add_content_optimized.sql` - **0003 Rate Limits** (source_file): CREATE TABLE IF NOT EXISTS rate limits key TEXT PRIMARY KEY, count INTEGER NOT NULL, window start INTEGER NOT NULL ; CREATE INDEX IF NOT EXISTS rate limits window idx ON rate limits window start ; Evidence: `migrations/0003_rate_limits.sql` - **0004 Memories Fts** (source_file): CREATE VIRTUAL TABLE IF NOT EXISTS memories fts USING fts5 id UNINDEXED, content, content optimized, tokenize = 'unicode61 remove diacritics 2' ; DROP TRIGGER IF EXISTS memories ai; CREATE TRIGGER memories ai AFTER INSERT ON memories BEGIN INSERT INTO memories fts id, content, content optimized VALUES new.id, new.content, COALESCE new.content optimized, '' ; END; DROP TRIGGER IF EXISTS memories ad; CREATE TRIGGER memories ad AFTER DELETE ON memories BEGIN DELETE FROM memories fts WHERE id = old.id; END; DROP TRIGGER IF EXISTS memories au; CREATE TRIGGER memories au AFTER UPDATE OF content, content optimized ON memories BEGIN DELETE FROM memories fts WHERE id = old.id; INSERT INTO memories f… Evidence: `migrations/0004_memories_fts.sql` - **0005 Content Hash** (source_file): ALTER TABLE memories ADD COLUMN content hash TEXT; CREATE INDEX IF NOT EXISTS memories user hash idx ON memories user id, content hash ; Evidence: `migrations/0005_content_hash.sql` - **Schema** (source_file): CREATE TABLE IF NOT EXISTS users id TEXT PRIMARY KEY, email TEXT UNIQUE, created at INTEGER NOT NULL ; CREATE TABLE IF NOT EXISTS api keys key hash TEXT PRIMARY KEY, user id TEXT NOT NULL REFERENCES users id ON DELETE CASCADE, label TEXT, created at INTEGER NOT NULL, last used at INTEGER, revoked at INTEGER ; CREATE INDEX IF NOT EXISTS api keys user idx ON api keys user id ; CREATE TABLE IF NOT EXISTS memories id TEXT PRIMARY KEY, user id TEXT NOT NULL REFERENCES users id ON DELETE CASCADE, content TEXT NOT NULL, tags TEXT, written by TEXT, session id TEXT, created at INTEGER NOT NULL, superseded by TEXT REFERENCES memories id , forgotten at INTEGER ; CREATE INDEX IF NOT EXISTS memories use… Evidence: `schema.sql` - **Blog** (source_file): function metaTags ⋮---- function masthead ⋮---- function footer ⋮---- function blogPostingJsonLd post, url ⋮---- function breadcrumbJsonLd post, url ⋮---- export function blogPostHtml post Evidence: `src/blog.js` - **Dashboard** (source_file): export function dashboardHtml Evidence: `src/dashboard.js` - **Worker** (source_file): function uuid ⋮---- async function sha256Hex text ⋮---- function json obj, status = 200, extraHeaders = ⋮---- function jsonRpc id, result function jsonRpcError id, code, message, data ⋮---- async function generateApiKey ⋮---- // Wrap a user row into the same context shape the rest of the code expects. // Applies the pro/free downgrade + internal founder exception. function contextFromUserRow row ⋮---- async function authenticate request, env ⋮---- // Cookie path ⋮---- // ------------- rate limiting ------------- // // Sliding-window per-key counter backed by D1. Two D1 round-trips worst case: // a SELECT to read the current window + one INSERT/UPDATE to advance it. // Cheap at prototype sca… Evidence: `src/worker.js` - **Client** (source_file): all = ⋮---- DEFAULT BASE URL = "https://gnosem.dev" DEFAULT TIMEOUT = 30.0 ⋮---- @dataclass class Memory ⋮---- id: str content: str tags: List str = field default factory=list written by: Optional str = None session id: Optional str = None created at: Optional int = None content raw: Optional str = None optimized: Optional bool = None score: Optional float = None ⋮---- @classmethod def from dict cls, d: Mapping str, Any - "Memory" ⋮---- tags = d.get "tags" or ⋮---- tags = ⋮---- @dataclass class WriteResult ⋮---- optimized: bool = False exact duplicate: bool = False deduped: bool = False matched score: Optional float = None matched content preview: Optional str = None compression ratio: Opti… Evidence: `sdk-python/src/gnosem/client.py` - **Client** (source_file): import { GnosemAPIError, GnosemAuthError, GnosemError, GnosemRateLimitError, } from "./errors.js"; import type { ExportOptions, ExportResult, ForgetResult, GnosemOptions, ListOptions, ListResult, MeResult, RotateKeyResult, SearchOptions, SearchResult, SupersedeOptions, SupersedeResult, WriteBulkResult, WriteInput, WriteOptions, WriteResult, } from "./types.js"; ⋮---- export class Gnosem ⋮---- constructor opts: GnosemOptions = ⋮---- // -------- MCP tool wrappers all go through POST /mcp with JSON-RPC 2.0 -------- ⋮---- / Write a new memory. Server semantically de-dupes against existing memories unless force: true . Content is capped at 8KB. / async write content: string, opts: WriteOptions =… Evidence: `sdk-ts/src/client.ts` - **Errors** (source_file): export class GnosemError extends Error ⋮---- constructor message: string, status = 0, body = "" ⋮---- export class GnosemAuthError extends GnosemError ⋮---- constructor message: string, status = 401, body = "" ⋮---- export class GnosemRateLimitError extends GnosemError ⋮---- constructor message: string, retryAfter = 0, status = 429, body = "" ⋮---- export class GnosemAPIError extends GnosemError ⋮---- constructor message: string, status: number, body = "" Evidence: `sdk-ts/src/errors.ts` - **Types** (source_file): export interface Memory { id: string; content: string; content optimized?: string null; tags: string ; written by: string null; session id: string null; created at: number; score?: number; superseded by?: string; forgotten at?: number; } ⋮---- export interface WriteInput { content: string; tags?: string ; writtenBy?: string; sessionId?: string; noOptimize?: boolean; force?: boolean; } ⋮---- export interface WriteResult { id: string; created at: number; optimized?: boolean; deduped?: boolean; exact duplicate?: boolean; matched score?: number; matched id?: string; key: string : unknown; } ⋮---- export interface WriteBulkResult { results: WriteResult ; } ⋮---- export interface SearchResult { m… Evidence: `sdk-ts/src/types.ts` - **Tsconfig** (structured_config): { "compilerOptions": { "target": "ES2022", "module": "ES2022", "moduleResolution": "bundler", "lib": "ES2022", "DOM" , "types": "node" , "outDir": "dist", "rootDir": "src", "declaration": true, "declarationMap": true, "sourceMap": true, "strict": true, "noUncheckedIndexedAccess": true, "esModuleInterop": true, "forceConsistentCasingInFileNames": true, "skipLibCheck": true, "allowJs": false, "resolveJsonModule": true, "isolatedModules": true }, "include": "src/ / " , "exclude": "node modules", "dist", "test" } Evidence: `sdk-ts/tsconfig.json` - **Internal launch/marketing prep — not for the public repo.** (source_file): .wrangler/ .firecrawl/ node modules/ .dev.vars .env .env. .DS Store .log Evidence: `.gitignore` - **Favicon Ink** (source_file): Evidence: `brand/favicon-ink.svg` - **Favicon** (source_file): Evidence: `brand/favicon.svg` - **Gnosem Lockup Inverse** (source_file): GNOSEM Evidence: `brand/gnosem-lockup-inverse.svg` - **Gnosem Lockup** (source_file): GNOSEM Evidence: `brand/gnosem-lockup.svg` - **Gnosem Mark Ink** (source_file): Evidence: `brand/gnosem-mark-ink.svg` - **Gnosem Mark Inverse** (source_file): Evidence: `brand/gnosem-mark-inverse.svg` - **Gnosem Mark** (source_file): Evidence: `brand/gnosem-mark.svg` - **sdk-python/.gitignore** (source_file): .venv/ .pytest cache/ pycache / .py cod $py.class .egg-info/ build/ dist/ .mypy cache/ .ruff cache/ Evidence: `sdk-python/.gitignore` - **Pyproject** (source_file): build-system requires = "setuptools =61.0", "wheel" build-backend = "setuptools.build meta" Evidence: `sdk-python/pyproject.toml` - **sdk-ts/.gitignore** (source_file): node modules/ dist/ .tsbuildinfo .DS Store .log Evidence: `sdk-ts/.gitignore` - **sdk-ts/.npmignore** (source_file): src/ test/ tsconfig.json tsconfig.tsbuildinfo .npmignore node modules/ .log .DS Store Evidence: `sdk-ts/.npmignore` - **Wrangler** (source_file): { "name": "sharedmem", "main": "src/worker.js", "compatibility date": "2026-06-01", "compatibility flags": "nodejs compat" , "observability": { "enabled": true }, "d1 databases": { "binding": "DB", "database name": "sharedmem", "database id": "5a629266-d37f-4797-b492-b52ec1e9914b" } , "vectorize": { "binding": "VECTORIZE", "index name": "sharedmem-embeddings" } , "ai": { "binding": "AI" }, "routes": { "pattern": "gnosem.com", "custom domain": true }, { "pattern": "www.gnosem.com", "custom domain": true }, { "pattern": "gnosem.dev", "custom domain": true }, { "pattern": "www.gnosem.dev", "custom domain": true } } Evidence: `wrangler.jsonc` ## Rules the Host AI Must Follow - **Treat this asset as pre-work context, not a runtime environment.**: The AI Context Pack contains only an evidence-backed understanding of the project, not the project's executable state. Evidence: `README.md`, `brand/README.md`, `cli/README.md` - **When answering the user, distinguish what can be previewed from what can only be verified after install.**: The consumer value of the pre-install experience comes from reducing bad installs and misjudgments, not from pretending to be a real run. Evidence: `README.md`, `brand/README.md`, `cli/README.md` ## Questions the User Should Answer First - Which host AI or local environment do you plan to use it in? - Do you just want to experience the workflow first, or are you ready to actually install? - What matters most to you: install cost, output quality, or conflicts with your existing rules? ## Acceptance Checks - Every capability claim can be traced back to a file path in evidence_refs. - AI_CONTEXT_PACK.md does not package previews as a real run. - The user can understand who it fits, what it can do, how to start, and the risk boundaries within 3 minutes. --- ## 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. - **Project Overview**: importance `high` - source_paths: README.md, server.json - **System Architecture and Worker Routing**: importance `high` - source_paths: src/worker.js, src/openapi.js, src/llms-txt.js, src/blog.js, src/brand.js - **Memory Data Model, Migrations, and AI Integration**: importance `high` - source_paths: schema.sql, migrations/0001_add_plan.sql, migrations/0002_add_content_optimized.sql, migrations/0003_rate_limits.sql, migrations/0004_memories_fts.sql - **SDKs, CLI Installer, and Self-Hosting**: importance `medium` - source_paths: sdk-ts/src/client.ts, sdk-ts/src/index.ts, sdk-ts/src/types.ts, sdk-ts/src/errors.ts, sdk-ts/package.json ## Repo Inspection Evidence - repo_clone_verified: true - repo_inspection_verified: true - repo_commit: `695083cf374d4a78873da1b3c4ba21569d739460` - inspected_files: `README.md`, `src/blog.js`, `src/brand.js`, `src/dashboard.js`, `src/llms-txt.js`, `src/openapi.js`, `src/worker.js` 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: 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/gnosem/gnosem - 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: 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/gnosem/gnosem - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 3: 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/gnosem/gnosem - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 4: 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/gnosem/gnosem - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 5: 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/gnosem/gnosem - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.