Skip to documentation content
On this page
  1. Reference contract
  2. Authoritative source

Runtime manifest fields

Declares every generated runtime-layout, launcher, dependency, and audit-provenance field.

Reference contract

FieldValueDescription
nameruntime bundle identity
createdAtbundle creation timestamp
platformtarget operating system
archtarget processor architecture
pythonExecutableruntime-relative backend Python entry
scientificPythonExecutableruntime-relative workflow Python base
publicSdkPathruntime-relative directory containing telion and telion_api
backendModecompiled or development backend layout
serviceExecutableruntime-relative backend service executable
serviceArgumentsmanifest prefix arguments for service mode
cliExecutableruntime-relative backend CLI executable
cliArgumentsmanifest prefix arguments for backend CLI mode
batchExecutableruntime-relative Telion Batch executable
batchArgumentsmanifest prefix arguments ending in --batch
releaseAuditModelpackaged audit-model identity and digest
releaseAuditMeshPayloadpackaged audit-mesh identity and digest
backendSourcedevelopment-source path; absent in production
requirementsbundled requirement-lock filename
constraintsbundled constraint-lock filename
cudaRequirementsoptional CUDA requirement-lock filename
cudaIncludedwhether CUDA dependencies are bundled
pythonArtifactProvenanceartifact certification mode
pythonArtifactLockscopied platform artifact-lock set and digest
seedVenvoptional development seed-environment provenance

Release tooling writes manifest.json inside the packaged runtime. Fields whose inputs are absent are omitted by JSON serialization. Batch launchers primarily consume batchExecutable, batchArguments, scientificPythonExecutable, and publicSdkPath; packaging audits validate the full field set and runtime containment.

Authoritative source

Catalog
telion.packaged-runtime.manifest
Identity
runtime.manifest
Path
scripts/build-bundled-python.cjs
Symbol
manifest