The supported runtime workflow begins with an initialized workspace and
profile-specific readiness, submits one typed v2 operation, resolves its
durable result, and inspects the authoritative run before replay or recovery.
the named operation and profile have their exact dependencies
readiness does not execute or allocate a job
v2 ingest and v2 index
source bytes and an immutable profile-selected index are retained
input formats, model state and resource policy remain enforced
v2 search, v2 ask, and v2 research
bounded evidence, grounded claims and research traces are produced from retained state
claims remain limited to resolvable cited evidence
v2 run
the complete linked workflow executes under one durable authority
terminal job status is separate from result and inspection payloads
v2 replay and v2 compare
a new attempt is bound to retained inputs and compared under declared dimensions
replay cannot reconstruct missing source or artifact bytes
v2 backup and v2 restore
the database, CAS, indexes and workspace controls form a verified recovery set
backup refuses live work, symlinks, drift and external model state
HTTP v2 liveness/readiness
process liveness plus initialized, ingest, index, retrieve, ask, research, or run dependency checks
readiness is scoped by the requested operation
CLI/HTTP/Python capability discovery
effective configuration origins, active identities, installed formats/providers, and readiness matrix
reports actual installed support without enabling a provider or mutating state
Start with the strongest demonstrated surface that answers the operational
question. Do not use dry-run success as a live readiness result or one
capability's readiness as evidence that a stronger operation is ready.
DuckDB is the durable local authority, not multi-host infrastructure. Runtime
includes a local durable job worker and governed backup/restore, but it is not a
sandbox, cluster scheduler, identity provider, secret manager, TLS terminator,
or tenant-isolation boundary. Hosts must enforce process and network isolation,
access control, encryption, capacity, retention and credentials.