DBabel separates runtime context, terminology evidence, review decisions and document delivery.
User request / files
|
v
+-----------------------+
| Runtime control |
| - Task Context |
| - Format Probe |
| - Capability Probe |
| - Resource Router |
+-----------+-----------+
|
| load_now only
v
+-----------------------+ +----------------------+
| Task-specific policy |<----->| Runtime knowledge |
| and document handling | | user resources |
+-----------+-----------+ | standards/vendor docs|
| +----------------------+
v
+-----------------------+
| Ingest validation |
| structure / coverage |
+-----------+-----------+
|
v
+-----------------------+
| Terminology / |
| translation reasoning |
+-----------+-----------+
|
+---------------------+
| |
v v
+-----------------------+ +-----------------------+
| Accuracy Core | | Evidence assessment |
| deterministic QA | | semantic adjudication |
+-----------+-----------+ +-----------+-----------+
| |
+-------------+-------------+
v
Human review decisions
|
v
Agent language recheck
(suggestions -> human review)
|
v
Final / checkpoint gate
|
v
round-trip / scoped output
The repository contains workflow code, schemas, policies, templates, adapters and synthetic tests. Project documents and terminology are supplied at runtime.
Project glossaries remain user/project data. Only PROJECT_APPROVED entries are
eligible for deterministic enforcement within their declared scope.
The Accuracy Core checks literal integrity and approved terminology conditions. The Agent evaluates meaning and evidence; the reviewer records decisions; the export adapter verifies the resulting copy.
Format probing is bounded and non-executing. Optional parser/detector backends are capabilities, not mandatory dependencies. A selected parser must still be followed by ingest validation before full coverage can be claimed.
The provider-backed runtime saves verified batches and artifacts under a process-held run lock, enabling recovery of inactive unfinished stages. Official SDKs and the built-in client share DBabel's bounded retries, response validation and task-level synthetic preflight. Translation memory and rejection constraints use one exact project/document scope; RapidFuzz supplies suggestions within it. Optional TMX and evidence-cache CLIs preserve provenance and report stale dependencies. Local tooling provides the entry points.