Arcane OSSDK docs

Capability contract

Newer is allowed only when required behavior remains.

An application may run on a newer Arcane Core. Version alone never substitutes for a missing protocol, feature, capability, or method.

Admission checks the complete declared contract

  • Target

    The requested target appears in every selected or bundled app descriptor.

  • Core floor

    The host Core meets the highest minimum declared by the SDK runtime and complete app closure.

  • Protocol

    requirements.arcaneProtocol matches the host protocol generation.

  • Features

    Every declared feature is advertised by the host.

  • Capabilities

    Every requested capability is available to the app boundary.

  • Methods

    Every declared method exists with compatible meaning.

Example

app minimum 0.8.12host Core 0.9.0Allowed only if every declared contract remains

A higher semantic version does not override one missing method. Conversely, an exact version equality requirement would reject safe non-breaking Core upgrades unnecessarily.

Breaking changes must become visible

A host must stop advertising an old protocol, feature, capability, or method when its meaning or guarantee changes incompatibly. Change the protocol generation or contract identifier so admission fails before provider build or launch.

Compatibility and integrity answer different questions

Compatibility

Can this host still provide every behavior the app declared?

Integrity identity

Which exact SDK runtime, release, toolchain, and artifact bytes were verified for this build state?

Hashes and lock identities do not require the installed Arcane version to equal the app's minimum forever.