Schema, draft and versions
What it is
Section titled “What it is”The schema is the definition of all collections (fields, rules, views, automations, flows, sites) in a JSON manifest, heskala.collections. Large changes are made in a draft («Development», Desarrollo) and applied to production with a deploy. Each deploy is saved as a version.
How it works
Section titled “How it works”- Go to Settings → Collections → Schema (Esquema) to see the collections on a canvas.
- Switch to Development: a copy of production is created that you can edit without affecting anyone.
- Open «Development and versions» (Desarrollo y versiones) to edit the JSON, test it, see the plan and deploy.
- From the history you can load an earlier version into the draft and deploy it again.
- To export a group of collections as an app: Settings → Collections → «Export as app».
Rules and limits
Section titled “Rules and limits”- Only an administrator deploys.
- A deploy runs in a single transaction and is saved as a new version. It never deletes data or changes field types.
- There is one draft per company: if someone else has one open, do not overwrite it.
- An imported file cannot exceed 1 MB.
For agents (MCP)
Section titled “For agents (MCP)”Recommended order:
get_schema_draft(orstart_schema_draftif there is none).patch_schema_draftwith all operations together. Avoidsave_schema_draft: it rewrites the whole manifest.plan_schema_draft: review the risks and tell the person.deploy_schema_draftonly after they confirm.
Others: discard_schema_draft, list_schema_versions, restore_schema_version (loads a version into the draft) and export_schema.