Skip to content

ddcore 0.2 ​

This series was written after the fact, from the repository's history. It records what an app would notice in each release — a capability, a contract, a default — and not every commit that went into it.

0.2.0 — 2026-09-11 ​

Added ​

  • Job administration (PRD-04): ddcore jobs, a System Manager-only HTTP surface and MCP tools inspect, retry and cancel jobs — a running job is cancelled cooperatively — with per-queue and per-method metrics, a daily retention sweep whose windows live in ops, and the request_id of the request that queued the work carried onto the job. See operations.
  • An action can be attached to a field, not only to the document, so the button sits beside the input it fills and the framework can see it: a translated label, hidden and dependsOn instead of an HTML field, an esc() per app and a delegated click listener.
  • desk.logo finally does something: the brand mark is the one declared by the first app in load order, or the initial of the site's name, in the sidebar and on the sign-in screens alike.

Breaking ​

  • site is gone from ddcore.json, from config.File and from engine.Config. The site's name is now the title of the first app that is not the core, resolved on the server so that the sidebar, a recovery e-mail and /health cannot disagree, and translated for whoever is reading. A config that still carries the key loads and ignores it, so no deployment breaks — but every one of them is renamed by its app on the next start, and a site that wants a name other than its app's title no longer has a way to say so. doctor loses its site: line, and /health can no longer tell two deployments of one app apart.

Fixed ​

  • The site's name is a catalogue key wherever it is shown, in the sidebar and in the mail.

MIT Licensed · ddcore (Data Driven Core) · Development documentation (main)