Aziel Runtime

aziel-runtime

Aziel Runtime starts at Softwares, FragGate, and the library. Softwares picks a slug. FragGate is the single exec door. library_lookup searches library papers and cites. Install on Glama, then call Softwares, pick a slug, and fraggate_call. 40+ research tools run through that one door. Every call can leave a receipt.

Install (remote first)

Public MCP — no API key:

https://aziel-runtime.vibelock.workers.dev/mcp

Transport: Streamable HTTP. Full client recipes: docs/AGENTS.md.

Registry: io.github.AzielEliab/aziel-runtime · Glama: Install

Access

• Public: Softwares, FragGate list/describe/call, library lookup — no auth
• Glama hosted: optional Install Server. Glama hosted-tool meters stay separate from Worker GET /v1/uses
• Local stdio: clone + cli/mcp-stdio.mjs (dev path; keep below the remote URL)

First tools

1. Softwares / fraggate_list
2. fraggate_describe → pick a slug
3. fraggate_call (use confirm: true when required)

How to use

1. Click [Install / Add to Glama](https://glama.ai/mcp/servers/AzielEliab/aziel-runtime) (also https://glama.ai/mcp/servers/@AzielEliab/aziel-runtime).
2. In any MCP client, call Softwares (tools/list name Softwares). The door runs first. Pick a slug, then fraggate_call. library_lookup searches library papers and cites. ChainLock, TemporalLock, and ForgeReceipts stamp when the call needs a ledger. confirm=true writes. dry_run=true previews and writes nothing. background=true returns Running until a receipt hash exists. Done only with that hash. tools/list stays 36.

Diagnostics, if needed: fraggate_list → fraggate_describe {name} → fraggate_call {name, op, payload, confirm:true}.

Worker remote: https://aziel-runtime.vibelock.workers.dev/mcp

Example first call: Softwares {}, pick a slug, then fraggate_call with { "slug": "foldlock", "op": "fold-preview" }. library_lookup with { "q": "Florence", "op": "search" } is a library paper or cite. Also: decisiongate_check with a short proposal and dry_run:true, or forgereceipts receipt for a completed task.

MCP tools/list is 36 tools. FragGate is the single door. Public connect is the remote URL in Install (remote first) (Streamable HTTP, no API key). Glama Install Server is optional and meters separately from Worker GET /v1/uses. Local stdio stays last. Compatible AI clients are listed below. Author: Aziel Eliab.

Designed purpose

Aziel Runtime (aziel-runtime) is a node-meshed orchestration suite of MCP-connected software designed to route catalog Softwares through the FragGate door, mint receipts, and coordinate mesh presence. Use it to list, describe, and call product operations over MCP or OpenAPI, then keep the returned receipt. It exists so each Softwares product stays a separate engine behind one door.

Start

1. node cli/aziel-runtime.mjs
2. node cli/aziel-runtime.mjs session open --local
3. node cli/aziel-runtime.mjs session status --local

The terminal prints a short summary. Add --json for the machine object. Help: node cli/aziel-runtime.mjs --help. The same three steps are in RUN.txt.

Softwares purpose copy (one_line + description) is the designed-to-do addendum on GET /v1/software (src/software-copy.js). Hubs refresh from that route.

FragGate is THE single public executable door (fraggate_list → fraggate_describe → fraggate_call). Softwares catalog is Plain → Gate → Lock; hubs refresh from GET /v1/software. Humans use Softwares in the Worker UI on the VibeLock host (browser / PWA) — no download required. Agents use OpenAPI/MCP. Optional suite pack JSON remains at /download. NodeMesh / QNM read-only suite-presence is ON by default; GET /v1/mesh never enables radios beyond that.

Version 2.0.0-rc1 is the certification-point freeze (not a feature dump): public contract, clean-room reproducibility, and external adversarial pack under docs/2.0/. No intentional behavioral breaks from 1.9.3. Remain-OFF untouched. Crawler surfaces keep the abstract above; changelog stays below. 1.9.3 closed remaining AZRT-1.9-GAPS-CLOSE items (isolate AZ-OS ethics session VFS; isolate-safe Ask Jeeves; binding-gated media-run; published independent-validation attestation path — not a third-party lab). 1.9.2 bound Browser Rendering and live D1 MASTER. 1.9.1 closed AZRT-1.9-GAPS-CLOSE isolate-safe verify. 1.9.0 closed AZRT-1.9-CLOSE-1.0. 1.7.11 is the SEO-clarity heritage that locked that lead copy.

Kernel: AzielEliab/fraggate (FG-0.1)

[Try on Glama](https://glama.ai/mcp/servers/AzielEliab/aziel-runtime) is the primary public host / discovery / install listing (also https://glama.ai/mcp/servers/@AzielEliab/aziel-runtime). Worker origin stays the execution / OpenAPI / MCP HTTP surface.

Entity graph (locked): Person @id https://www.azieleliab.com/#aziel · Runtime SoftwareApplication @id https://www.azieleliab.com/runtime#runtime. Worker origin is the execution endpoint (url). relatedLink is the Glama discovery / install host. Identity Aziel Eliab only.

open → policy → exec(slug, op, payload) → receipt → close

Agents should not narrate that chain. Prefer fraggate_list → fraggate_describe → fraggate_call { name, op, payload }. Hubs/clients: GET /v1/software.

1.3.0 vendored portable engines (ark, azai Lamb check, azclce, decisiongate, foldlock, zsolver) and ran them in this isolate.

1.2.0 was a session/receipt runtime: exec still upstreamFetched product Workers. Those receipts were not “this process ran FoldLock.”

1.1.0 was catalog + pull + proxy that started calling itself a runtime. Those front doors stay. They are not exec.

For every catalog slug session exec loads a vendored module, computes engine_digest = SHA-256 of that artifact’s bytes, runs the primary compute op inside this Worker isolate (the jail) or a local CLI jail, wipes scratch buffers, and the receipt includes engine_digest, engine_slug, engine_op, ran_in. GET /v1/health engine_slugs equals true_engine_slugs. Ops that literally cannot run without product-Worker bindings (KV / D1 / AI / live media) stay honest per-op proxy_fallback — the slug itself remains a true engine.

Cloudflare’s Worker / Durable Object isolate is the jail. No extra guest isolate is claimed. engine_digest is still required.

Hosted / in-process AZAI is still protocol mirror + Lamb check (Service → Clarity → Peace). The local core is standalone. Ollama is optional SLOT, not the identity.

Any OpenAPI-, MCP-, or HTTP-tool-capable assistant imports this OpenAPI file — then use fraggate_call. Session tools and runtime_run are advanced/internal. /p/{slug}/{op} is proxy only and is not the agent default path.

Author: Aziel Eliab Identity: Aziel Eliab (primary). Also known as Aziel Elroi Eliab (alternateName / aka only). License: Apache-2.0 Version: 2.0.0-rc1 2.0 pack: docs/2.0/ (contract freeze; self-test ≠ third-party lab) Role: engine-runtime (layer: catalog+pull+proxy+session+in-process-engines+fraggate) Door: fraggate Primary host: Try on Glama Worker (execution / OpenAPI / MCP HTTP): aziel-runtime → https://aziel-runtime.vibelock.workers.dev/ Entity parent: https://www.azieleliab.com/runtime Library mirror: https://www.azielcorpuslibrary.net/runtime Rose-star brand mark: https://aziel-runtime.vibelock.workers.dev/sigil.png Packaging: Worker session + in-repo CLI (node cli/aziel-runtime.mjs) + stdio MCP (node cli/mcp-stdio.mjs / npm run mcp). No counted runtime tarball.

Forks are welcome and always allowed. Do not invent Zenodo DOIs.

Inspect the code (not the crawler files)

Full path map: docs/2.0/INSPECT.md. How to run tests: docs/2.0/TESTS.md. Privacy: docs/DATA.md. Review / agent-assisted commits: docs/GOVERNANCE.md. wrangler.toml main is src/index.js (unminified). Cloudflare may bundle that same module for deploy — the reviewed artifact is this tree.

Compatible AI clients

Assistants / clients that can call OpenAPI, MCP, or HTTP tools:

• ChatGPT (GPT Actions / OpenAI)
• Grok (xAI)
• Venice
• Claude (Anthropic Desktop / custom tools)
• Cursor (MCP)
• Glama (Install Server / MCP)
• Perplexity
• Microsoft Copilot / Bing
• Google Gemini / Vertex AI
• Mistral
• Meta AI
• Apple Intelligence / Applebot surfaces
• Amazon Q / Amazonbot tooling
• DuckAssist / DuckDuckGo AI
• You.com
• Cohere
• plus other MCP/OpenAPI-capable assistants

Practical Add-to steps below cover ChatGPT, Grok, Venice, Claude Desktop, and Glama / Cursor MCP. Do not invent step-by-step for every crawler.

Crawl / SEO Allow set on robots.txt: GPTBot/ChatGPT, Venice, Grok, Google-Extended, GoogleOther, Google-CloudVertexBot, Claude(+Search/User), anthropic-ai, Perplexity(+User), bingbot, Meta-External*, Applebot(+Extended), Amazonbot, DuckDuck/DuckAssist, MistralAI-User, YouBot, CCBot, cohere-ai, cohere-training-data-crawler, Diffbot, AI2Bot(+Dolma), Timpibot, Petalbot, Bytespider, Omgili(+bot), FirecrawlAgent, ImagesiftBot, Cloudflare-AI-Search, FacebookBot, TikTokSpider, Baiduspider*, Yandex.

GitHub About (description / homepage / topics) is documented in docs/GITHUB.md so indexes see MCP, OpenAPI, and FragGate. Coordinator applies gh repo edit from that lock.

Websites / Live sites

[Try on Glama](https://glama.ai/mcp/servers/AzielEliab/aziel-runtime) is the primary public host / discovery / install listing. This Worker homepage stays the API / MCP / OpenAPI execution surface. Human Softwares hubs are azieleliab.com, Aziel Corpus Library, and GodLock.uk. Sister archive: [He Didn't Jump](https://www.hedidntjump.com/). Official Aziel sites: [The Furnace Isn't Free](https://www.furnaceisntfree.com/) (Aziel) and [TimeToUnsealTheBook](https://www.timetounsealthebook.net) (Aziel, HTTP 200). Neither is a Live Node.

The Worker ships a FoldLock-packed library tip (index cite + sample MASTER + About Aziel) — not the entire live corpus. Verify via FragGate foldlock/pack-verify; open via aziel-corpus/tip-pack. Honesty: docs/corpus-fold-pack.md.

Every Worker launch (homepage, /about, every /p/{slug}, HTML Softwares/describe shells) includes product-specific #hashtag parts plus the same About Aziel block. Shared partial workerLaunchHtml. Product Workers inherit About Aziel + the fold tip by copy; hashtag parts stay local. Rule: docs/WORKER-LAUNCH.md.