Astraform Samples v0.2.1

Astraform Samples v0.2.1

Banking and marketing starters using the renamed Astraform SDK packages, with
the existing Java and Python imports and APIs preserved.

Compatibility

• Platform: v0.4.0, delivered separately from the samples.
• Java: ai.astraform:sdk-java:0.4.5 from Maven Central.
• Python: astraform-sdk==0.3.5 from PyPI.
• Provider contracts: 1.2.3.

For source builds, Java provider tests use
ai.astraform:conformance-java:0.4.5; Python provider checks use
astraform-conformance==0.3.5. The conformance imports and
remote-domain-conformance command are unchanged.

Replace the old Python author-kit distribution when adopting astraform-sdk;
do not install both into one environment because they provide the same imports.
The container starters include their runtime dependencies. Source builds use
the checked-in Maven dependencies and PyPI registry locks.

Starter selection

Starter	Archive
Python issued banking	astraform-banking-starter-v0.2.1.tar.gz
Java issued banking	astraform-java-banking-issued-starter-v0.2.1.tar.gz
Java monthly banking	astraform-java-banking-monthly-starter-v0.2.1.tar.gz
Scheduled marketing	astraform-marketing-scheduled-starter-v0.2.1.tar.gz

Download the selected release's archive and matching checksum, verify the
checksum, then follow its bundled README. The shared release-manifest.json
identifies the source revisions, image digests and archive hashes. The manifest
inside each archive records its compatibility and file checksums. A source
dependency update does not change previously published images or archives.

The generic Java/Spring provider starter is now available as
starter-java-spring in samples source, with a standalone Maven build. It is
separate from the four deployment archives and is no longer distributed as an
SDK Maven template artifact.

The marketing example has one customer goal: understand the actual readiness
finding and get practical agency advice. The customer can clarify material
uncertainties or propose a handoff for agency feedback within the same
conversation. Scheduled and current-boundary configurations use that same goal
with different simulation start boundaries. The models choose their messages and
when to stop; the example prescribes no minimum number of turns or successful
outcome. Advice and proposal feedback do not execute the handoff or clear the
campaign for launch.

Simulation behavior

Platform configuration, customer launch, run inspection and evidence export use
the native SDKs. Partner-bank setup uses the partner-owned banking API.
Customer and partner models remain independently configurable.

Issued banking and marketing retain their authored receipt conditions and
customer-FINISH requirement. Monthly banking retains native scheduled domain
work and participation through its configured horizon. The selected platform
must support these capabilities; installing an SDK does not upgrade platform
behavior. Model decisions, unsuccessful goals and stop reasons remain visible
in the recorded evidence. Goal completion does not certify factual advice or
confirm a real payment or campaign launch.

Preserve platform database and evidence volumes. Marketing domain state and
agency conversation state remain in memory. These single-host examples do not
establish production isolation, high availability or population capacity. Keep
credentials and customer evidence private.

Published v0.2.0 artifacts retain Java SDK 0.4.4, Python SDK 0.3.4 and contracts
1.2.2. Use each historical archive with its own guide and manifest rather than
substituting its image or package versions.

Astraform-authored samples retain Apache License 2.0. Platform software and
third-party dependencies retain their separate terms.