Tags

Tags give the ability to mark specific points in history as being important
  • v0.5.0

    v0.5.0
    
    Added:
    
    - Added CLM v0.1 as a local projection head. It evaluates TypeSafe requests through one configured OpenAI-compatible Qwen3-8B embeddings endpoint and returns the same typed answers and probabilities as Laya and Von.
    - Added per-provider enablement. A CLM-only deployment downloads only the CLM checkpoint. `GET /v1/models` and MCP list only the providers enabled by the deployment.
    
    Changed:
    
    - Rebuilt CPU and CUDA provider layers on the matching Torchbase images. Application changes now reuse the shared Torch runtime layers.
  • v0.4.1

    v0.4.1
    
    Fixed:
    
    - Fixed MCP behind a reverse proxy. Operators can allowlist exact `Host` and browser `Origin` values without disabling DNS-rebinding protection.
    
    Changed:
    
    - Reordered final CPU and CUDA image layers so application changes reuse the already-built Laya and Von environments.
  • v0.4.0

    v0.4.0
    
    Added:
    
    - Added Docker and Compose runtime user forwarding. Direct Docker commands and Make targets pass the caller's UID and GID, so caller-owned model directories work without image-specific ownership.
    
    Changed:
    
    - CPU and CUDA images now use non-root `1000:1000` only as the fallback when no runtime identity is supplied. CUDA's Triton cache follows the selected runtime identity.
  • v0.3.1

    73e55fd4 · Release v0.3.1 ·
    v0.3.1
    
    Changed:
    
    - Rewrote the README, API guide, deployment guide, and agent setup around local model selection, typed decisions, MCP, model memory, and Docker deployment.
  • v0.3.0

    9b7bfe27 · Release v0.3.0 ·
    v0.3.0
    
    Added MCP Streamable HTTP at `/mcp` with `system_one`, `list_models`, and `unload_models` tools. MCP shares the TypeSafe request contract, model supervisor, body limit, request ID handling, and optional Bearer authentication with REST.
    
    Added a distributable MCP registry manifest, an OCI registry identity label in both CPU and CUDA images, and tag-gated MCP registry publishing.
    
    Added Claude, Codex, and OpenClaw agent integrations that explain Docker deployment, typed decisions, MCP connection, and safe use of probability-bearing results.
    
    Added tag-gated ClawHub publishing for the Decidealot skill and OpenClaw stdio bridge.
    
    Fixed CUDA inference under the hardened runtime by providing Triton's required compiler, Python headers, and narrow executable cache mount.
  • v0.2.0

    0652e359 · Release v0.2.0 ·
    v0.2.0
    
    Breaking changes:
    
    - Removed `jev` and every `jev-*` alias. Decidealot runs local Laya and Von only, and every decision request now requires an explicit supported `model` selector.
    - Removed `POST /v1/models/{model}/unload`. Use idempotent `POST /v1/models/unload` to release the single resident provider.
    - Removed `DECIDEALOT_MODEL_DATA_DIR`, `DECIDEALOT_LAYA_MODEL_DIR`, `DECIDEALOT_VON_MODEL_DIR`, and `DECIDEALOT_DEFAULT_MODEL`. Mount one host directory at the fixed container path `/models` instead.
    
    Changed:
    
    - Startup downloads and verifies both pinned model bundles before readiness, then loads model and Torch memory only for the selected provider.
    - Added Laya checkpoint selectors for automatic, English, multilingual, and typed-decision routing. Added model-selection and response-shape examples to the API guide.
    - Fixed real model-test cleanup for model files created by the container's non-root runtime user.
  • v0.1.0

    ab50d3ee · Release v0.1.0 ·
    Decidealot v0.1.0
    
    Initial release.
    
    - Added local Laya and Von execution behind TypeSafe-compatible `POST /v1/systemone` and `GET /v1/models` endpoints.
    - Added CPU and CUDA Docker images, lazy provider startup, explicit unload endpoints, and configurable idle unloading that releases the full model and Torch runtime.
    - Added pinned model download and reuse through named volumes or narrow host directories.
    - Added TypeSafe request validation, optional Bearer authentication, request-size limits, structured logs, and public API and deployment documentation.
    - Added deterministic unit and local-provider integration tests, real CPU model checks, and CUDA image validation.