Astraform Remote-domain developer docs

Partner beta / remote-domain.v1 / public SDK baseline

Ship agent domains through a boundary enterprises can trust.

Astraform lets platform teams run replayable AI agent simulations while domain engineers build out-of-process services through the remote-domain.v1 contract. The host owns time, replay, policy, lifecycle, and operator visibility. Public Python and Java SDKs make authoring easier, but conformance decides whether a domain is supportable.

Open Quickstart SDK Release Contract
Release console remote-domain.v1 readiness
0.1.0
Protocol contract Versioned Ready
Python author kit PyPI 0.1.0 Published
Java author kit Maven Central 0.1.0 Published
External consumer smoke Python + Java Passing
Release trigger workflow_dispatch only Manual
Banking remote proof Dashboard + scheduled work Proven
Published Java coordinates ai.astraform
Published Python packages astraform-*
Release workflow Manual-only
Version rule Immutable

SDK lanes

One protocol, two authoring kits, one publishing ritual.

Python and Java/Spring must ship through the same release discipline: versioned artifacts, registry install, conformance helper, clean external consumer smoke tests, and immutable release discipline.

Python

Author kit
astraform-remote-domain-author-kit
Conformance
astraform-remote-domain-conformance
Registry
Published on PyPI at version 0.1.0.
Install
pip install 'astraform-remote-domain-author-kit[fastapi]==0.1.0' astraform-remote-domain-conformance==0.1.0

Java / Spring

Author kit
ai.astraform:remote-domain-author-kit-java
Conformance
ai.astraform:remote-domain-conformance-java
Registry
Published on Maven Central at version 0.1.0.
Install
ai.astraform:remote-domain-author-kit-java:0.1.0

Release gate

  1. Build wheel, sdist, jar, source jar, and javadoc jar.
  2. Run remote_domain_sdk_release.yml with one shared SDK version.
  3. Publish only a version that does not already exist.
  4. Install from the registry in clean external projects.
  5. Run conformance outside the monorepo.

Boundary model

The host is the runtime. The domain is not a shadow host.

This is the line that keeps the platform maintainable. If domains own clock, replay, policy, or canonical runtime state, the extension model has failed.

Host-owned controls

  • Clock and replay contract
  • Agent registration and lifecycle
  • Due-work dispatch
  • MCP and A2A policy
  • Telemetry and operator visibility
remote-domain.v1 HTTP / JSON lifecycle manifest -> prepare -> execute-work -> status -> inspection -> shutdown

Domain-owned semantics

  • Persona validation
  • Opaque state initialization
  • Domain work mutation
  • Status and inspection projections
  • Creator metadata through uiProfile

Certification runway

What has to be true before a partner domain is supportable.

01

Build against the protocol

Use an author kit, but make the lifecycle contract the source of truth.

02

Pass conformance locally

Validate schema, lifecycle operations, and state projection before host wiring.

03

Register with the host

Verify manifest fetch, protocol compatibility, and runtime discovery.

04

Prove runtime behavior

Show dashboard status, tool mounting, scheduled work, and inspection evidence.

Banking remote proof

The proof is real. The migration is not finished.

Banking can now run through the Java remote-domain path in the generic host: dashboard creation works, manifest tools mount, and scheduled transactions execute after a clock advance. That is meaningful evidence, not just architecture intent.

It is not permission to delete every banking-specific runtime surface. Scenario Lab, compatibility routes, operator APIs, and agent-runtime-banking cleanup still need explicit work.

Remote manifestFetched
Dashboard initHTTP 200
Scheduled workExecuted
Residue statusSplit

Current limits

Do not sell what the platform has not earned.

Enterprise buyers forgive honest beta boundaries. They do not forgive discovering those boundaries after procurement.

Immutable SDK versions

Publishing the same version twice should fail. Bump versions for release; use smoke-only for verification.

Synchronous v1 protocol

No async workflow ownership or remote runtime kernel in v1.

Self-hosted beta

Partners own deployment; this is not a managed SaaS promise.

Banking cleanup remains

The remote proof works, but legacy runtime, Scenario Lab, and operator compatibility cleanup remains explicit.