Templates
Templates define the structure and behavior of digital twins in Filedgr.
Template Types
Standard Templates
- Public templates covering common asset types
- Define the streams every vault starts with
- Supply a default image for vaults built from them
Custom Templates
Example template:
Template Fields
A template returned by the API carries:
| Field | Notes |
|---|---|
id | UUID |
name, description, author | Descriptive metadata |
status | UPLOAD_PENDING · UPLOADED · DELETED · ERROR |
public | Whether the template is listed for everyone |
required_streams | Stream names pre-created on every vault built from this template |
default_image, default_image_cid, image_upload_url | Template imagery |
config | Behaviour flags, below |
Configuration flags
config has exactly four boolean flags:
| Flag | Effect |
|---|---|
is_permissioned | Vault access is governed by explicit permission grants |
is_searchable | Vault is indexed for search |
is_ai_ready | Vault content is prepared for AI retrieval |
is_dynamic_streams | Streams may be added beyond required_streams |
note
Templates are not versioned. There is no version field and no semantic-versioning scheme —
updating a template with PUT /templates/{template_id} mutates it in place. Vaults already created
from it keep the template snapshot that was deployed to IPFS at creation time.
IPFS
A template's default image is pinned to IPFS when the template is created, and the resulting
default_image_cid is copied onto every vault built from it. The template record itself is not
stored on IPFS.