ArchitectureA supervised JVM-class runtime — OLTP on seven engines, OLAP on three. AI-native, MCP-native, observable as plain SQL.Read the architecture
Está viendo la edición Perú. Está viendo la edición Colombia. You're viewing the Pakistan edition. Cambiar a la edición global →Cambiar a la edición global →Switch to the global edition →

Moving an application between dictionaries: plan, apply and restore, every kind

Code, table models, objects, REST endpoints, agents, C routines, components and documentation move between dictionaries through a plan with a verdict per item, one journal wave, a backup in the report, and a restore.

Promoting an application from a development dictionary to the next stage used to run through a 2,900-line script that cloned rows, changed every id and bypassed the journal. This release replaces it with a transport that plans before it writes, backs up what it changes, and can put it back.

Every kind moves

  • Code Functions, includes, modules, workflows, templates, OLAP schemas, triggers and routines, with an RCS version per changed body and a note naming the transport.
  • Table models A model moves with the rows it owns and the shared rows it depends on, written in dependency order; a child only the target has is kept and reported.
  • Objects, endpoints, agents, routines A table, report or view moves as the document the authoring service reads, surrogate ids removed; REST contexts and endpoints through the REST writers; agents with their tools and skills; C routines with their files.
  • Components and documentation Labels, images, messages and renders by natural key; documentation merged by folder path and page name, with the target's annotations, embeddings and history untouched.

The lifecycle

  • Plan Reads both sides and writes nothing. Each item gets a verdict: new, changed, diverged, unchanged, skipped or refused. Drafts refuse on either side, and the root dictionary refuses to be a target.
  • Apply Enabled only when the plan is applicable. Backs up the target, writes one changeset wave, records a run row with the report and the backup, and closes the header. The backup travels inside the report as text; the server stores no file.
  • Restore On the run, with a reason, while no newer run stands in the way. Items return to pending and the header reopens.
  • From a script or a job The same three verbs are a scripting binding, and the publishing job dry-runs by default and reaches the root dictionary only on explicit confirmation.

Twenty-five deviations from the old engine are recorded, each a defect it had: rows dragged from neighbouring tables, translations collapsed, histories replaced. The new one is slower to write and faster to trust.