appcore-sdk
Release candidate appcore-sdk 1.0.2-rc.4. Select this RC explicitly; it does not replace earlier stable releases or certify a deployment. Internal AppCore dependencies, where present, are pinned to each dependency’s independent RC.
The runtime benchmark measures default facade construction, empty
App::prepare, and preparation with 32 registered commands. Run
cargo bench -p appcore-sdk --bench runtime; set APPCORE_BENCH_CASE to
construct_defaults, prepare_empty or prepare_32_commands to isolate one
case. The benchmark is also discoverable by appcore-dev bench. It measures
construction, validation and teardown, not HTTP startup or cluster operation.
Building with --features full changes the linked feature profile; it does not
exercise every optional capability.
appcore-sdk is the documented application facade for AppCore. It keeps a
new application's dependency surface small and delegates infrastructure to the
crates that own it. It replaces the retired appcore-bin; it does not preserve
the old Runtime host or CLI.
use *;
Implement Application when registering commands, queries and tasks for an
explicit deployment. The base facade only requires contracts and the Runtime
core plus bounded logging. App::prepare executes every registration hook and
returns immutable Core registries, a frozen query router and bounded task
definitions without starting a host. Enable api for HTTP queries, scheduler for scheduled work,
deployment for provider-resolved bindings, or storage, sync, ai and
filemaker only when those capabilities are required. Provider composition,
listeners and process lifecycle remain application/deployment concerns rather
than library responsibilities.
Executable examples
Examples are grouped by progression under examples/: 01-basics,
02-manifests, 03-application, 04-storage, 05-sync, 06-ai and
07-filemaker, 08-logging and 09-api. Start each with
cargo run -p appcore-sdk --example NAME; the
capability examples require the corresponding SDK feature. They cover every
public SDK path without pretending that deployment process composition is an
SDK capability.
Use App::logging(LoggerConfig) to select terminal, bounded JSONL file, both,
disabled, or crash-only output. File names, per-file bytes, active rotations
and the optional YYYY/MM archive are explicit. Crash-only output is written
with App::dump_crash_log; it creates no file during normal execution. See
08-configured-logging.
Stable documentation
Stable ID: ACR-028. See the supplemental architecture and integration guide. This permanent ID remains valid if the wiki page moves.
Existing applications should follow the crate-owned migration guide.
DiagnosticBundleBuilder creates a bounded DiagnosticBundleV1 for support
reports. It covers platform, environment, versions, a non-reversible storage
fingerprint, Gateway/sync/update status and recent safe errors. Text is
redacted and bounded before export, secrets and raw paths are excluded by
default, and to_json emits the stable schema marker
appcore.sdk.diagnostic.v1. Sensitive opt-in is recorded explicitly but does
not cause this SDK bundle to collect secret values.
EnvironmentProfile standardizes dev/QA/production, local/release,
desktop/sync-node/mobile, standalone/cluster, optional cluster/tenant labels,
storage namespace and update channel. It rejects incoherent combinations and
provides diagnostic_label() without exposing secrets or paths. Call
validate_namespace_separation before promoting between non-release and
release storage namespaces.
Use CapabilityRegistry to declare application capabilities and map commands
to them. coverage reports commands without a mapping and enforces bounded
registration. CapabilityOutcome standardizes authentication_required and
permission_denied transport outcomes; the SDK does not evaluate business
authorization or grant permissions.
Small causal composition
This section describes unpublished source changes. Verify the exact registry package before consumer adoption.
Enable only sync to access the new revision classifier through appcore_sdk::sync. Default features remain empty. SQLite, Update host adapters, Gateway and Tauri remain explicit deployment dependencies, not a hidden SDK process host. FileMaker IPC diagnostics stay in the owning crate. The executable sync recovery example uses opaque events and memory transport without a real Gateway; durability and host installation require separate provider/adapter qualification.
Release candidate — 2026-10-14
1.0.2-rc.1: source changes.
1.0.2-rc.3
Dependency-only RC: exact internal pins select the qualified AI security distribution and FileMaker RC where applicable. Public APIs, default features and V1 inputs are unchanged. Select the new exact version and refresh the full lockfile explicitly; old exact pins remain immutable. Rollback requires assessing the older optional Candle ZIP vulnerabilities.
Negotiated HA availability — 1.0.2-rc.4
The opt-in peer.availability.v1 profile separates local transport failure, authenticated rejection, pending execution and durable confirmation. It preserves frozen V1 behavior for V1 peers and never treats a transport ACK as business durability. Deployment composition must supply the durable executor and distinct request/response authentication. See the availability contract and adoption requirements.