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

LGD Engine

by Medxpert-orgversion 0.1.1i★ 0iRuns on your computerRepository ↗
Registry nameio.github.Medxpert-org/lgd-engine

How to install

What it does

Judgment core for medical-device AI change control: 510(k) change and postmarket gates.

  • Connects Runs on your computer
  • Account or key No key needed
  • Category Clinics & health

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.

Let your AI install it with one sentence

Please install LGD Engine. Follow https://mcp.popnx.com/i/medxpert-org-lgd-engine.md, show me the commands and wait for my OK before running them.

Paste it into an AI that can work on your computer (such as Claude Code or Cursor). It reads our steps, shows you the commands and waits for your OK. No key, no sign-up. · See the full text your AI reads

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 Python (uv) 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 LGD Engine for Claude on this computer, in this order: 1) Check uv with uv --version. If it is missing, tell me to install it from https://docs.astral.sh/uv/getting-started/installation/; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "lgd-engine": { "command": "uvx", "args": [ "lgd-engine" ] } } } 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 LGD Engine 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 uv (if you don’t have it)

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

    uv --version
    • A version number such as uv … = 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: uv has no click-through installer. Copy the one-line command for your system (macOS or Windows) from uv’s official page into Terminal · no separate Python install needed; uv downloads it when required

    Open the uv download page ↗

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

    Install once; it works for everything that needs uv

  2. Open the Claude desktop app’s settings file

    SettingsDeveloperEdit Config

  3. Paste these settings and save the file

    {
      "mcpServers": {
        "lgd-engine": {
          "command": "uvx",
          "args": [
            "lgd-engine"
          ]
        }
      }
    }
  4. Quit Claude and open it again

  5. Try it

    Use LGD Engine and tell me what you can do for me, then show me one thing

    ✓ If Claude says it is using LGD Engine or shows a LGD Engine 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 LGD Engine yet

LGD Engine 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 LGD Engine

  • Install Python (uv) on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone
  • Install Python (uv) on your computer first (one time)
  • Install Python (uv) on your computer first (one time)
  • Install Python (uv) on your computer first (one time)

B · Others in Clinics & health 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 Python (uv) 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 LGD Engine for Claude Code on this computer, in this order: 1) Check uv with uv --version. If it is missing, tell me to install it from https://docs.astral.sh/uv/getting-started/installation/; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): claude mcp add --scope user lgd-engine -- uvx lgd-engine 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 LGD Engine 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 uv (if you don’t have it)

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

    uv --version
    • A version number such as uv … = 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: uv has no click-through installer. Copy the one-line command for your system (macOS or Windows) from uv’s official page into Terminal · no separate Python install needed; uv downloads it when required

    Open the uv download page ↗

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

    Install once; it works for everything that needs uv

  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 lgd-engine -- uvx lgd-engine
  4. Type /mcp in Claude Code

    You should see LGD Engine listed as connected

  5. Try it

    Use LGD Engine and tell me what you can do for me, then show me one thing

    ✓ If Claude Code says it is using LGD Engine or shows a LGD Engine 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 Python (uv) on your computer first (one time)

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 LGD Engine for Cursor on this computer, in this order: 1) Check uv with uv --version. If it is missing, tell me to install it from https://docs.astral.sh/uv/getting-started/installation/; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "lgd-engine": { "command": "uvx", "args": [ "lgd-engine" ] } } } 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 LGD Engine 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 uv (if you don’t have it)

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

    uv --version
    • A version number such as uv … = 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: uv has no click-through installer. Copy the one-line command for your system (macOS or Windows) from uv’s official page into Terminal · no separate Python install needed; uv downloads it when required

    Open the uv download page ↗

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

    Install once; it works for everything that needs uv

  2. Click this button to open Cursor

    Open in Cursor

    Cursor asks you to confirm; click Install

  3. Open the AI chat in Cursor in Agent mode

  4. Try it

    Use LGD Engine and tell me what you can do for me, then show me one thing

    ✓ If Cursor says it is using LGD Engine or shows a LGD Engine 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 Python (uv) on your computer first (one time)

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 LGD Engine for VS Code on this computer, in this order: 1) Check uv with uv --version. If it is missing, tell me to install it from https://docs.astral.sh/uv/getting-started/installation/; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "servers": { "lgd-engine": { "type": "stdio", "command": "uvx", "args": [ "lgd-engine" ] } } } 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 LGD Engine 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 uv (if you don’t have it)

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

    uv --version
    • A version number such as uv … = 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: uv has no click-through installer. Copy the one-line command for your system (macOS or Windows) from uv’s official page into Terminal · no separate Python install needed; uv downloads it when required

    Open the uv download page ↗

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

    Install once; it works for everything that needs uv

  2. Click this button to open VS Code

    Open in VS Code

    VS Code asks you to confirm; click Install

  3. Open the AI chat in VS Code in Agent mode

  4. Try it

    Use LGD Engine and tell me what you can do for me, then show me one thing

    ✓ If VS Code says it is using LGD Engine or shows a LGD Engine 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 LGD Engine💬 Discussion →
For developers: Terminal commands and JSON settings

Installed on your computer

Claude Code

claude mcp add --scope user lgd-engine -- uvx lgd-engine

Claude Desktop (claude_desktop_config.json)

{
  "mcpServers": {
    "lgd-engine": {
      "command": "uvx",
      "args": [
        "lgd-engine"
      ]
    }
  }
}

Cursor (~/.cursor/mcp.json)

{
  "mcpServers": {
    "lgd-engine": {
      "command": "uvx",
      "args": [
        "lgd-engine"
      ]
    }
  }
}

VS Code (mcp.json)

{
  "servers": {
    "lgd-engine": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "lgd-engine"
      ]
    }
  }
}

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
Licencei
Apache-2.0
Connection
Runs on your computer
Latest versioni
0.1.1
Published to registryi
Nov 16, 2026
Code last changedi
Nov 17, 2026
Maker
Medxpert-org
Packages
pypi: lgd-engine
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 19, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account Medxpert-org, which owns the repo

  • ✓ Pass

    Still maintained

    Code last changed 2 days ago

  • ✓ Pass

    Has a licence

    Uses Apache-2.0

  • – 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)

Not checked yet

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/medxpert-org-lgd-engine.svg)](https://mcp.popnx.com/en/servers/medxpert-org-lgd-engine)

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 Clinics & healthi

  • More stars than 0% of the other 1186 servers in this category
  • Published to the registry more recently than 88% of the other 1186 servers in this category
  • Basic checks equal to or better than 99% of the other 1186 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 LGD Engine 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 2 days ago, and the latest version (0.1.1) reached the registry 3 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv) on your computer.

What can I use instead?

In the same category: Medplum MCP, Mirobody, Codescene MCP Server, WHOOP — MissingMCP, Marrow

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

Medplum MCP

Securely access and manage FHIR healthcare data stored in Medplum.

by medplumWidely used★ 2.8KUpdated 4 months ago

Runs in the cloud✓ service owner · medplum.com

Mirobody

Lab results to LOINC codes and UCUM units, symptoms and diagnoses to ICPC-3. Offline, no API key.

by thetahealthGrowing↓ 725/wk★ 1.6KUpdated 9 days ago

Runs on your computer✓ thetahealth.ai

Codescene MCP Server

An MCP server that provides CodeScene Code Health analysis tools.

by codescene-ossGrowing↓ 3.8K/wk★ 85Updated 8 months ago

Runs on your computer✓ service owner · codescene.com

Marrow

Marrow Health: your Apple Health data over MCP, from the free iOS app. Reads, and writes on demand.

by skeletonarmytechEarly↓ 62/wk★ 4Updated 28 days ago

Runs on your computer✓ skeletonarmy.tech
Compared with similar ones
This one
LGD Engine
Medplum MCPMirobodyCodescene MCP ServerWHOOP — MissingMCPMarrow
Runs whereInstalls on your computerRuns in the cloud, nothing to installInstalls on your computerInstalls on your computerRuns in the cloud, nothing to installInstalls on your computer
Needs a keyNoNoNoNoNoNo
Add with + in ClaudeNoNoNoNoNoNo
Basic checks3/34/43/32/32/43/3
LicenseApache-2.0Apache-2.0Apache-2.0NOASSERTIONMITMIT
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.

LGD Engine

LGD Engine is the judgment core for medical-device AI change control. While general agent frameworks orchestrate LLMs, LGD Engine supplies the *theory-bound gate*: every change verdict is produced by an auditable, offline-testable judgment chain grounded in the LGD theory (three laws, 有籍有证有门禁 / registered-evidenced-gated, 触点即门 / every touchpoint is a gate). Zero runtime dependencies — the core gate runs with no LLM.

Prerequisites

  • Python 3.9+ (python --version). Nothing else: the gate, the judges and the CLI are stdlib-only.
  • git, if you are cloning rather than downloading a zip.
  • Optional: PyYAML only for the 17-check OpenAPI validation (pip install -e ".[yaml]" from a checkout). Without it the validator says so and runs 5 text checks instead of pretending it ran 17.
  • Node 18+ only for the TypeScript SDK smoke; Docker only for the compose demo.

Quickstart

Shortest path — clone, run the gold tests, get your first verdict, then wire it to your agent host:

git clone https://github.com/Medxpert-org/lgd-engine.git

cd lgd-engine python -m demo1.change_gate --case demo1/cases/case01_red_pma_process.json

exit code: 0 = go, 1 = hold, 2 = reject

Exit codes are verdicts. In single-case mode the process exit code *is*

the verdict: 0 = go, 1 = hold, 2 = reject. A correct reject therefore

exits 2 — CI wrappers must map the code to the verdict instead of treating

any non-zero exit as a failed run. --all instead exits 0 only when every

case matches its expected verdict, and 1 on any mismatch. The CLI prints

the same mapping on its last line.

Verify the whole gate before trusting it (stock Python 3.9+, stdlib only):

# Windows

.\demo1\run_demo1.ps1 # 5/5 + 6/6 change-gate self-tests .\demo2\run_demo2.ps1 # 26/26 five-seat review self-tests

Any OS

python demo1/test_demo1.py # change-gate gold tests python demo2/test_demo2.py # five-seat review tests python demo1/test_ecosystem.py # 13-domain / 11-stage alignment tests python framework/gate_bot.py # CI gate (six checks)

One decision from a case JSON:

python -m demo1.change_gate --all

python -m demo1.change_gate --case demo1/cases_jurisdiction/supplier_swap.json --jurisdiction NMPA

Editable install (optional) exposes the console script:

pip install -e .        # then use `lgd-gate` (see pyproject [project.scripts])

Then point your MCP client at it — copy-paste configs are in Interface layer below.

Architecture

Layered design — adapters on the outside, judgment core in the middle, fully offline:

L0  AI hosts (Claude Desktop, Cursor, agents)

│ stdio / (streamable-HTTP in 0.1) ▼ L1 lgd.gate ── aggregation core (GateEngine + GateReport) │ ├── L1.5 skill registry (skill.yaml manifest) │ ▼ L2 DomainJudge ×13+ (offline, gold-tested; 2 shipped: 510(k), post-market) ▲ │ evidence: precedents / cases / regulation citations L3 lgd_engine/theory/laws.yaml (declarative three-law rules)

Runnable surfaces today: python -m demo1.web serves a local web UI + JSON endpoint (POST http://127.0.0.1:8765/judge) that returns the exact GateReport shape the frozen OpenAPI contract defines.

See the framework drafts for the registry and adapter specs: framework/skill-manifest-spec.md, framework/plugin-adapter.md, framework/ecosystem-map.md (11 stages × 8 jurisdictions).

Interface layer (Beta)

Four contract surfaces are in the trunk; all are local-trust adapters until the public 0.1 release wires production endpoints (TLS, auth).

InterfaceTransport / entryRun itVerify it
REST (demo)stdlib HTTP, 127.0.0.1:8765, POST /judgepython -m demo1.webcurl -X POST http://127.0.0.1:8765/judge -H 'Content-Type: application/json' -d @demo1/cases/case01_red_pma_process.json

| REST contract | OpenAPI 3.1, docs/openapi.yaml (/v1/judge, /v1/decisions) | — | python docs/validate_openapi.py — 5 text checks on a stdlib install, 17/17 structural once the yaml extra is installed from a checkout (pip install -e ".[yaml]"; the package is not on PyPI yet); the script prints an explicit warning when it had to skip the 12 structural checks | | SSE event stream | tails append-only demo2/events.jsonl, 6 event types | python -m demo2.sse_server --port 8770 --smoke | exits 0 only after all 6 types appear (precondition: see the SSE note below) | | MCP server (stdio) | lgd_engine/mcp_server.py | python lgd_engine/mcp_smoke.py | smoke exercises initialize / tools list / judge / RBAC-deny (denied → -32003) | | TypeScript SDK | lgd-engine-ts/ (zero-dep types mirroring OpenAPI) | cd lgd-engine-ts && npm run smoke | Node 18+; smoke exits 0 | | Container | Dockerfile + docker-compose.yml | docker compose up | REST demo on 127.0.0.1:18090 — NOT VERIFIED in the 2026-11-04 review (no Docker on the reviewing host, no container step in CI) |

Contract status note: docs/openapi.yaml freezes the production wire

shape (/v1/*, TLS, bearer auth). No /v1 service exists in the tree

yet — demo1/web.py (/judge, no /v1 prefix) is the behavioral

reference for request/response semantics.

SSE smoke precondition. The smoke asserts all six event types, so the

append-only log must already contain both a pass path and a hold path:

python -m demo2.session --case demo2/case_gate_report.json --auto and

python -m demo2.session --case demo2/case_gate_report_critical.json --auto

(or .\demo2\run_demo2.ps1 plus .\demo2\run_demo2.ps1 critical). On a

fresh clone the log is empty, the smoke exits 1, and it now names the

missing types and the exact command to generate them.

MCP client config (copy-paste, local-trust)

Run the server from a clone for now; from the public 0.1 release, pip install lgd-engine provides the lgd-engine-mcp console entry (equivalent to python -m lgd_engine.mcp_server). Both forms resolve all internal paths from the package itself, so no specific working directory is required.

Claude Desktop — claude_desktop_config.json (Settings → Developer → Edit Config):

{

"mcpServers": { "lgd-engine": { "command": "python", "args": ["-m", "lgd_engine.mcp_server"] } } }

Cursor — .cursor/mcp.json at your project root, or use the bundled .cursor-plugin/plugin.json (declares the same stdio server for the Cursor plugin host):

{

"mcpServers": { "lgd-engine": { "command": "python", "args": ["-m", "lgd_engine.mcp_server"] } } }

Platform notes:

  • Windows: python (or py -3); macOS/Linux: python3 — replace the command value accordingly, or use the absolute path of your interpreter.
  • The server binds stdio locally and trusts the caller's role claim (local-trust adapter, no network authentication boundary) — production wiring is scheduled for the public 0.1 release.
  • streamable-HTTP: the 0.1 release will also expose a streamable-HTTP endpoint; client config will then use "url" instead of command/args.

The LGD Foundation

Theory home vs. engine home. This repository is the engine implementation. The theory itself — the doctrine, the domain papers and the standards participation (ITU FG-TIDA, W3C) — is maintained in lgd-theory under the theory line; this repository neither restates nor owns it.

LGD Engine is not a hollow scaffold: it is the executable expression of a complete theory-and-evidence stack, all distilled into runnable rules.

The judgment chain is grounded in three laws:

  1. 有籍 · Registered — every judgment is tied to a registered context: a device record, a predicate, a case identifier. No context, no verdict.
  2. 有证 · Evidenced — every decision rule must cite evidence (a precedent id, a case entry, a regulation citation). A go with zero evidence refs is downgraded to hold.
  3. 有门禁 · Gated — every touchpoint is a gate (触点即门): release decisions, agent tool calls, MCP invocations and CI pushes all pass through the same three-state gate (go / hold / reject).

The rest of the stack:

  • Theory — the doctrine, specified as declarative rules in lgd_engine/theory/laws.yaml (law, trigger predicates, gate action).
  • Published work — a publication line (records registered with DataCite) that grounds the doctrine in medical-device change control and AI-agent governance; the paper accompanying this repository is under preparation and its self-citations are placeholders until registration.
  • Verified precedents — change-classification precedents (MAJ/MOD/MIN, including FDA recall events such as Z-1924-2025 and Z-0893-2026) and a library of real change-control cases, distilled into the judge rules under lgd_engine/judges/.
  • 13-domain judgment knowledge — clinical evaluation, postmarket surveillance, UDI, SaMD and more, mapped onto the 11-stage medical-device ecosystem (see framework/ecosystem-map.md and framework/eco-regulatory-matrix.md, 11 stages × 8 jurisdictions). Two domain judges are implemented in this release (510(k) change classification, post-market); the remaining domains are roadmap adapters.
  • International alignment — standards tracking lives in the theory line: the ITU FG-TIDA and W3C AI-agent memory/interop threads are followed in lgd-theory, and this repository implements the rules those threads settle rather than tracking them itself.

Every judge carries an explicit evidence source, making the chain theory → code → verifiable test (enforced in CI).

Where the rest of the stack lives

This repository is the engine. The theory, the evidence catalog and the challenge core are maintained in their own repositories, so this README links out instead of duplicating them:

  • Theory flagship (doctrine, three laws, domain papers): https://github.com/zhaoxinghua09-cell/lgd-theory
  • Doctrine DOI — concept record: https://doi.org/10.5281/zenodo.22456647 (current version v1.7.0: https://doi.org/10.5281/zenodo.23446125)
  • Portal (all public surfaces in one place): https://zhaoxinghua09-cell.github.io/lgd-hub/
  • Silent-failure catalog (failure modes this gate is built to catch): https://github.com/zhaoxinghua09-cell/silent-failure-catalog
  • uibc-core — verifiable evidence packages for autonomous agents (software DOI https://doi.org/10.5281/zenodo.22821834): https://github.com/zhaoxinghua09-cell/uibc-core
Three counts, three scopes

11 stages and 13 domains appear throughout this repository and they measure different things — neither is a count of the other:

  • 11 stages — the engine's implemented lifecycle model, i.e. the adapter family enumerated in framework/ecosystem-map.md (11 stages × 8 jurisdictions). This is an engineering projection: it covers the stages the gate can judge today or has a named adapter for.
  • 13 domains — the judgment-domain taxonomy (clinical evaluation, postmarket, UDI, SaMD, …) mapped onto those stages in framework/13domains-mapping.md. Several domains are cross-stage (compliance grading, risk management), which is why

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