ReferenceAvailable
Runtime manifest fields
Declares every generated runtime-layout, launcher, dependency, and audit-provenance field.
Reference
| Field | Value | Description |
|---|---|---|
| name | runtime bundle identity | — |
| createdAt | bundle creation timestamp | — |
| platform | target operating system | — |
| arch | target processor architecture | — |
| pythonExecutable | runtime-relative backend Python entry | — |
| scientificPythonExecutable | runtime-relative workflow Python base | — |
| publicSdkPath | runtime-relative directory containing telion and telion_api | — |
| backendMode | compiled or development backend layout | — |
| standaloneUpstreamBytecodeModules | upstream modules carried as bytecode in compiled standalone bundles | — |
| serviceExecutable | runtime-relative backend service executable | — |
| serviceArguments | manifest prefix arguments for service mode | — |
| cliExecutable | runtime-relative backend CLI executable | — |
| cliArguments | manifest prefix arguments for backend CLI mode | — |
| batchExecutable | runtime-relative Telion Batch executable | — |
| batchArguments | manifest prefix arguments ending in --batch | — |
| releaseAuditModel | packaged audit-model identity and digest | — |
| releaseAuditMeshPayload | packaged audit-mesh identity and digest | — |
| backendSource | development-source path; absent in production | — |
| requirements | bundled requirement-lock filename | — |
| constraints | bundled constraint-lock filename | — |
| cudaRequirements | required CUDA direct-solver requirement-lock filename | — |
| cudaIncluded | required true marker for bundled CUDA direct-solver dependencies | — |
| cudaDirectSolverRequired | required true marker that packaged solves fail closed without the CUDA direct-solver runtime | — |
| pythonArtifactProvenance | artifact certification mode | — |
| pythonArtifactLocks | copied platform artifact-lock set and digest | — |
| seedVenv | optional 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.