PROTOCOL · TYPED DSL · URI PROCESS · 0.2.0rc2

One manifest.
Every environment.

Exchange typed configuration, publish through guarded URI Processes, select an LLM by deterministic format capability, and serve browsers, services, Raspberry Pi devices, queues and digital twins in the format each side prefers.

Try conversion Plan a publication

JSONYAMLHCLtyped@1TypeScriptproto3policy-sh

publication.wm.yaml

schema: subactor.projects/v1
project: obslugabiurowa-pl
publish_uri:
  plesk://host/site/command/sync
verify_uri:
  plesk://host/site/command/publish-verify
contract: contract:plesk-publication
mutation: dry-run-by-default

twin facts→plan→signed apply→receipt

8dialect frontends

7exact Plesk URI routes

3diagnostic severities

0implicit authority grants

ARCHITECTURE

Different syntax. Common meaning.

Each dialect has its own parser. Documents normalize into canonical data/IR, pass schema and policy checks, then travel inside one envelope.

Author

JSON / YAML / TOML HCL-compatible Strongly typed DSL Safe TypeScript data Policy DSL / proto3

CANONICALWellManifestEnvelope + IR

Run

Browser / WASM Backend / gRPC MQTT / IoT Plesk / URI Process Digital twins / LLM

HTTPWebSocketMQTT v5protobuf / gRPCCQRS / Events

POLYGLOT RUNTIMES

Local when capable. Remote when constrained.

A runtime declaration selects a compatible implementation; it never uploads arbitrary code or expands Contract AQL authority.

◫

Frontend

Dependency-free JavaScript SDK, WebSocket streams and a WASM build path.

runtime:frontend-wasm@1

⌘

Backend

Python reference service, Rust core scaffold, HTTP/gRPC and append-only events.

runtime:backend-python@1

⌁

Firmware

Thin HTTP/MQTT clients delegate parsing and execution to an edge gateway.

runtime:firmware-thin@1

◇

Digital twin

Read-only portraits and environment facts; effects stay in authorized connectors.

runtime:digital-twin-readonly@1

PLESK PUBLICATION

Review facts. Dry-run exact files. Apply one signed plan.

A `subactor.projects/v1` registry becomes a deterministic plan. URI Twin is read-only; `urirun-connector-plesk` performs the guarded effect.

Preflight

Connector readiness, subscription capacity, DNS authority/propagation and non-mutating TLS evidence.

wellm plesk-plan …

Dry-run

The connector computes the exact file/hash plan and returns a reviewable plan_hash.

apply=false

Guarded apply

Mutation requires green gates, the unchanged connector hash and a signed single-use grant.

--apply --plan-hash …

Verify

Final receipt checks DNS, TLS, HTTPS and content evidence for the declared deployment.

publish-verify

EXAMPLE

Plan `obslugabiurowa.pl` locally.

wellm plesk-plan examples/plesk/projects.json \
  --project obslugabiurowa-pl \
  --source-ref workspace:obslugabiurowa-pl=examples/plesk/site/www \
  --workspace-root . --to yaml

ADAPTIVE LLM ROUTING

Choose the cheapest model that can preserve your protocol.

Models are tested on synthetic fixtures before the real request. Parsing, JSON Schema and exact normalized semantics decide the result—never another LLM judge.

{ }

Formats

JSON, YAML, typed WellManifest, HCL and a restricted TypeScript data module.

formats: […]

✓

Logic

URI wildcard permissions, concrete execution and fail-closed publication gates.

semantic equality

Cost

Tokens, latency and response cost are retained when supplied by the provider route.

prefer: lowest_cost

↺

Cache

The winner is cached by benchmark fingerprint; the actual request goes to one selected model.

FirstRequestModelSelector

LIVE PLAYGROUND

Convert through the running gateway.

The page calls /v1/convert. Start the runtime locally or with Compose to use it.

InputDialect

OutputDialect

Select Convert to contact the runtime.

INFO Ready.

FAIL-CLOSED BY DESIGN

Wildcards grant scope.
Only concrete URIs execute.

Credentials stay outside manifests. Plesk apply requires an exact reviewed hash and signed grant. LLM output remains untrusted until deterministic validation passes.

1Parse without shell or TypeScript execution
2Validate type, schema and normalized meaning
3Authorize a concrete URI server-side
4Execute a registered adapter only
5Record an idempotent receipt/event

ECOSYSTEM

One protocol across the stack.

Use	Package / service	Preferred runtime	Boundary	Status
Browser configuration	`@wellmanifest/wellm-sdk`	JS / WASM	HTTP · WS	working
Backend orchestration	`wellm-server`	Python / Rust path	HTTP · gRPC	working RC
Plesk publication	`wellm.plesk`	Control / bridge	concrete URI · receipt	tested planner
LLM model selection	`wellm.llmbench`	Python + LiteLLM	schema · semantics · cost	offline tested
IoT / firmware	thin client + bridge	remote edge	MQTT · protobuf	source
Digital twins	situation + router	read-only server	events · URI	working demo
Native bindings	Rust / PyO3 / N-API	local native	FFI	scaffold

START WITH A SIDECAR

Give every language one manifest gateway.

docker compose up --build runtime
curl http://localhost:8080/v1/capabilities
wellm benchmark-llm examples/benchmark/config.yaml --mock

One manifest.Every environment.