Skip to content
AntFabric Corev1.0.0local

What's ready and what's next

  1. Create it: pnpm plugin:new <name> here, or antfabric plugin new <name> in your own core instance (Devkit).
  2. Declare it in plugin.yaml: permissions, routes and screens, workflows, events, notifications, contracts, configuration (Anatomy).
  3. Build server code, workflows and screens with the SDK only (Server side, Background work, Screens).
  4. Check with tests, pnpm plugins:check --boot and pnpm api:spec (Testing, Review checklist).
  5. Pack it: antfabric plugin pack gives a versioned tarball, plus a contracts-only one.
  6. Add it to an instance: antfabric plugin add. It is selected in the instance file.
  7. Deploy: the instance’s image is built with its selected plugins, and the migration job creates the plugin’s schema and database role.
  • Server:
    • routes behind core’s guards;
    • its own database role and schema;
    • configuration and secrets;
    • files with quotas, multipart uploads up to 5 GiB;
    • resources in the manifest: larger bodies, CORS headers, file limits, Postgres extensions (vector), runtime assets;
    • a cache, rate limits by cost, concurrency slots;
    • audit;
    • people lookup, search and lookup by email; accounts with roles and active state when the manifest asks (people.accounts);
    • read-only views of core data (core_v1.users, roles) and foreign keys to users(id);
    • the installed and removed plugins (PluginRegistry), and one-off tasks (antfabric plugin run <id> <task>);
    • shared rate limits;
    • metrics and spans;
    • @Idempotent() for retried writes.
  • Background work: workflows and schedules, periodic jobs (PluginJobs.every), child workflows, continueAsNew, heavy activities on their own pool, a worker pool of your own (workers.pool: own), starts in your transaction.
  • Live and async:
    • live events to the apps, with your own recipient filter;
    • server-side events between plugins, at least once, with retries per subscriber, and core’s own (a person deactivated, roles changed, a plugin removed);
    • notifications by inbox, email and push.
  • Between plugins: contracts that are versioned, optional or required, or extension points with many providers. Core attaches the acting person, and they work in Activities and event handlers.
  • Screens: web, App Admin, desktop and phone; navigation by route id (a route may open App Admin); the UI kit; lazy loading, a shared data layer refreshed by events, permissions in the client, translations, slots, device access and a screen testing kit.
  • Instance setup: version pins, optional integrations switched off, secrets from environment variables, all in the instance file.
  • Shipping: packed plugins, a production build with contracts compiled in, and API schemas namespaced per plugin.

Phase F (screen foundation) is done: lazy plugin screens, usePluginQuery / usePluginMutation, usePermission and <Can>, translations with useT, slots, the screen testing kit, device access and VirtualList (Screens). Still open:

Coming Until then
A language picker in the web shells The phone’s picker sets the language; web follows the browser
Slots on the phone Link to the other screen by route id
Developer experience fixes from the plugin team See the plan’s §8

The order and details are in the core hardening plan (apps/documentation/docs/meta/core-hardening-plan.md).