Developer Guide

Engineering principles

• Keep models replaceable behind capability-aware adapters.
• Keep lifecycle, policy, approvals, tool execution, and evidence in typed software.
• Make side effects bounded, idempotent, checkpointed, and recoverable.
• Preserve context provenance and memory scope.
• Use UTC timestamps and explicit terminal states.

Implementation pathways

Build sequence

1. Define intent and success criteria.
2. Define authority and tool contracts.
3. Create durable lifecycle state.
4. Add model adapters.
5. Assemble scoped context.
6. Validate proposals.
7. Execute bounded side effects.
8. Capture evidence.
9. Recover or terminate.
10. Evaluate the completed workflow.

Role-based reading paths

Runtime contract

{
  "contractVersion": "1.0",
  "intent": {
    "objective": "Prepare a dependency update",
    "riskClass": "reversible-change",
    "successCriteria": ["tests-pass", "reviewable-diff"]
  },
  "context": {
    "sources": [],
    "memoryScopes": [],
    "prohibitedDataClasses": []
  },
  "authority": {
    "allowedTools": [],
    "writePolicy": "draft-only",
    "requiredApprovals": ["merge", "deploy"]
  },
  "execution": {
    "state": "running",
    "checkpointPolicy": "before-side-effect",
    "budgets": { "steps": 24, "elapsedSeconds": 900 }
  },
  "evidence": {
    "events": [],
    "artifacts": [],
    "unresolvedUncertainty": []
  }
}

Tool registry and policy

Tool contracts define schema, permissions, side effects, credentials, idempotency, timeout, rollback or compensation, approval, and evidence. Policy outcomes are allow, deny, require approval, transform, or escalate.

Testing stochastic workflows

Test deterministic boundaries exactly and probabilistic behavior through repeated trials, allowed outcome ranges, versioned fixtures, fault injection, policy assertions, and evidence completeness.

Reference downloads

These files are conceptual MiRuntime editorial references, not a product SDK or certification profile.