Skip to main content

appcore-sdk

Stable documentation ID: ACR-028.

Published release: appcore-sdk 1.0.0-rc.2.

appcore-sdk is the application-facing facade. It gives business code a small manifest-first surface while specialized crates continue to own storage, scheduling, synchronization, AI, document generation, and deployment integration. It replaces the retired appcore-bin; the SDK does not preserve that crate's host or Runtime CLI.

Migration from appcore-bin

The final registry release of appcore-bin is only a retirement notice. New applications must depend directly on appcore-sdk. Existing applications keep their manifests and business code, replace appcore_bin imports, and let their deployment executable own providers, listeners, workers, and shutdown.

Choose it when​

  • starting an external AppCore application from the three artifacts;
  • implementing Application and registering commands, events, queries, decisions, states, handlers, or tasks;
  • using canonical local defaults before supplying explicit V1 manifests;
  • opting into capability namespaces without manually composing a Runtime host.

It does not start an implicit network listener, choose providers, resolve secrets, or own process lifecycle. Deployment composition remains explicit.

Main contracts​

  • run and App provide the smallest validated local context;
  • Application defines application-owned registration hooks;
  • manifest reexports the canonical V1 manifest contracts;
  • feature-gated namespaces expose API, deployment, scheduler, storage, sync, AI, and FileMaker contracts;
  • App::logging configures the bounded appcore-log pipeline.

Start with the first application tutorial and the crate-owned English guide, Portuguese guide, or French guide. Then run the crate-owned basic example and intermediate example.