Decidealot

Your hardware. Local decision models. Run Laya and Von through TypeSafe-compatible HTTP or MCP.

At startup Decidealot downloads and verifies both local model bundles. It then loads only the model selected by a request, unloads it after the configured idle period, and returns typed choice, score, and noul answers with model probabilities. It exposes the TypeSafe HTTP API and MCP Streamable HTTP from the same local container.

Contents

• Quick start
• Use the API
• Use MCP
• Expose MCP through a proxy
• Pick a model
• Configuration
• CUDA
• Model storage and unloading
• Agent integrations
• Docs

Quick start

You need Docker. This starts the CPU image on loopback, stores downloaded model files in one narrow host directory, and gives the container no capabilities or writable root filesystem.

model_directory="$HOME/.local/share/decidealot/models"
runtime_uid=$(id -u)
runtime_gid=$(id -g)
mkdir --parents "$model_directory"

docker run --detach --name decidealot --init --restart unless-stopped \
  --user "$runtime_uid:$runtime_gid" \
  --read-only --cap-drop ALL --security-opt no-new-privileges:true \
  --pids-limit 512 --memory 8g --cpus 4 \
  --tmpfs /tmp:rw,noexec,nosuid,size=128m \
  --tmpfs /var/run:rw,noexec,nosuid,size=8m \
  --log-driver json-file --log-opt max-size=10m --log-opt max-file=5 \
  --mount type=bind,source="$model_directory",target=/models \
  --publish 127.0.0.1:8080:8080 \
  psyb0t/decidealot:v0.4.1

Check the service, then ask Laya to make one typed decision:

curl --fail http://127.0.0.1:8080/health

curl --fail http://127.0.0.1:8080/v1/systemone \
  --header 'Content-Type: application/json' \
  --data '{
    "model": "laya",
    "state": "A proposed action would permanently delete protected data.",
    "questions": {
      "handling": {
        "type": "choice",
        "instructions": "Choose the required handling for this action.",
        "criteria": {
          "allow": "The action is reversible and does not affect protected data.",
          "require_review": "The action is irreversible or affects protected data."
        }
      }
    }
  }'

The first service startup downloads both pinned model bundles and can take several minutes. Wait for /health before sending a decision. Later service starts reuse the same host directory. The response includes answers.handling.choice and a probability per choice key. Your caller chooses what to do with that decision, for example only allowing allow when its probability meets your own threshold.

Use the API

Send the state to judge and a bounded question. Decidealot returns typed results with probabilities.

Endpoint	What it does
POST /v1/systemone	Runs the selected model against state and returns typed answers.
GET /v1/models	Lists every supported alias and the model behind it.
POST /v1/models/unload	Stops all providers.
/mcp	Version 2 MCP Streamable HTTP, with system_one, list_models, and unload_models tools.
GET /health	Reports whether downloaded model bundles are ready.

choice questions need named criteria. score questions need an ordered criteria array whose position is the score. noul questions return a probability between zero and one. The API guide has the request rules, response shape, validation failures, aliases, authentication, and lifecycle behavior.

Use MCP

The same container serves MCP Streamable HTTP at http://127.0.0.1:8080/mcp. The system_one tool takes the same model, state, and questions fields as POST /v1/systemone. list_models returns the live catalog. unload_models releases local model memory. Direct loopback clients and containers using the decidealot Docker service name work by default.

Point an MCP client at that exact URL. Its configuration format varies, but the connection values are always equivalent to this:

{
  "mcpServers": {
    "decidealot": {
      "url": "http://127.0.0.1:8080/mcp",
      "headers": {
        "Authorization": "Bearer your-token-here"
      }
    }
  }
}

Omit the Authorization header only when DECIDEALOT_API_KEY is empty. The MCP tools return structured output matching the HTTP result bodies, so an agent can inspect probabilities before it chooses the next action. A client that only supports local stdio can use the optional OpenClaw bridge described in Agent integrations. The API guide has tool inputs, output shapes, session behavior, and failure behavior.

Expose MCP through a proxy

The MCP server keeps DNS-rebinding protection enabled. A proxy, tunnel, or public DNS name must be allowed explicitly. Add the exact public Host value to DECIDEALOT_MCP_ALLOWED_HOSTS. Browser-based MCP clients must also add their exact origin, including the scheme, to DECIDEALOT_MCP_ALLOWED_ORIGINS.

For a proxy that publishes https://mcp.example.net/mcp, put these values in the Compose .env file before docker compose up -d, or pass the same variables with docker run --env:

DECIDEALOT_API_KEY=replace-with-a-real-secret
DECIDEALOT_MCP_ALLOWED_HOSTS=127.0.0.1,127.0.0.1:*,localhost,localhost:*,[::1],[::1]:*,decidealot,decidealot:*,mcp.example.net
DECIDEALOT_MCP_ALLOWED_ORIGINS=http://127.0.0.1:*,http://localhost:*,http://[::1]:*,https://mcp.example.net

Keep --publish 127.0.0.1:8080:8080 when a local reverse proxy terminates TLS. The proxy forwards the request unchanged with Host: mcp.example.net. After bearer authentication, Decidealot returns 421 for an untrusted host and 403 for an untrusted browser origin. Invalid or missing bearer credentials return 401 first. Do not disable this protection or allow a broad wildcard for an internet-facing endpoint.

Pick a model

Every request must name a selector. GET /v1/models returns the same catalog at runtime.

Selector	What it runs	Pick it when
laya, laya-auto, laya-latest	Laya with automatic checkpoint routing.	State may arrive in more than one language or script.
laya-english	Laya's English checkpoint.	State is English and uses the Latin script.
laya-multilingual	Laya's multilingual checkpoint.	State is in another language or script, including short Latin-script text that is not clearly English.
laya-typed-decisions	Laya's checkpoint tuned for structured workflow decisions.	Your workload looks like repeated policy, routing, triage, or approval decisions. Validate it on your own cases first.
von, von-latest, von-1.1, von-1.1.0	The local English-only Von 1.1 model.	You want Von's independent result for a short, well-posed decision, or want to compare it with Laya before standardizing a workflow.

What differs

Laya is one model family with three checkpoints. Its automatic selectors choose English or multilingual checkpoints from the input script and a language heuristic. Use laya-multilingual for known non-English short Latin-script messages. laya-typed-decisions targets repeated structured decision work.

Von is a separate English-only decision model for short questions with clear criteria. Both models take the same TypeSafe state and questions shape and return typed choice, score, and noul answers with probabilities. Your application applies the threshold and action that follow.

Decidealot keeps one provider resident. Moving between Laya selectors stays in the Laya provider. Moving between Laya and Von waits for active work, releases the old provider and its Torch memory, then starts the other one.

Set DECIDEALOT_PROVIDER_IDLE_UNLOAD_SECONDS to choose when an idle provider releases its model and Torch memory.

Configuration

Pass configuration with --env-file or your container manager. The image uses fixed internal ports. Docker port publishing controls where the service is reachable.

Variable	Default	Meaning
DECIDEALOT_API_KEY	empty	Optional Bearer token for every public API and MCP request.
DECIDEALOT_MAX_REQUEST_BYTES	1048576	Maximum JSON request body size.
DECIDEALOT_PROVIDER_IDLE_UNLOAD_SECONDS	600	Idle time before automatic unload. Set 0 to disable only timeout-based unloads.
DECIDEALOT_MCP_ALLOWED_HOSTS	loopback names and decidealot	Comma-separated Host values accepted by MCP. Add each reverse-proxy hostname here.
DECIDEALOT_MCP_ALLOWED_ORIGINS	loopback HTTP origins	Comma-separated browser origins accepted by MCP. Add each public browser origin here.

The container always stores bundles under /models. Its only model storage setting is the host directory mounted there. Keep the loopback bind for one-host use. Before putting Decidealot behind a proxy, tunnel, or public address, set DECIDEALOT_API_KEY to a real secret, require Authorization: Bearer <your-key> from every caller, and configure the precise MCP host and origin allowlists above.

CUDA

psyb0t/decidealot:v0.4.1-cuda uses CUDA 12.6 and needs a compatible NVIDIA driver, NVIDIA Container Toolkit, and --gpus all. CUDA images are amd64-only. The CPU image is the right default unless inference speed and model memory justify the GPU setup.

model_directory="${model_directory:-$HOME/.local/share/decidealot/models}"
runtime_uid=$(id -u)
runtime_gid=$(id -g)
mkdir --parents "$model_directory"

docker run --detach --name decidealot --init --restart unless-stopped \
  --user "$runtime_uid:$runtime_gid" \
  --gpus all --read-only --cap-drop ALL --security-opt no-new-privileges:true \
  --pids-limit 512 --memory 8g --cpus 4 \
  --tmpfs /tmp:rw,noexec,nosuid,size=128m \
  --tmpfs /var/run:rw,noexec,nosuid,size=8m \
  --tmpfs /var/cache:rw,exec,nosuid,nodev,size=512m,uid=$runtime_uid,gid=$runtime_gid,mode=0755 \
  --log-driver json-file --log-opt max-size=10m --log-opt max-file=5 \
  --mount type=bind,source="$model_directory",target=/models \
  --publish 127.0.0.1:8080:8080 \
  psyb0t/decidealot:v0.4.1-cuda

CUDA needs one writable executable cache because Triton compiles and loads short-lived CUDA helpers there. The rest of the container remains read-only and noexec. Deployment has the complete CPU, CUDA, authentication, persistent-storage, and host-directory recipes.

Model storage and unloading

Mount one narrow host directory at /models. Decidealot creates and manages /models/laya and /models/von inside it. The Docker commands run as your current host UID and GID, so a directory you create yourself is writable without an image-specific chown. The image falls back to non-root 1000:1000 only when no runtime user is supplied.

Unload the loaded runtime when you are done with it:

curl --fail --request POST http://127.0.0.1:8080/v1/models/unload

Only one provider can be loaded, but the endpoint reports both providers so the result is clear. Unload terminates the provider process, so it releases model weights, Torch allocations, worker threads, and the CUDA context. A later request starts it again.

Agent integrations

Install the Decidealot skill from the psyb0t marketplace after the release that contains it. The skill tells an agent how to deploy the Docker image, choose Laya or Von, submit TypeSafe decisions, read probabilities, use direct MCP, and use the stdio bridge only when its client needs one.

claude plugin marketplace add psyb0t/agents
claude plugin install decidealot@psyb0t

codex plugin marketplace add psyb0t/agents
codex plugin add decidealot@psyb0t

OpenClaw can install the skill or its stdio bridge. The bridge forwards stdio traffic to a Decidealot container you already run.

openclaw skills install @psyb0t/decidealot
openclaw plugins install clawhub:@psyb0t/decidealot

Docs

Doc	What it covers
API	TypeSafe request and response shapes, errors, authentication, aliases, and provider lifecycle.
Deployment	Hardened Docker commands, CUDA, persistent model directories, and exposure rules.
Changelog	User-visible changes by version.

License

Decidealot code is WTFPL. Laya, Von, PyTorch, Transformers, and each downloaded model keep their own upstream licenses. Read those before putting a model into a commercial product.