Skip to main content
Glama
tetracoralla

Gridlace

Official
by tetracoralla

Deterministic Dependency Engine

Dependency reasoning over declared graphs for humans and AI agents.

Dependency engine workspace showing a declared graph and computed release plan

It answers five questions over relations you declare:

  • Is this dependency graph valid and acyclic?

  • What remains before these targets can be completed?

  • What can run now and in which parallel layers?

  • What will these changes affect?

  • Why is this target blocked or affected?

The engine proves derivations over declared relations. It does not prove that the declared business relations are true.

This repository is deliberately limited to dependency reasoning. It is not a general orchestration standard, provider-selection framework, task runner, graph discovery system, graph database, or visual graph editor. Its browser workspace includes an optional read-only 3D sphere for inspecting the declared dependency graph; editing remains explicit JSON and all calculations still use the deterministic core.

Graph contract

{
  "schema": "agent-deps/v1",
  "nodes": [
    { "id": "schema" },
    { "id": "backend" },
    { "id": "release" }
  ],
  "requires": [
    { "dependent": "backend", "prerequisite": "schema" },
    { "dependent": "release", "prerequisite": "backend" }
  ]
}

Public edges never use ambiguous from / to keys.

Related MCP server: ASR Graph of Thoughts (GoT) MCP Server

Develop

Use Node.js 22.12 or newer.

This repository is the public source distribution. It is not currently published to the npm registry.

npm ci
npm run check
npm run start:ui

The browser workspace opens on a transparent Sphere: declared dependency curves and depth-coded nodes form the spatial volume, without a solid globe. Rotate, zoom, or focus it; open Source for exact JSON and Analysis only when query controls and results are needed. The viewer lives in a separate browser-only chunk. It adds no Agent tools or schema fields and stores no camera or layout state in the graph.

After npm run check, CLI requests can be run from a clone as operation-specific JSON read from standard input or an explicit --input file:

node dist/adapters/cli.js resolve --input request.json --pretty

If you install a locally packed copy, the same entry point is available as dependency-engine.

The MCP server exposes graph_validate, dependency_resolve, dependency_impact, dependency_slice, and dependency_explain. The local HTTP adapter exposes matching POST /v1/* routes and GET /health. When the npm package is installed from a local pack rather than cloned, run the MCP entry point as node node_modules/@openadam/dependency-engine/dist/adapters/mcp.js.

Start the built local HTTP adapter with:

node dist/adapters/http-server.js --host 127.0.0.1 --port 8787

The HTTP adapter defaults to 127.0.0.1 and is intended for trusted local use. It does not provide authentication, authorization, or TLS. Do not expose it directly to an untrusted network; see the security policy.

License

Copyright 2026 openAdam. Licensed under the Apache License 2.0. Bundled browser dependencies are documented in the third-party notices.

See the product identity, product model, and review contract for exact boundaries.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

No tool schema history has been recorded yet.

Maintenance

ActivityMaintained
ResponsivenessNo issues

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/tetracoralla/deterministic-dependency-engine'

If you have feedback or need assistance with the MCP directory API, please join our Discord server