LogoDicto Docs

Versions, provenance and validation

Identify the maintained setup snapshot, image pins, adaptations and limits of documentation validation.

The downloadable core reference is derived from a maintained deployment configuration snapshot, revision 3de2ef19266e4276df6191da7a887058d7cedb61, exported on 2026-11-05. The bundle's versions file travels with the example. It is not a claim that every optional production component is represented or that the bundle has been installed on every platform.

ComponentReference selection
Dicto API/migrator/jobsv2.4.2, pinned to one image digest
Management Digest snapshot of the maintained latest image on 2026-11-05
PostgreSQL18.3 with pgvector 0.8.3 and pg_textsearch 1.3.1
RustFSDigest snapshot recorded in the Compose file
Inference gatewayv1.0.12
TranscriptionvLLM 0.26.0 + matching audio dependencies; public Whisper large-v3
Text generationvLLM 0.32.0; GPT-OSS 120B
PlatformLinux AMD64; NVIDIA hardware required by the GPU overlays

Product/storage digests are in the canonical Compose download. Other named image versions remain registry tags; upstream model revisions are not immutable pins in this example. Record the resolved model revisions and any additional digests in your deployment change record. Do not infer a supported app/server matrix from a moving tag or the date of a page.

Adaptations from the maintained deployment#

The example replaces organization hostnames, SSO registrations and credentials, isolates data/network names, and combines the core orchestration under one Compose project. It preserves the path-based API/management deployment and separate backend roles. Public Whisper replaces the private local checkpoint and custom patches, so optional audio capabilities are left off. The sample auth profile bootstraps a new administrator instead of copying an existing SSO or passkey configuration.

Organization-specific integrations, additional AI models, retrieval/document workers, Scripto's agent runtime, clinical assets and full monitoring are outside this download. Their absence is explicit; enabling related UI does not install them.

What validation establishes#

The docs pipeline checks page links/anchors/search, generated artifact hashes, canonical embedded examples, generated Markdown/index coverage and archive/member checksums. Both reference Compose profiles are rendered in CI without pulling private product images. The mounted reference configuration also passed validate-config --resolve-env locally with the pinned v2.4.2 image and example values on 2026-11-05. These checks do not contact identity providers, run GPU models or validate the accuracy of a transcript. A fresh GPU/product end-to-end deployment must be performed by the operator; it is not run in the docs build.

Local container smoke checks also verified the pinned management image serves /management/, its callback document and a nested route with the intended base path. The gateway accepted the sample route file, rejected an unauthenticated model-list request and returned the configured aliases with the example key. These isolated checks did not perform real administrator sign-in or upstream model inference.

Exported schemas have their own manifest recording the private-source revision and checksums. They are reviewed snapshots, not a full compatibility guarantee for every product release. The deployed image's validate-config --resolve-env check is authoritative for the settings it accepts.