Astraform Samples v0.1.0

Astraform Samples v0.1.0

The first shared release of Astraform's public examples. All domains, languages
and frameworks use this repository version; choose the example you need without
installing the others.

Included

• A downloadable Python banking starter and SHA256 checksum: prebuilt bank,
  separate PostgreSQL database, LLM Banking Advice agent, Gemini/Ollama templates,
  customer scenario and SDK launch/inspect/export helper.
• Source examples for Java/Spring banking, Python/FastAPI banking, Marketing Ops,
  the LLM Creative Agency, Banking Advice and Refund Policy.
• Guides for connecting partner services to the released Astraform platform
  through HTTP, A2A and customer-scoped MCP tools.
• Apache 2.0 licensing for all Astraform-authored examples and documentation.

Java and marketing are source examples in this release. Prepared starter
archives for them are not included yet. GitHub's source archives contain only
this public samples repository, not the Astraform platform implementation.

Python banking starter

Avery has an already-issued January credit-card statement and AUD 100 available.
The customer must understand the amount, due date and whether that budget covers
the minimum payment or full balance. The customer reads its assigned account
through MCP; the banking partner reads the same backend through its own API and
answers over A2A. Both agents use configured language models.

Download astraform-banking-starter-v0.1.0.tar.gz and its matching .sha256
asset. Verify the checksum before extracting, then follow the included README.
The release also includes release-manifest.json with release and starter
provenance. The archive selects refreshed, digest-pinned Python SDK 0.3.2
banking and advice images; bundle-manifest.json records their actual build
revision, compatibility and payload hashes. Its embedded notes come from the
selected packaging revision, which can differ from the repository release commit.

Compatibility

Component	Version or requirement
Astraform Platform	v0.2.0, downloaded separately from the platform release
Python SDK	0.3.2, included in the Banking Advice image
Java SDK	0.4.2, used by the Java source examples
Public contracts	1.2.0
Starter host	Docker with Compose v2 and Python 3.10+ for initialization
Models	Gemini or Ollama, configured separately for the customer and partner

Platform, SDK and samples versions are independent. Provider credentials remain
in local private configuration and are not part of the archives.

Verification and limits

Source compatibility checks against the published Java 0.4.2 and Python 0.3.2
packages passed 621 banking, marketing and advice tests with no skipped tests.
Python banking used real PostgreSQL. Advice tests used owned HTTP/model fixtures;
these package checks did not execute a real customer-model simulation.

Earlier ARM64 reference trials used the released platform bundle and the previous
Python SDK 0.3.1 banking images. Gemini achieved the configured customer goal
with an MCP lookup and a real A2A partner exchange. The Ollama customer retrieved
its statement but abandoned the goal before contacting the partner; that run did
not exercise the partner model. Both outcomes and same-run evidence inspection
were preserved. Those trials do not establish the outcomes of the refreshed
images. Check the release's current verification record for the exact image
digests and actual model outcomes; AMD64/ARM64 availability alone is not runtime
verification on both architectures.

The packaged scenario uses fixed, already-issued records. It does not exercise
monthly statement generation, multiple customers or capacity limits. The banking
partner reads current records per request, has no persistent conversation history
and cannot make or schedule payments. Source examples include additional
scenarios; their presence does not extend this starter's verification.

Customer choices and goal failures are simulation evidence. Service health or a
successful export does not establish answer quality. Inspect the goal, messages
and actual tool activity in the result before evaluating the partner's behavior.

License

Examples, configuration and documentation use Apache License 2.0. The Astraform
platform is distributed separately under its own terms. Third-party components
retain their licenses.

Refreshed artifact verification

The refreshed images were built from public samples commit 8cfcb2cf3ddaf305124005acdc846ca1895713da. All eight image/architecture combinations across AMD64 and ARM64 were checked against the actual published SDK bytes: Java 0.4.2 for Java banking and Marketing Ops, and Python 0.3.2 for the public banking and advice pair. Source labels and later filesystem layers were also verified. The exact Python starter candidate has SHA256 70afe9cf66db3fe7485aef7b40b33d862345601a9b9804765fa286ef1d593f2d; its 13 manifest-listed payload hashes pass, and the archive contains 14 files including the manifest.

The release configuration was merged at a9aa4bad7678485675691a21ea21057a7a62fcfe. Its exact main checks and publication workflow passed. All three public release assets were downloaded anonymously; the archive and checksum are byte-identical to the candidate used for the prepublication trial, and the release manifest records that release commit and the pinned packaging source.

The runtime trial covered the Python banking starter on ARM64. One prepublication customer trial with genuine qwen3.5:4b/Ollama ended FAILED after about 18.5 minutes. Two recorded customer-provider responses each ended with finish reason length and reported 8,192 completion tokens, and the customer goal timed out; no successful customer decision or native customer MCP/A2A receipts were observed. One separate manual read-only partner request returned HTTP 200 in 10.227 seconds. Its 536-character genuine-model reply was preserved and validated against the actual response schema, bank context and issued statement. The partner response also included unsupported financial interpretation; schema/transport success does not establish correct advice. That check covers the tested endpoint/model path; answer quality and a successful native customer goal remain unverified. Runtime verification was performed on ARM64 only; the AMD64 checks cover image availability and SDK bytes.