Astraform Bring your own business world

Bring your own business world / remote-domain.v1

Build domain simulations behind a boundary enterprises can trust.

Astraform's buyer-facing promise is customer outcome simulation. remote-domain.v1 is how domain engineers bring their own business state, actions, and evidence projections into that product without exposing platform internals or moving business source code into the host. Public Python and Java SDKs make authoring easier. Synthetic customer agents can then exercise the workflow through the boundary a partner chooses to expose, but conformance decides whether a domain is supportable.

Open Quickstart View SDK Install Paths
Domain readiness bring-your-own-domain readiness
0.1.0
Protocol contract Versioned Ready
Python author kit PyPI package Available
Java author kit Maven package Available
Conformance harness Python + Java Required
Preview deployment Self-hosted Partner-owned
Evidence boundary Host + domain Explicit
Published Java coordinates ai.astraform
Published Python packages astraform-*
Conformance support Python + Java
Preview deployment Self-hosted

SDK lanes

One protocol, two authoring kits, one conformance path.

Python and Java/Spring expose the same lifecycle contract: registry install, conformance helper, host registration, and evidence projection through remote-domain.v1.

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

Support gate

  1. Install from the registry in clean external projects.
  2. Implement the remote-domain.v1 lifecycle contract.
  3. Pass the conformance harness before host registration.
  4. Register with a self-hosted Astraform deployment.
  5. Emit evidence projections for report-relevant domain activity.

Boundary model

The host runs the simulation. The domain brings the business world.

This is the line that keeps customer outcome simulation credible. Astraform owns simulation time, replay, and run evidence. Your domain owns business semantics, persistence, policy truth, and side effects.

Host-owned controls

  • Clock and replay contract
  • Agent registration and lifecycle
  • Due-work dispatch
  • Tool and delegation policy
  • Canonical simulation snapshots
  • Replay evidence 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
  • Policy engines, APIs, tools, and side effects
  • Status, inspection, and evidence projections
  • Creator metadata through uiProfile

Certification runway

What has to be true before a business 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 lifecycle execution, domain evidence projections, and replay-linked outcome evidence.

Preview scope

Clear boundaries for early partners.

Partner Preview is intentionally narrow. The goal is one useful simulation pass with explicit assumptions, not a broad managed platform promise.

Self-hosted preview

Partners own deployment and connectivity for the first preview lane.

Synchronous v1 protocol

remote-domain.v1 supports the current lifecycle contract; long-running async domain ownership is outside v1.

Conformance required

A domain is supportable only after it passes the conformance harness and host registration checks.

Evidence under assumptions

Outcome reports are decision-grade stress-test evidence, not production forecasts or automatic launch approvals.