What a template is — and isn't
When a creator publishes a template, jurniti sparse-copies their VM's persist drive (/dev/vdb) and zstd-compresses it into shared storage. That blob is the template. It captures everything the harness wrote to persist:
- Harness config + system prompts
- Conversation memory, embeddings, vector stores
- Custom skills, tools, scripts
- Datasets and uploaded files
It does not capture VM memory state — templates are persist-only in v1. The harness reinstalls itself fresh on first boot of the forked VM, then reads the inherited persist drive and picks up where the creator left off.