Minimum runtime surface
A practical implementation begins with explicit ports rather than a provider SDK woven through business logic.
RuntimeContractRunStateMachineIContextAssemblerIModelAdapterIToolConnectorIPolicyEngineIApprovalGatewayICheckpointStoreIRuntimeStateStoreIEvidenceLedgerIRuntimeEvaluatorThe names are conceptual. The important property is that business use cases depend inward on stable contracts while provider, database, workflow, and model details remain adapters.
Guide map
Quickstart
Build one reversible dependency-update run.
02Run Lifecycle
Make transitions, actors, invariants, and concurrency explicit.
03Model Adapters
Normalize capabilities, streaming, usage, and failures.
04Tools and Policy
Validate action envelopes, credentials, decisions, and approvals.
05Memory and Lineage
Assemble attributable context and governed memory projections.
06Durable Execution
Resume long-running work and recover partial effects.
07Observability and Evidence
Correlate operations with reviewer-facing evidence.
08Testing
Combine deterministic, stochastic, adversarial, and fault tests.
09Teleodynamic Profile
Optional research fields for goals, viability, reflection, and edit proposals.
10Deployment
Version runtime controls atomically and operate failure runbooks.
Reference implementation posture
- Organize by capability and use case, not by provider.
- Use clean ports and adapters with explicit, versioned contracts.
- Keep deterministic lifecycle, policy, validation, and evidence boundaries.
- Use UTC timestamps, cancellation, deadlines, and normalized errors.
- Capture evidence before returning or retrying a material failure.
Non-goals
These guides do not prescribe one technology stack, workflow engine, model provider, complete open-source implementation, hosted runtime, package, certification, or production-ready MiRuntime SDK.
Source record
References
Microsoft. Microsoft Learn. Published Current documentation; last reviewed 2026-06-23 UTC. Official architecture guidance.
- Cloud Design Patterns Primary source
Microsoft. Azure Architecture Center. Published Current documentation; last reviewed 2026-06-23 UTC. Official architecture guidance.
National Institute of Standards and Technology. NIST. Published 2023-01-26; last reviewed 2026-06-20 UTC. Government framework.