/api/remote-domain/v1/manifest
Declares protocol version, lifecycle operations, domain labels,
creator uiProfile, supported work kinds, control
actions, scorecards, and evidence capabilities.
remote-domain.v1 providers
Build the domain provider behind the evidence.
remote-domain.v1 is the contract between Astraform's
simulation host and your business world. Implement a provider, pass
conformance, then expose the state, workflow actions, and inspection
views that make launch decisions replayable.
Your domain keeps policy truth. Astraform turns the run into evidence.
Provider-owned state
Conformance gate
Replay inspection
Evidence projections
Provider readiness
remote-domain.v1 support gate
0.1.2
Protocol version
remote-domain.v1
Ready
Manifest
Capabilities
Required
Prepare / execute
Lifecycle
Required
Domain work windows
Provider-owned
Supported
Inspection projection
Report-ready
Required
Conformance harness
Python + Java
Required
Host registration
Self-hosted
Explicit
Provider artifact
remote-domain.v1
Evidence path
inspection + replay
Conformance gate
Python / Java
Boundary
domain-owned truth
Protocol console
A provider contract for replayable customer outcomes.
Every endpoint exists to preserve the chain from customer scenario to domain action, side effect, inspection, and report evidence.
/api/remote-domain/v1/prepare
Initializes opaque domain state from a persona, cohort, recipe, or scenario seed. The host stores references; the provider owns business semantics and validation.
/api/remote-domain/v1/execute-work
Runs bounded customer or workflow work and returns state deltas, emitted evidence, tool-facing outputs, warnings, and checkpoint references.
/api/remote-domain/v1/domain-system-work-window
Lets the provider execute institution-side time progression: interest, statement close, SLA expiry, fees, policy refresh, or other business-owned scheduled work.
/api/remote-domain/v1/inspection
Projects readable state and evidence for the dashboard, report, affected-subject drilldown, replay timeline, and export bundle.
SDK lanes
Install the kit. Prove the provider. Register the boundary.
Python and Java/Spring expose the same lifecycle contract. The SDKs help author providers, but conformance is the gate that makes a domain supportable.
Python
- Author kit
astraform-remote-domain-author-kit- Conformance
astraform-remote-domain-conformance- Registry
- Published on PyPI at version
0.1.2. - Install
pip install 'astraform-remote-domain-author-kit[fastapi]==0.1.2' astraform-remote-domain-conformance==0.1.2
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.2. - Install
-
ai.astraform:remote-domain-author-kit-java:0.1.2
ai.astraform:remote-domain-conformance-java:0.1.2
Support gate
- Install from the registry in clean external projects.
- Implement the
remote-domain.v1lifecycle contract. - Pass the conformance harness before host registration.
- Register with a self-hosted Astraform deployment.
- Emit evidence projections for report-relevant domain activity.
Boundary model
Astraform hosts the run. Your provider owns the truth.
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
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
Supportable means conformance plus replay evidence.
Build against the protocol
Use an author kit, but make the lifecycle contract the source of truth.
Pass conformance locally
Validate schema, lifecycle operations, and state projection before host wiring.
Register with the host
Verify manifest fetch, protocol compatibility, and runtime discovery.
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.