A runtime template is the immutable starting state for a class of Jio microVMs. It binds the guest environment, machine layout, devices, vCPU count, and memory size that Core is allowed to restore.
Bundle shape
runtime-templates/
<template-id>/
manifest.json
template.json
memorymanifest.jsondeclares the bundle identity and artifact digests.template.jsoncontains normalized, versioned machine state.memorycontains the immutable prewarmed guest memory image.<template-id>is content-addressed and validated before use.
Core opens, hashes, validates, and prewarms an explicitly selected bundle before serving sessions. Invalid sizes, digests, state, devices, or resource profiles fail closed.
Template safety
A reusable template must not contain:
- user workloads or repository data;
- API keys, model credentials, or access tokens;
- a network lease or open connection;
- a reusable machine identity; or
- clone-shared randomness that survives to readiness.
Identity, entropy, storage, and networking are applied after restore for each session generation.
Availability
Templates are currently managed by Jio operators. The public client cannot upload, publish, activate, or mutate a runtime template. There is no turnkey public template builder or download channel yet.
Treat templates as immutable releases. Build and install a new content-addressed bundle instead of editing one in place.