Extensions And Compatibility#
The AISDL Specification is an open framework. Its common reference covers broad enterprise needs, but it does not freeze the future. Implementors can add documented utilities and Services. A System can use them when its Designer has their contracts and its target AISDL Runtime supports them.
This guide defines the extension framework. It does not add new fields to the existing resource schemas or invent new AISDL AIScript syntax.
Utilities#
A utility supplies operations over values, such as Dates calculations. Its contract states its name and version, exact methods, arguments, result types, behavior, errors and working examples. State whether an operation depends on a clock, randomness or other execution context. A utility must not hide external effects behind a value operation.
An additional utility uses an interface form supported by the language. Adding a new language construct requires a versioned language amendment, not just an implementation helper.
Services#
A Service supplies an explicitly declared capability. Its contract includes exact callable methods, types, behavior and errors, plus configuration, credential needs, permissions, lifecycle, timeouts and external effects. Use the same declaration and lookup rules as other Services.
A Service implementation must not expose an unrestricted host handle to Process code. Its effects remain subject to Runtime policy. A new adapter cannot silently change an existing Service interface.
Teach The Designer The Applicable Contracts#
Supply the actual common reference and every extension contract required by the target environment to the AI before it designs with them. A feature name alone does not teach its interface. The AI owns the business design and can freely combine the supplied capabilities without inventing methods.
Keep a compatibility record alongside a release: the reference snapshot, required extension names and versions, adapter identifiers, and applicable support evidence. This record is not a new manifest.json property required by the resource schema.
Provider Extensions And Common Amendments#
A provider may publish a clearly identified extension without claiming that every AISDL Runtime supports it. An extension becomes common only through an accepted, published revision of the community reference.
An amendment proposal supplies its purpose, complete contract, examples, compatibility impact and reproducible tests. Until an explicit community decision and published revision exist, it remains a proposal. The current community reference does not imply an established standards-body approval process.
Keep ownership and version information unambiguous. An incompatible change needs a distinguishable version or name. Two providers must not claim the same unchanged interface while implementing different meanings.
Portability#
A System is portable between Runtimes that support its required contracts with compatible semantics. Optional provider extensions narrow that set unless another provider implements them too.
The current Service reference includes concrete adapter identifiers. These are part of the compatibility requirements, not universal backend mandates. A destination must support them or establish an explicit compatible mapping. It must not silently substitute an adapter and assume equivalent behavior.
The local cache belongs to one execution engine's memory; another engine has independent contents. The reference's JVM terminology describes the current implementation profile. A Runtime using another host language must document an equivalent scope. A shared cache uses a shared store; it is not a local cache with a different name.
Moving a System also requires data and history transfer, credential provisioning, integration and policy mapping, and a safe handover of in-flight work. Matching specifications do not perform these operations automatically.
Evidence#
Publish a version-specific support matrix, interface tests, security and resource limits, and known differences. Passing examples does not establish complete semantic equivalence or industry certification. A Runtime conformance claim identifies the exact contracts and tested scope.