Astraform Samples v0.2.0

Astraform Samples v0.2.0

Native customer simulation samples for banking and marketing, with independently
configured customer and partner models.

Compatibility and starter selection

The source uses Java author kit 0.4.4, Python author kit 0.3.4 and
contracts 1.2.2, targeting a separately delivered platform v0.4.0.
Use the artifacts listed by the selected platform and samples releases, and
verify their manifests and checksums. Platform v0.3.0 provides strict customer FINISH support;
explicit banking domain identity and marketing
requestFactBindingMode: "RESOLVE_TRUSTED" require v0.4.0 or later. Packaging
records the selected scenario's requirements without silently removing fields.

Starter configuration	Archive	Customer and domain behavior
Python issued banking	astraform-banking-starter-v0.2.0.tar.gz	Python bank; issued statement; qualifying receipt and customer FINISH
Java issued banking	astraform-java-banking-issued-starter-v0.2.0.tar.gz	Java bank; same strict issued-statement rule
Java monthly banking	astraform-java-banking-monthly-starter-v0.2.0.tar.gz	Java bank; native monthly statement work and retained participation through the horizon
Scheduled marketing	astraform-marketing-scheduled-starter-v0.2.0.tar.gz	Marketing domain work, Creative Agency reply and customer FINISH

Download the artifacts listed by the selected release and verify each archive's
checksum before extraction. The shared release-manifest.json identifies source
revisions, image digests and archive hashes. Source dependency pins do not update
existing images or establish their installed package versions.

Customer and partner model selection are independent. Gemini partner profiles
and Gemini/Ollama customer options are documented in each starter's guide. Keep
credentials in private configuration rather than scenarios or shared evidence.

Integration and completion behavior

Customer creation, publication, launch, inspection and evidence export use the
native Java/Python SDKs. Banking preparation seeds only the partner-owned backend
and discovers the customer's scoped MCP grant; the downloaded Java client then
owns the Java customer workflow. A Java provider can also serve a separately
configured Python customer; provider and customer language are distinct choices.

Issued banking and marketing preserve their explicit
completionPolicy.requireCustomerFinish:true plus receipt conditions. Monthly
banking preserves its authored policy, native domain work and horizon; packaging
does not add a strict flag. Customer decisions and model responses remain
observable, including unsuccessful outcomes. Inspect actual advice and stop
reasons; configured achievement does not certify factual quality or payment
execution.

Marketing source offers separate advice and proposal-review cases. Proposal
review asks the customer to develop a handoff and obtain assessment of its
coverage and remaining gaps; it does not execute that handoff. Updated templates
require domain revision marketing-ops.native-events.v4 and its matching input
schema. The selected review separates completion from launch approval and
preserves known, unknown and unreported business facts. Use matching rebuilt
images when adopting these templates; source changes do not alter old archives.

Operation and limits

Public archives use digest-pinned images and include their compatibility
requirements. Local-verification archives instead require their recorded image
IDs already installed; keep them local rather than distributing them as public
downloads. Image architecture descriptors alone do not establish runtime
compatibility with a host.

These samples use a single host and private network. They do not perform real
payments or campaign launches, or establish production security, high
availability or population capacity. Marketing domain and agency conversation
state remain in memory; exported platform evidence is a separate durability
boundary. Preserve platform database/evidence volumes and keep credentials,
logs and customer evidence private.

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