Prototype · Preview: every server in the official registry, synced every 30 minutes. Sign in with Google to write reviews.Prototype · updated every 30 min
PopNx MCPMCP servers for people who use AI · explained in plain words

Semantic State Runtime

by oaslanankaversion 0.3.3i★ 0iRuns on your computer
Registry nameio.github.oaslananka/semantic-state-runtime

How to install

What it does

Local MCP server for policy-authorized semantic context and source-authority reconciliation.

  • Connects Runs on your computer
  • Account or key No key needed
  • Category Other

Why it ranks here

Lists are ordered by a usage score (out of 100) built from these parts

Popularity0/80GitHub stars or weekly downloads: the larger counts 60, the smaller 20
Freshness12/12Full marks for a release or code change within 30 days
Still answering0/8The cloud endpoint answered at the last check
Usage score12/100

Quality: Passed 3/3 basic checks (shown, not used for ordering) · Momentum: No data yet (Used only on the Trending tab)

Install

Pick the AI app you use, then copy the settings.

Passed 3/3 checks · Runs on your computer · ✓ Commands checked Nov 16, 2026

First: which AI do you use?

Pick your app and the steps appear below.

Works with Claude, with some setup first

Install Node.js on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone

Let AI install it

Copy this message into a Claude chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server Semantic State Runtime for Claude on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "semantic-state-runtime": { "command": "npx", "args": [ "-y", "semantic-state-runtime" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the Semantic State Runtime tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install Node.js (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    node -v
    • A version number such as v26.13.1 = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed

    Open the Node.js download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v

    Install once; it works for everything that needs Node.js

  2. Open the Claude desktop app’s settings file

    SettingsDeveloperEdit Config

  3. Paste these settings and save the file

    {
      "mcpServers": {
        "semantic-state-runtime": {
          "command": "npx",
          "args": [
            "-y",
            "semantic-state-runtime"
          ]
        }
      }
    }
  4. Quit Claude and open it again

  5. Try it

    Use Semantic State Runtime and tell me what you can do for me, then show me one thing

    ✓ If Claude says it is using Semantic State Runtime or shows a Semantic State Runtime tool in the answer, you are connected

Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version

ChatGPT cannot connect Semantic State Runtime yet

Semantic State Runtime runs on your computer, but ChatGPT can only connect servers that run on the web

What you can do instead

A · Use an app that can connect Semantic State Runtime

  • Install Node.js on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone
  • Install Node.js on your computer first (one time)
  • Install Node.js on your computer first (one time) · No one-click button: paste the settings and fill in the values yourself
  • Install Node.js on your computer first (one time) · No one-click button: paste the settings and fill in the values yourself

B · Others in Other that work with ChatGPT

Picked from the most used in the same category, only ones that connect by address with no key

Works with Claude Code, with some setup first

Install Node.js on your computer first (one time)

Let AI install it

Copy this message into a Claude Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server Semantic State Runtime for Claude Code on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): claude mcp add --scope user semantic-state-runtime -- npx -y semantic-state-runtime 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the Semantic State Runtime tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install Node.js (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    node -v
    • A version number such as v26.13.1 = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed

    Open the Node.js download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v

    Install once; it works for everything that needs Node.js

  2. Open Terminal

    Mac: press Command+Space and type Terminal · Windows: open PowerShell

  3. Paste this command and press Enter

    claude mcp add --scope user semantic-state-runtime -- npx -y semantic-state-runtime
  4. Type /mcp in Claude Code

    You should see Semantic State Runtime listed as connected

  5. Try it

    Use Semantic State Runtime and tell me what you can do for me, then show me one thing

    ✓ If Claude Code says it is using Semantic State Runtime or shows a Semantic State Runtime tool in the answer, you are connected

Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Works with Cursor, with some setup first

Install Node.js on your computer first (one time) · No one-click button: paste the settings and fill in the values yourself

Let AI install it

Copy this message into a Cursor chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server Semantic State Runtime for Cursor on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "semantic-state-runtime": { "command": "npx", "args": [ "-y", "semantic-state-runtime" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the Semantic State Runtime tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install Node.js (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    node -v
    • A version number such as v26.13.1 = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed

    Open the Node.js download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v

    Install once; it works for everything that needs Node.js

  2. Open Cursor’s MCP settings file

    ~/.cursor/mcp.json

    Paste these settings, fill in the empty values and save

    {
      "mcpServers": {
        "semantic-state-runtime": {
          "command": "npx",
          "args": [
            "-y",
            "semantic-state-runtime"
          ]
        }
      }
    }
  3. Open the AI chat in Cursor in Agent mode

  4. Try it

    Use Semantic State Runtime and tell me what you can do for me, then show me one thing

    ✓ If Cursor says it is using Semantic State Runtime or shows a Semantic State Runtime tool in the answer, you are connected

Menu names checked against Cursor’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Works with VS Code, with some setup first

Install Node.js on your computer first (one time) · No one-click button: paste the settings and fill in the values yourself

Let AI install it

Copy this message into a VS Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server Semantic State Runtime for VS Code on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "servers": { "semantic-state-runtime": { "type": "stdio", "command": "npx", "args": [ "-y", "semantic-state-runtime" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the Semantic State Runtime tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install Node.js (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    node -v
    • A version number such as v26.13.1 = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed

    Open the Node.js download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v

    Install once; it works for everything that needs Node.js

  2. Open VS Code’s MCP settings file

    MCP: Open User Configuration

    Paste these settings, fill in the empty values and save

    {
      "servers": {
        "semantic-state-runtime": {
          "type": "stdio",
          "command": "npx",
          "args": [
            "-y",
            "semantic-state-runtime"
          ]
        }
      }
    }
  3. Open the AI chat in VS Code in Agent mode

  4. Try it

    Use Semantic State Runtime and tell me what you can do for me, then show me one thing

    ✓ If VS Code says it is using Semantic State Runtime or shows a Semantic State Runtime tool in the answer, you are connected

Menu names checked against VS Code’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Other apps that use MCP, such as Windsurf, Zed or Gemini CLI, each add servers differently. See how in the app list.

See every app that uses MCP →

JSON settings are under “For developers” below

Stuck? Ask people who use Semantic State Runtime💬 Discussion →
For developers: Terminal commands and JSON settings

Installed on your computer

Claude Code

claude mcp add --scope user semantic-state-runtime -- npx -y semantic-state-runtime

Claude Desktop (claude_desktop_config.json)

{
  "mcpServers": {
    "semantic-state-runtime": {
      "command": "npx",
      "args": [
        "-y",
        "semantic-state-runtime"
      ]
    }
  }
}

Cursor (~/.cursor/mcp.json)

{
  "mcpServers": {
    "semantic-state-runtime": {
      "command": "npx",
      "args": [
        "-y",
        "semantic-state-runtime"
      ]
    }
  }
}

VS Code (mcp.json)

{
  "servers": {
    "semantic-state-runtime": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "semantic-state-runtime"
      ]
    }
  }
}

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

At a glance

Downloads per weeki
Not on npm/PyPI
Connection
Runs on your computer
Latest versioni
0.3.3
Categoryi
Other
Published to registryi
Nov 16, 2026
Code last changedi
Nov 15, 2026
Maker
oaslananka
Packages
npm: semantic-state-runtime
Website
github.com
Registry status
Active

Which apps can use it

Based on how this server connects and on each app’s own docs, checked Nov 10, 2026.

Run on your computer in

ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast

All apps, with pros and cons →

Related guides

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 16, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account oaslananka, which owns the repo

  • ✓ Pass

    Still maintained

    Code last changed yesterday

  • ✓ Pass

    Has a licence

    Uses MIT

  • – Not applicable

    Endpoint responds

    This one runs on your computer; there is no internet endpoint

  • – Not applicable

    Sign-in with OAuth

    Runs on your computer and uses local settings instead

  • … Not checked yet

    No hidden instructions in tool descriptions

    Runs on your computer; we can only read tool lists from internet endpoints

Published vulnerabilities (OSV.dev)

No entries on OSV.dev for semantic-state-runtime@0.3.3

Checks only this package version, not every dependency · checked Nov 16, 2026

What we check → · JSON

Makers: ask for a re-check or report wrong info
For makers: add a badge to your README

If you made this, paste this code into your README. The badge links back to this page.

[![Featured on PopNx MCP](https://mcp.popnx.com/badge/oaslananka-semantic-state-runtime.svg)](https://mcp.popnx.com/en/servers/oaslananka-semantic-state-runtime)

Discussion

Ask, share a tip or report that it does not work. Sorted by what people marked helpful.

No posts yet. Be the first to ask or share.

Posts here are written by users, not the PopNx team.

Sign in to post

User reviews

No reviews yet

Sign in to write a review

Compared with others in Otheri

  • More stars than 0% of the other 20025 servers in this category
  • Published to the registry more recently than 99% of the other 20025 servers in this category
  • Basic checks equal to or better than 100% of the other 20025 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Semantic State Runtime safe?

It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed yesterday, and the latest version (0.3.3) reached the registry today.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: World Monitor, openstatus, Oh My Posh Validator, Strata, Jitsu

Similar alternatives

Same category, other makers, commands already checked. Official ones first, then by stars.

Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

World Monitor

Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 97 tools.

by koala73Widely used★ 90.7KUpdated 2 days ago

Runs in the cloud✓ service owner · worldmonitor.app

openstatus

Manage monitors, status pages, incidents and maintenances in your openstatus workspace.

by openstatusHQWidely used★ 9.3KUpdated 2 months ago

Runs in the cloud✓ service owner · openstatus.dev

Oh My Posh Validator

Validate oh-my-posh configurations and segment snippets against the official schema.

by JanDeDobbeleerWidely used★ 23.8K Stars for the whole repoUpdated 27 days ago

Runs in the cloud✓ service owner · ohmyposh.dev

Strata

MCP server for progressive tool usage at any scale (see https://klavis.ai)

by Klavis-AIGrowing★ 5.8KUpdated 14 months ago

Runs in the cloudRepo archived✓ klavis.ai

Jitsu

Manage Jitsu data pipelines: destinations, streams, connections, functions, live events.

by jitsucomWidely used★ 5.1KUpdated 4 months ago

Runs in the cloud✓ service owner · jitsu.com
Compared with similar ones
This one
Semantic State Runtime
World MonitoropenstatusOh My Posh ValidatorStrataJitsu
Runs whereInstalls on your computerRuns in the cloud, nothing to installRuns in the cloud, nothing to installRuns in the cloud, nothing to installRuns in the cloud, nothing to installRuns in the cloud, nothing to install
Needs a keyNoNoNoNoNoNo
Add with + in ClaudeNoNoNoNoNoNo
Basic checks3/34/44/44/41/44/4
LicenseMITAGPL-3.0AGPL-3.0MITApache-2.0MIT
PriceNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registry

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

Semantic State Runtime

Switch AI coding agents without losing the current project facts.

Connect one public GitHub repository or selected local folder, then ask your MCP-capable AI agent for the open issues and relevant decisions. SSRL keeps a bounded, read-only project view updated on demand and applies explicit source authority instead of trusting stale local notes.

Status: public npm MCP release (current version in the npm badge). The MCP runtime is usable

with synthetic data, but independent human onboarding and production use are

not yet validated. No hosted service or model account is included.

Semantic State Runtime (SSRL) helps AI agents use the right information when several sources disagree. It reconciles writable state against explicit source authority, persists the result across sessions and exposes only policy-authorized context through the Model Context Protocol (MCP).

Why it matters

Imagine a project deadline is November 15 in a stale local copy, but the trusted source says November 20. Rather than letting an AI assistant guess, SSRL can:

  1. Identify which source is authoritative for the field.
  2. Produce and apply a precondition-checked correction to the writable copy.
  3. Give a new MCP client the authorized, current deadline after restart.
  4. Exclude fields and evidence the client is not permitted to see.

This is state reconciliation and access-controlled context, not simply chat-history memory, an unrestricted file search, or an LLM provider.

Connect your first real project

npm install -g semantic-state-runtime

ssrl-connect https://github.com/oaslananka/semantic-state-runtime cd ssrl-semantic-state-runtime opencode

Ask: "Use SSRL context.compile for oaslananka/semantic-state-runtime. Which GitHub issues are currently open? Show issue numbers and sources." The generated OpenCode configuration is ready; Antigravity's workspace-local .agents/mcp_config.json and a separate Copilot MCP entry are included.

Alternatively, connect a local folder once using ssrl-connect ./my-project --out ./my-project-ssrl. It discovers the project's GitHub origin when present, or accepts --local-only. Existing files are never modified; only selected Markdown, and GitHub open issue/PR metadata when connected, are ingested. The bounded refresh runs when context is requested, not through a background service. This is not an automatic history of every chat or file.

See the one-command project connection guide for exact limits, private GitHub access, refresh timing, source authority and reproducible acceptance evidence.

Install from npm

Requirements: Node.js 24.12+ and npm. No Git clone, workspace build, API key, or model account is needed to try the synthetic read-only MCP server.

npm install -g semantic-state-runtime

ssrl-demo-init ./ssrl-example ssrl-node --version

The initializer creates a new folder and refuses to overwrite one. It writes read-only synthetic Markdown and ready-to-use client definitions:

  • OpenCode: open ./ssrl-example as the working directory; the generated opencode.json uses the installed server's absolute paths.
  • VS Code Copilot: in Copilot, choose Chat: Open Customizations → MCP Servers → Copilot Global. Copy the ssrl entry from ./ssrl-example/copilot.mcp-config.json into your existing global mcp-config.json (merge; do not replace other configured servers).

The underlying ssrl.config.json limits access to synthetic records and does not grant writes. Ask the client to call context.compile for Project Atlas deadline; the authorized response contains 2026-11-20. A model account may be needed by your chat client, not by SSRL itself. Client definitions are generated inside the demo folder; your global configuration is never modified.

Use the explicit configuration guide before authorizing access to real files. Windows and Linux registry installs plus MCP tool calls passed with synthetic data; independent human onboarding and production suitability remain unverified.

See installation and client setup.

Run the demo

Requirements: Node.js 24.12+ and pnpm 12.14.0. From a fresh clone:

pnpm install --frozen-lockfile

pnpm build pnpm demo:handoff

The demo uses synthetic Markdown/SQLite data and two actual MCP SDK client sessions. Its output shows the stale value, trusted value, state.plan/state.apply reconciliation, restarted runtime, authorized context.compile answer, and privacy checks. Package installation may use the network; the demo itself requires no API key or external model.

Walk through the real observed output.

Use it as an MCP server

For a source-built alternative, see the source-based Developer Preview installer. It builds a production-only installation at an explicit final path; the source-based Windows installation cannot safely be moved afterward. The published npm package is standalone, separate from that limitation.

Maintainers can still build a private local npm tarball using pnpm preview:pack -- and verify it with pnpm test:preview-pack. The stable npm package is publicly available with GitHub release provenance. The Registry listing must be verified separately against the official MCP Registry API; independent consumer acceptance has not yet been established.

When running a local source build instead, after creating an explicit configuration file using the local runtime guide, start the server with:

node packages/node-app/dist/cli.js ./ssrl.config.json

./ssrl.config.json is your own file, not an included ready-made production config. Use explicit source mappings, principal scopes, field policies and local paths. The server does not silently discover user files. Point your MCP-capable client's stdio command and arguments at the built CLI and that config; each chat client has a different config format.

MCP toolWhat it does
state.planComputes a bounded proposed change based on source authority and preconditions.
state.applyApplies an approved proposal only within configured write permissions.
context.compileReturns current, policy-scoped semantic context within a bounded token budget.

Start read-only. Grant only state:read and context:read when a client needs retrieval, and disable writable field policies and plan/apply. The first-run OpenCode setup creates such a temporary synthetic read-only workspace automatically:

pnpm demo:chat-setup

The setup is offline; an actual hosted-model chat request requires a separate, explicit developer API key and network access.

Verified AI client integrations

OpenCode v2.3.0 and Goose CLI v1.59.0 each made a real context.compile MCP call and returned the correct authorized deadline from synthetic data. They are two independently tested chat applications, not two independently hosted model providers: both used the same NVIDIA developer gateway on one Windows host. These tests do not establish physical cross-device synchronization or readiness for real user data.

See OpenCode and Goose examples and the separate live two-model handoff.

Project status

  • Ready to try: public npm stable release (latest), read-only synthetic first-run, local build, deterministic demo, stdio MCP integration and regression tests.
  • Not yet delivered: independently validated human onboarding or a fully supported consumer product. Registry discoverability is verified separately through the official public API after publication.
  • License: GNU GPL v3.0, copyright (c) 2026 Osman Aslan. Redistribution is subject to the GPL copyleft terms.
  • Participation: read Contributing and Security. Security issues can be reported privately.

Architecture and implementation

source systems / local files

↓ connectors + restart-safe ingestion ↓ immutable Artifact Plane + Semantic State Store ↓ bitemporal state / retractions / typed identity / relations ↓ incremental Context Capsules ↓ Context Access Gateway ↓ retrieval / future agent adapters

AI side effects: agent -> RuntimeHost plan/apply -> provider preconditions -> journal

Implemented checkpoints include:

  • canonical entity identity and typed alias resolution;
  • bitemporal semantic observations and immutable retractions;
  • explicit field authority and conflict detection;
  • deterministic reconciliation planning and proposal digests;
  • durable SQLite semantic state + ordered change feed;
  • incremental, time-aware context capsules;
  • Markdown filesystem and Google Calendar ingestion adapters;
  • immutable content-addressed Artifact Plane;
  • policy-enforced artifact access;
  • local stdio MCP composition;
  • authenticated stateless MCP 2026-07-28 HTTP composition;
  • principal-aware, capsule-backed derived context access;
  • MCP context.compile projection with authenticated context:read preflight;
  • policy-scoped prefix-Merkle replication with bounded resumable sessions;
  • principal-scoped immutable record + artifact blob transfer;
  • authenticated bounded replication HTTP with real two-node semantic/artifact convergence;
  • optional Ed25519 device-bound HTTP Message Signature authentication with replay defense;
  • epoch-scoped opaque encrypted replication object identities that hide plaintext record/blob identifiers and digests from an untrusted relay;
  • descriptor-generic prefix-Merkle + bounded reconciliation with epoch-scoped opaque views and no plaintext reconciliation metadata.

Design posture

Core constraints are intentionally stricter than a conventional "RAG over personal files" system:

  • source evidence remains auditable;
  • derived caches/indexes are rebuildable and never define truth;
  • authorization happens before identity resolution/ranking when disclosure could leak hidden state;
  • agents receive bounded semantic context rather than unrestricted source-system search;
  • transport authentication and domain authorization are separate layers;
  • protocol adapters such as MCP do not define canonical semantics.

See docs/invariants.md and the versioned design documents under docs/.

Ne

Only the beginning is shown; read the rest in the repo