{ "schemaVersion": "1.0", "name": "MiRuntime Content Catalog", "description": "Machine-readable route and editorial metadata for the managed MiRuntime.com publication.", "version": "2.8.5", "updatedUtc": "2026-06-27T00:00:00Z", "canonicalBase": "https://miruntime.com/", "status": "MiRuntime editorial framework", "itemCount": 55, "items": [ { "id": "home", "title": "Machine Intelligence Runtime", "path": "/", "url": "https://miruntime.com/", "summary": "MiRuntime.com defines Machine Intelligence Runtime: the execution-time control layer for agents, tools, memory, policy, recovery, telemetry, and evidence.", "purpose": "MiRuntime.com defines Machine Intelligence Runtime: the execution-time control layer for agents, tools, memory, policy, recovery, telemetry, and evidence.", "status": "MiRuntime perspective", "statusLabel": "MiRuntime perspective", "audience": "All audiences", "level": "Overview", "lastReviewed": "2026-06-27", "lastReviewedUtc": "2026-06-27T00:00:00Z", "topics": [ "Machine Intelligence Runtime", "AI runtime", "agent runtime" ], "mainConcepts": [ "Machine Intelligence Runtime", "AI runtime", "agent runtime" ], "sections": [], "references": [], "related": [] }, { "id": "machine-intelligence-runtime", "title": "What Is Machine Intelligence Runtime?", "path": "/machine-intelligence-runtime/", "url": "https://miruntime.com/machine-intelligence-runtime/", "summary": "A rigorous definition of Machine Intelligence Runtime with citation-safe boundaries, responsibilities, maturity limits, and differences from model servers, agent frameworks, workflow engines, and AI gateways.", "purpose": "A rigorous definition of Machine Intelligence Runtime with citation-safe boundaries, responsibilities, maturity limits, and differences from model servers, agent frameworks, workflow engines, and AI gateways.", "status": "Definition", "statusLabel": "Definition", "audience": "Platform architects, engineering leaders, product leaders", "level": "Foundational", "lastReviewed": "2026-06-27", "lastReviewedUtc": "2026-06-27T00:00:00Z", "topics": [ "definition", "architecture", "governance", "runtime boundaries", "runtime evidence" ], "mainConcepts": [ "definition", "architecture", "governance", "runtime boundaries", "runtime evidence" ], "sections": [ { "id": "definition", "label": "Definition" }, { "id": "comparison", "label": "What MIR is—and is not" }, { "id": "responsibilities", "label": "Observe, constrain, recover, prove" }, { "id": "decision", "label": "When MIR is justified" }, { "id": "citation-boundary", "label": "Citation and claim boundary" }, { "id": "maturity", "label": "Maturity model" } ], "references": [ "airi-2026", "onnx-runtime", "vllm-docs", "nist-airmf-2023" ], "related": [ { "id": "runtime-architecture", "path": "/runtime-architecture/" }, { "id": "agent-tool-execution", "path": "/agent-tool-execution/" }, { "id": "governance-and-trust", "path": "/governance-and-trust/" } ] }, { "id": "runtime-architecture", "title": "Runtime Architecture", "path": "/runtime-architecture/", "url": "https://miruntime.com/runtime-architecture/", "summary": "A seven-layer reference architecture for Machine Intelligence Runtime, including lifecycle, cross-cutting controls, deployment patterns, and failure recovery.", "purpose": "A seven-layer reference architecture for Machine Intelligence Runtime, including lifecycle, cross-cutting controls, deployment patterns, and failure recovery.", "status": "Reference architecture", "statusLabel": "Reference architecture", "audience": "Platform architects and senior developers", "level": "Technical", "lastReviewed": "2026-06-27", "lastReviewedUtc": "2026-06-27T00:00:00Z", "topics": [ "architecture", "control plane", "runtime plane", "structured data", "runtime evidence" ], "mainConcepts": [ "architecture", "control plane", "runtime plane", "structured data", "runtime evidence" ], "sections": [ { "id": "stack", "label": "Seven-layer architecture" }, { "id": "sequence", "label": "Execution sequence" }, { "id": "planes", "label": "Control and runtime planes" }, { "id": "deployment", "label": "Deployment patterns" }, { "id": "failure", "label": "Failure and recovery" }, { "id": "evidence-discovery", "label": "Evidence and discovery" }, { "id": "downloads", "label": "Downloadable architecture" } ], "references": [ "airi-2026", "mcp-spec-2025", "otel-genai", "nist-airmf-2023" ], "related": [ { "id": "architecture-deep-dive", "path": "/architecture-deep-dive/" }, { "id": "clean-architecture-for-mir", "path": "/clean-architecture-for-mir/" }, { "id": "deployment-tradeoffs", "path": "/deployment-tradeoffs/" }, { "id": "control-plane-runtime-plane", "path": "/control-plane-runtime-plane/" }, { "id": "developer-runtime-contract", "path": "/developers/runtime-contract/" }, { "id": "performance-hardware", "path": "/performance-hardware/" } ] }, { "id": "control-plane-runtime-plane", "title": "Control Plane and Runtime Plane", "path": "/control-plane-runtime-plane/", "url": "https://miruntime.com/control-plane-runtime-plane/", "summary": "How managed Machine Intelligence Runtime separates organizational control from isolated agent execution and tracks lifecycle state.", "purpose": "How managed Machine Intelligence Runtime separates organizational control from isolated agent execution and tracks lifecycle state.", "status": "Production pattern", "statusLabel": "Production pattern", "audience": "Platform architects and infrastructure teams", "level": "Technical", "lastReviewed": "2026-06-27", "lastReviewedUtc": "2026-06-27T00:00:00Z", "topics": [ "managed runtime", "lifecycle", "isolation" ], "mainConcepts": [ "managed runtime", "lifecycle", "isolation" ], "sections": [ { "id": "separation", "label": "Why separate the planes" }, { "id": "control", "label": "Control-plane responsibilities" }, { "id": "runtime", "label": "Runtime-plane responsibilities" }, { "id": "lifecycle", "label": "Lifecycle state machine" }, { "id": "operations", "label": "Operational boundaries" } ], "references": [ "aws-agentcore", "google-agent-platform", "airi-2026", "otel-genai" ], "related": [ { "id": "event-driven-runtime-orchestration", "path": "/event-driven-runtime-orchestration/" }, { "id": "deployment-tradeoffs", "path": "/deployment-tradeoffs/" }, { "id": "runtime-architecture", "path": "/runtime-architecture/" }, { "id": "governance-and-trust", "path": "/governance-and-trust/" }, { "id": "performance-hardware", "path": "/performance-hardware/" } ] }, { "id": "runtime-intelligence", "title": "Runtime Intelligence", "path": "/runtime-intelligence/", "url": "https://miruntime.com/runtime-intelligence/", "summary": "Test-time compute, search, verification, refinement, and closed-loop runtime intervention around model inference.", "purpose": "Test-time compute, search, verification, refinement, and closed-loop runtime intervention around model inference.", "status": "Research synthesis", "statusLabel": "Research synthesis", "audience": "Researchers, architects, and performance engineers", "level": "Advanced", "lastReviewed": "2026-06-27", "lastReviewedUtc": "2026-06-27T00:00:00Z", "topics": [ "test-time compute", "verification", "closed-loop control" ], "mainConcepts": [ "test-time compute", "verification", "closed-loop control" ], "sections": [ { "id": "shift", "label": "From parameter scaling to runtime allocation" }, { "id": "methods", "label": "Methods" }, { "id": "closed-loop", "label": "Closed-loop control" }, { "id": "tradeoffs", "label": "Tradeoffs" }, { "id": "boundary", "label": "Weights versus runtime" } ], "references": [ "test-time-compute-2024", "self-consistency-2022", "tree-of-thoughts-2023", "atlas-rtc-2026", "airi-2026" ], "related": [ { "id": "mir-design-patterns", "path": "/mir-design-patterns/" }, { "id": "event-driven-runtime-orchestration", "path": "/event-driven-runtime-orchestration/" }, { "id": "performance-hardware", "path": "/performance-hardware/" }, { "id": "future-of-ai-runtimes", "path": "/future-of-ai-runtimes/" }, { "id": "runtime-architecture", "path": "/runtime-architecture/" } ] }, { "id": "agent-tool-execution", "title": "Agents and Tool Execution", "path": "/agent-tool-execution/", "url": "https://miruntime.com/agent-tool-execution/", "summary": "Typed tools, permission classes, approval gates, retries, rollback, connector boundaries, and MCP placement in a governed runtime.", "purpose": "Typed tools, permission classes, approval gates, retries, rollback, connector boundaries, and MCP placement in a governed runtime.", "status": "Production pattern", "statusLabel": "Production pattern", "audience": "Agent developers, security engineers, platform teams", "level": "Technical", "lastReviewed": "2026-06-27", "lastReviewedUtc": "2026-06-27T00:00:00Z", "topics": [ "agents", "tools", "permissions", "MCP" ], "mainConcepts": [ "agents", "tools", "permissions", "MCP" ], "sections": [ { "id": "loop", "label": "The governed agent loop" }, { "id": "contracts", "label": "Typed tool contracts" }, { "id": "authority", "label": "Permission classes" }, { "id": "recovery", "label": "Failure and recovery" }, { "id": "connectors", "label": "Connector trust boundaries" } ], "references": [ "mcp-spec-2025", "owasp-agentic-threats", "owasp-prompt-injection-2025", "nist-airmf-2023" ], "related": [ { "id": "developer-tool-contracts", "path": "/developers/tool-contracts/" }, { "id": "governance-and-trust", "path": "/governance-and-trust/" }, { "id": "protocols-ecosystem", "path": "/protocols-ecosystem/" } ] }, { "id": "memory-and-evidence", "title": "Memory and Evidence", "path": "/memory-and-evidence/", "url": "https://miruntime.com/memory-and-evidence/", "summary": "A governed memory taxonomy, provenance and lifecycle controls, plus a user-facing evidence ledger for intelligent work.", "purpose": "A governed memory taxonomy, provenance and lifecycle controls, plus a user-facing evidence ledger for intelligent work.", "status": "Definition and production pattern", "statusLabel": "Definition and production pattern", "audience": "Developers, governance teams, researchers", "level": "Technical", "lastReviewed": "2026-06-27", "lastReviewedUtc": "2026-06-27T00:00:00Z", "topics": [ "memory", "evidence", "provenance", "audit" ], "mainConcepts": [ "memory", "evidence", "provenance", "audit" ], "sections": [ { "id": "distinction", "label": "Continuity versus accountability" }, { "id": "memory", "label": "Memory taxonomy and lifecycle" }, { "id": "evidence", "label": "Evidence schema" }, { "id": "timeline", "label": "Inspect a run" }, { "id": "limits", "label": "Replay and reproducibility limits" } ], "references": [ "airi-2026", "otel-genai", "nist-genai-profile-2024" ], "related": [ { "id": "developer-evidence-schema", "path": "/developers/evidence-schema/" }, { "id": "runtime-handoff", "path": "/runtime-handoff/" }, { "id": "governance-and-trust", "path": "/governance-and-trust/" } ] }, { "id": "local-first-control", "title": "Local-First Control", "path": "/local-first-control/", "url": "https://miruntime.com/local-first-control/", "summary": "Local-first versus local-only execution, hybrid model routing, data placement, offline continuity, approvals, and exportable evidence.", "purpose": "Local-first versus local-only execution, hybrid model routing, data placement, offline continuity, approvals, and exportable evidence.", "status": "MiRuntime perspective", "statusLabel": "MiRuntime perspective", "audience": "Architects, privacy teams, product leaders", "level": "Foundational", "lastReviewed": "2026-06-27", "lastReviewedUtc": "2026-06-27T00:00:00Z", "topics": [ "local-first", "hybrid AI", "privacy" ], "mainConcepts": [ "local-first", "hybrid AI", "privacy" ], "sections": [ { "id": "meaning", "label": "Local-first, not local-only" }, { "id": "placement", "label": "Placement decisions" }, { "id": "hybrid", "label": "Hybrid execution" }, { "id": "offline", "label": "Offline continuity" }, { "id": "control", "label": "User-governed control" } ], "references": [ "local-first-2019", "nist-genai-profile-2024", "onnx-runtime" ], "related": [ { "id": "runtime-architecture", "path": "/runtime-architecture/" }, { "id": "memory-and-evidence", "path": "/memory-and-evidence/" }, { "id": "governance-and-trust", "path": "/governance-and-trust/" } ] }, { "id": "governance-and-trust", "title": "Security and Governance", "path": "/governance-and-trust/", "url": "https://miruntime.com/governance-and-trust/", "summary": "Runtime threat modeling, prompt injection, least privilege, isolation, egress control, approval gates, evidence, and ownership.", "purpose": "Runtime threat modeling, prompt injection, least privilege, isolation, egress control, approval gates, evidence, and ownership.", "status": "Production guidance", "statusLabel": "Production guidance", "audience": "Security, governance, compliance, and platform teams", "level": "Advanced", "lastReviewed": "2026-06-27", "lastReviewedUtc": "2026-06-27T00:00:00Z", "topics": [ "security", "governance", "prompt injection", "least privilege" ], "mainConcepts": [ "security", "governance", "prompt injection", "least privilege" ], "sections": [ { "id": "model", "label": "Runtime threat model" }, { "id": "mapping", "label": "Threat-to-control mapping" }, { "id": "identity", "label": "Identity and least privilege" }, { "id": "oversight", "label": "Human oversight and incident response" }, { "id": "ownership", "label": "Governance ownership" } ], "references": [ "owasp-prompt-injection-2025", "owasp-agentic-threats", "nist-airmf-2023", "nist-genai-profile-2024", "mcp-spec-2025" ], "related": [ { "id": "mlops-lineage-and-agent-drift", "path": "/mlops-lineage-and-agent-drift/" }, { "id": "clean-architecture-for-mir", "path": "/clean-architecture-for-mir/" }, { "id": "agent-tool-execution", "path": "/agent-tool-execution/" }, { "id": "memory-and-evidence", "path": "/memory-and-evidence/" }, { "id": "developer-implementation-checklist", "path": "/developers/implementation-checklist/" } ] }, { "id": "performance-hardware", "title": "Performance and Hardware", "path": "/performance-hardware/", "url": "https://miruntime.com/performance-hardware/", "summary": "Task-level metrics, latency budgets, batching, KV-cache management, runtime overhead, accelerators, edge deployment, cost, and energy.", "purpose": "Task-level metrics, latency budgets, batching, KV-cache management, runtime overhead, accelerators, edge deployment, cost, and energy.", "status": "Production guidance and research", "statusLabel": "Production guidance and research", "audience": "Performance engineers, architects, infrastructure teams", "level": "Advanced", "lastReviewed": "2026-06-27", "lastReviewedUtc": "2026-06-27T00:00:00Z", "topics": [ "performance", "latency", "batching", "hardware" ], "mainConcepts": [ "performance", "latency", "batching", "hardware" ], "sections": [ { "id": "metrics", "label": "Task-level metrics" }, { "id": "budget", "label": "Latency budget" }, { "id": "scheduling", "label": "Scheduling and context" }, { "id": "hardware", "label": "Heterogeneous hardware" }, { "id": "method", "label": "Benchmark methodology" } ], "references": [ "triton-dynamic-batching", "vllm-docs", "onnx-runtime", "test-time-compute-2024" ], "related": [ { "id": "inference-infrastructure", "path": "/inference-infrastructure/" }, { "id": "deployment-tradeoffs", "path": "/deployment-tradeoffs/" }, { "id": "runtime-intelligence", "path": "/runtime-intelligence/" }, { "id": "runtime-architecture", "path": "/runtime-architecture/" }, { "id": "research-landscape", "path": "/research/landscape/" } ] }, { "id": "protocols-ecosystem", "title": "Protocols and Ecosystem", "path": "/protocols-ecosystem/", "url": "https://miruntime.com/protocols-ecosystem/", "summary": "How MCP, A2A, AI gateways, model servers, workflow engines, identity, observability, memory stores, and sandboxes relate to MIR.", "purpose": "How MCP, A2A, AI gateways, model servers, workflow engines, identity, observability, memory stores, and sandboxes relate to MIR.", "status": "Landscape", "statusLabel": "Landscape", "audience": "Architects, integration engineers, researchers", "level": "Technical", "lastReviewed": "2026-06-27", "lastReviewedUtc": "2026-06-27T00:00:00Z", "topics": [ "MCP", "A2A", "AI gateway", "observability" ], "mainConcepts": [ "MCP", "A2A", "AI gateway", "observability" ], "sections": [ { "id": "map", "label": "Neutral architecture map" }, { "id": "mcp", "label": "MCP placement" }, { "id": "a2a", "label": "Agent interoperability" }, { "id": "adjacent", "label": "Adjacent systems" }, { "id": "selection", "label": "Selection questions" } ], "references": [ "mcp-spec-2025", "a2a-spec", "otel-genai", "onnx-runtime", "vllm-docs" ], "related": [ { "id": "runtime-architecture", "path": "/runtime-architecture/" }, { "id": "research-landscape", "path": "/research/landscape/" }, { "id": "agent-tool-execution", "path": "/agent-tool-execution/" } ] }, { "id": "developers", "title": "Developer Guide", "path": "/developers/", "url": "https://miruntime.com/developers/", "summary": "Conceptual contracts, implementation boundaries, observability conventions, testing strategy, evidence requirements, and developer resources for MIR.", "purpose": "Provide conceptual contracts, reference schemas, implementation pathways, and role-based reading paths for MIR engineers.", "status": "Reference guide", "statusLabel": "Reference guide", "audience": "Developers and platform engineers", "level": "Technical", "lastReviewed": "2026-06-24", "lastReviewedUtc": "2026-06-24T00:00:00Z", "topics": [ "developer guide", "contracts", "testing" ], "mainConcepts": [ "implementation pathways", "build sequence", "role-based reading path", "conceptual contracts", "no-SDK boundary" ], "sections": [ { "id": "boundary", "label": "Conceptual contract boundary" }, { "id": "principles", "label": "Engineering principles" }, { "id": "pathways", "label": "Implementation pathways" }, { "id": "sequence", "label": "Build sequence" }, { "id": "roles", "label": "Role-based reading paths" }, { "id": "contract", "label": "Runtime contract" }, { "id": "tools", "label": "Tools and policy" }, { "id": "testing", "label": "Testing stochastic workflows" }, { "id": "downloads", "label": "Reference downloads" } ], "references": [ "mcp-spec-2025", "otel-genai", "nist-airmf-2023", "owasp-agentic-threats" ], "related": [ { "id": "clean-architecture-for-mir", "path": "/clean-architecture-for-mir/" }, { "id": "mir-design-patterns", "path": "/mir-design-patterns/" }, { "id": "developer-runtime-contract", "path": "/developers/runtime-contract/" }, { "id": "developer-tool-contracts", "path": "/developers/tool-contracts/" }, { "id": "developer-evidence-schema", "path": "/developers/evidence-schema/" }, { "id": "developer-implementation-checklist", "path": "/developers/implementation-checklist/" }, { "id": "developer-implementation-guides", "path": "/developers/implementation-guides/" }, { "id": "developer-quickstart", "path": "/developers/quickstart/" }, { "id": "developer-teleodynamic-runtime-profile", "path": "/developers/teleodynamic-runtime-profile/" } ] }, { "id": "developer-runtime-contract", "title": "Runtime Contract", "path": "/developers/runtime-contract/", "url": "https://miruntime.com/developers/runtime-contract/", "summary": "A conceptual, versioned contract for intent, context, authority, execution state, budgets, recovery, and evidence.", "purpose": "A conceptual, versioned contract for intent, context, authority, execution state, budgets, recovery, and evidence.", "status": "Reference contract", "statusLabel": "Reference contract", "audience": "Developers and platform engineers", "level": "Technical", "lastReviewed": "2026-06-27", "lastReviewedUtc": "2026-06-27T00:00:00Z", "topics": [ "runtime contract", "schema", "state machine" ], "mainConcepts": [ "runtime contract", "schema", "state machine" ], "sections": [ { "id": "shape", "label": "Contract shape" }, { "id": "state", "label": "Lifecycle and transitions" }, { "id": "validation", "label": "Validation rules" }, { "id": "versioning", "label": "Versioning and portability" }, { "id": "download", "label": "Download schema" } ], "references": [ "airi-2026", "nist-airmf-2023", "otel-genai" ], "related": [ { "id": "clean-architecture-for-mir", "path": "/clean-architecture-for-mir/" }, { "id": "event-driven-runtime-orchestration", "path": "/event-driven-runtime-orchestration/" }, { "id": "developers", "path": "/developers/" }, { "id": "developer-tool-contracts", "path": "/developers/tool-contracts/" }, { "id": "developer-evidence-schema", "path": "/developers/evidence-schema/" } ] }, { "id": "developer-tool-contracts", "title": "Tool Contracts", "path": "/developers/tool-contracts/", "url": "https://miruntime.com/developers/tool-contracts/", "summary": "A typed tool contract for schemas, permissions, side effects, credentials, idempotency, rollback, and evidence.", "purpose": "A typed tool contract for schemas, permissions, side effects, credentials, idempotency, rollback, and evidence.", "status": "Reference contract", "statusLabel": "Reference contract", "audience": "Developers, security engineers, connector owners", "level": "Technical", "lastReviewed": "2026-06-27", "lastReviewedUtc": "2026-06-27T00:00:00Z", "topics": [ "tool contract", "permissions", "MCP" ], "mainConcepts": [ "tool contract", "permissions", "MCP" ], "sections": [ { "id": "shape", "label": "Annotated contract" }, { "id": "permissions", "label": "Permission and risk" }, { "id": "execution", "label": "Execution rules" }, { "id": "mcp", "label": "MCP integration" }, { "id": "download", "label": "Download schema" } ], "references": [ "mcp-spec-2025", "owasp-agentic-threats", "owasp-prompt-injection-2025" ], "related": [ { "id": "agent-tool-execution", "path": "/agent-tool-execution/" }, { "id": "developer-runtime-contract", "path": "/developers/runtime-contract/" }, { "id": "developer-evidence-schema", "path": "/developers/evidence-schema/" } ] }, { "id": "developer-evidence-schema", "title": "Evidence Schema", "path": "/developers/evidence-schema/", "url": "https://miruntime.com/developers/evidence-schema/", "summary": "A conceptual event schema for requests, context, policy, approvals, tools, artifacts, failures, recovery, and uncertainty.", "purpose": "A conceptual event schema for requests, context, policy, approvals, tools, artifacts, failures, recovery, and uncertainty.", "status": "Reference contract", "statusLabel": "Reference contract", "audience": "Developers, auditors, governance teams", "level": "Technical", "lastReviewed": "2026-06-27", "lastReviewedUtc": "2026-06-27T00:00:00Z", "topics": [ "evidence schema", "audit", "telemetry" ], "mainConcepts": [ "evidence schema", "audit", "telemetry" ], "sections": [ { "id": "principles", "label": "Schema principles" }, { "id": "event", "label": "Event shape" }, { "id": "events", "label": "Required event types" }, { "id": "privacy", "label": "Privacy and retention" }, { "id": "download", "label": "Download schema" } ], "references": [ "otel-genai", "nist-genai-profile-2024" ], "related": [ { "id": "event-driven-runtime-orchestration", "path": "/event-driven-runtime-orchestration/" }, { "id": "mlops-lineage-and-agent-drift", "path": "/mlops-lineage-and-agent-drift/" }, { "id": "memory-and-evidence", "path": "/memory-and-evidence/" }, { "id": "developer-runtime-contract", "path": "/developers/runtime-contract/" }, { "id": "runtime-handoff", "path": "/runtime-handoff/" } ] }, { "id": "developer-implementation-checklist", "title": "Implementation Checklist", "path": "/developers/implementation-checklist/", "url": "https://miruntime.com/developers/implementation-checklist/", "summary": "A launch checklist for architecture, authority, tools, memory, recovery, evidence, testing, privacy, and operations.", "purpose": "A launch checklist for architecture, authority, tools, memory, recovery, evidence, testing, privacy, and operations.", "status": "Implementation checklist", "statusLabel": "Implementation checklist", "audience": "Engineering, security, governance, operations", "level": "Technical", "lastReviewed": "2026-06-24", "lastReviewedUtc": "2026-06-24T00:00:00Z", "topics": [ "implementation", "checklist", "release" ], "mainConcepts": [ "runtime controls", "research-aware controls", "developer implementation controls", "operator stop", "schema versioning" ], "sections": [ { "id": "scope", "label": "Scope and architecture" }, { "id": "authority", "label": "Identity and authority" }, { "id": "execution", "label": "Execution and recovery" }, { "id": "evidence", "label": "Evidence and operations" }, { "id": "release", "label": "Release gates" }, { "id": "research-aware-controls", "label": "Research-aware controls" }, { "id": "developer-controls", "label": "Developer implementation controls" } ], "references": [ "nist-airmf-2023", "owasp-agentic-threats", "mcp-spec-2025", "otel-genai" ], "related": [ { "id": "developers", "path": "/developers/" }, { "id": "governance-and-trust", "path": "/governance-and-trust/" }, { "id": "performance-hardware", "path": "/performance-hardware/" } ] }, { "id": "use-cases", "title": "Use Cases", "path": "/use-cases/", "url": "https://miruntime.com/use-cases/", "summary": "A filterable use-case guide covering objectives, runtime state, risk, approvals, evidence, recovery, and when MIR is unnecessary.", "purpose": "A filterable use-case guide covering objectives, runtime state, risk, approvals, evidence, recovery, and when MIR is unnecessary.", "status": "Decision guide", "statusLabel": "Decision guide", "audience": "Architects, product leaders, developers", "level": "Foundational", "lastReviewed": "2026-06-27", "lastReviewedUtc": "2026-06-27T00:00:00Z", "topics": [ "use cases", "risk", "approval" ], "mainConcepts": [ "use cases", "risk", "approval" ], "sections": [ { "id": "guide", "label": "How to use the explorer" }, { "id": "explorer", "label": "Use-case explorer" }, { "id": "simpler", "label": "When to use a simpler system" } ], "references": [ "nist-airmf-2023", "owasp-agentic-threats" ], "related": [ { "id": "machine-intelligence-runtime", "path": "/machine-intelligence-runtime/" }, { "id": "runtime-architecture", "path": "/runtime-architecture/" }, { "id": "developers", "path": "/developers/" } ] }, { "id": "research", "title": "Research", "path": "/research/", "url": "https://miruntime.com/research/", "summary": "A searchable research and primary-source index for runtime intelligence, managed execution, protocols, security, observability, and inference.", "purpose": "Provide a source-aware research index, program map, status vocabulary, open-gap register, and public data export.", "status": "Research index", "statusLabel": "Research index", "audience": "Researchers, technical readers, architects", "level": "Advanced", "lastReviewed": "2026-06-24", "lastReviewedUtc": "2026-06-24T00:00:00Z", "topics": [ "research", "papers", "sources", "claim register", "source evidence" ], "mainConcepts": [ "research programs", "source index", "editorial status", "open research gaps", "public research data" ], "sections": [ { "id": "method", "label": "Editorial method" }, { "id": "programs", "label": "Research programs" }, { "id": "status-legend", "label": "Status legend" }, { "id": "index", "label": "Research index" }, { "id": "gaps", "label": "Open research gaps" }, { "id": "data", "label": "Research data export" } ], "references": [ "airi-2026", "test-time-compute-2024", "mcp-spec-2025", "nist-airmf-2023" ], "related": [ { "id": "research-reports", "path": "/research/reports/" }, { "id": "research-landscape", "path": "/research/landscape/" }, { "id": "future-of-ai-runtimes", "path": "/future-of-ai-runtimes/" }, { "id": "teleodynamic-runtimes", "path": "/research/teleodynamic-runtimes/" }, { "id": "runtime-benchmarks-and-evaluation", "path": "/research/runtime-benchmarks-and-evaluation/" }, { "id": "reproducibility-evidence-and-open-questions", "path": "/research/reproducibility-evidence-and-open-questions/" } ] }, { "id": "research-reports", "title": "Reports", "path": "/research/reports/", "url": "https://miruntime.com/research/reports/", "summary": "Long-form MiRuntime reports with review dates, source status, footnotes, and explicit boundaries between evidence and synthesis.", "purpose": "Long-form MiRuntime reports with review dates, source status, footnotes, and explicit boundaries between evidence and synthesis.", "status": "Editorial collection", "statusLabel": "Editorial collection", "audience": "Researchers and technical readers", "level": "Advanced", "lastReviewed": "2026-06-24", "lastReviewedUtc": "2026-06-24T00:00:00Z", "topics": [ "reports", "editorial method", "citations" ], "mainConcepts": [ "reports", "editorial method", "citations" ], "sections": [ { "id": "collection", "label": "Report collection" }, { "id": "method", "label": "Publication method" }, { "id": "citation", "label": "Citation policy" }, { "id": "teleodynamic-report", "label": "Teleodynamic runtime synthesis" } ], "references": [ "airi-2026", "test-time-compute-2024", "nist-airmf-2023" ], "related": [ { "id": "report-machine-intelligence-runtime", "path": "/research/reports/machine-intelligence-runtime/" }, { "id": "report-future-architectures", "path": "/research/reports/machine-intelligence-runtime-architectures-future-ai/" }, { "id": "research", "path": "/research/" }, { "id": "report-teleodynamic-machine-intelligence-runtime", "path": "/research/reports/teleodynamic-machine-intelligence-runtime/" }, { "id": "teleodynamic-runtimes", "path": "/research/teleodynamic-runtimes/" } ] }, { "id": "research-landscape", "title": "Industry Landscape", "path": "/research/landscape/", "url": "https://miruntime.com/research/landscape/", "summary": "A neutral matrix of inference runtimes, agent frameworks, managed agent platforms, gateways, workflow systems, protocols, observability, and isolation.", "purpose": "A neutral matrix of inference runtimes, agent frameworks, managed agent platforms, gateways, workflow systems, protocols, observability, and isolation.", "status": "Neutral landscape", "statusLabel": "Neutral landscape", "audience": "Architects and strategy leaders", "level": "Technical", "lastReviewed": "2026-06-27", "lastReviewedUtc": "2026-06-27T00:00:00Z", "topics": [ "industry landscape", "vendors", "open source" ], "mainConcepts": [ "industry landscape", "vendors", "open source" ], "sections": [ { "id": "matrix", "label": "Landscape matrix" }, { "id": "status", "label": "How status is labeled" }, { "id": "questions", "label": "Evaluation questions" } ], "references": [ "aws-agentcore", "google-agent-platform", "onnx-runtime", "vllm-docs", "mcp-spec-2025", "a2a-spec", "otel-genai" ], "related": [ { "id": "protocols-ecosystem", "path": "/protocols-ecosystem/" }, { "id": "performance-hardware", "path": "/performance-hardware/" }, { "id": "research", "path": "/research/" } ] }, { "id": "report-machine-intelligence-runtime", "title": "Report: Machine Intelligence Runtime", "path": "/research/reports/machine-intelligence-runtime/", "url": "https://miruntime.com/research/reports/machine-intelligence-runtime/", "summary": "A structured editorial report defining MIR, its architecture, operational responsibilities, governance, performance, and open research questions.", "purpose": "A structured editorial report defining MIR, its architecture, operational responsibilities, governance, performance, and open research questions.", "status": "Editorial synthesis", "statusLabel": "Editorial synthesis", "audience": "Researchers, architects, technical leaders", "level": "Advanced", "lastReviewed": "2026-06-27", "lastReviewedUtc": "2026-06-27T00:00:00Z", "topics": [ "report", "MIR", "research synthesis" ], "mainConcepts": [ "report", "MIR", "research synthesis" ], "sections": [ { "id": "abstract", "label": "Abstract" }, { "id": "architecture", "label": "Architecture" }, { "id": "operations", "label": "Operational responsibilities" }, { "id": "security", "label": "Security and governance" }, { "id": "research", "label": "Research gaps" }, { "id": "method", "label": "Source note" } ], "references": [ "airi-2026", "test-time-compute-2024", "mcp-spec-2025", "nist-airmf-2023", "owasp-agentic-threats", "otel-genai" ], "related": [ { "id": "machine-intelligence-runtime", "path": "/machine-intelligence-runtime/" }, { "id": "runtime-architecture", "path": "/runtime-architecture/" }, { "id": "report-future-architectures", "path": "/research/reports/machine-intelligence-runtime-architectures-future-ai/" } ] }, { "id": "report-future-architectures", "title": "Report: MIR Architectures and the Future of AI", "path": "/research/reports/machine-intelligence-runtime-architectures-future-ai/", "url": "https://miruntime.com/research/reports/machine-intelligence-runtime-architectures-future-ai/", "summary": "A reviewed synthesis of runtime intelligence, managed execution, protocols, security, performance, and future MIR scenarios.", "purpose": "A reviewed synthesis of runtime intelligence, managed execution, protocols, security, performance, and future MIR scenarios.", "status": "Editorial synthesis", "statusLabel": "Editorial synthesis", "audience": "Researchers, architects, strategy leaders", "level": "Advanced", "lastReviewed": "2026-06-27", "lastReviewedUtc": "2026-06-27T00:00:00Z", "topics": [ "future report", "runtime intelligence", "managed runtime" ], "mainConcepts": [ "future report", "runtime intelligence", "managed runtime" ], "sections": [ { "id": "abstract", "label": "Abstract" }, { "id": "intelligence", "label": "Runtime intelligence" }, { "id": "managed", "label": "Managed execution" }, { "id": "ecosystem", "label": "Protocols and ecosystem" }, { "id": "future", "label": "Future scenarios" }, { "id": "omissions", "label": "Verification and omissions" } ], "references": [ "airi-2026", "test-time-compute-2024", "vigil-2025", "atlas-rtc-2026", "mcp-spec-2025", "a2a-spec", "aws-agentcore", "google-agent-platform", "owasp-agentic-threats" ], "related": [ { "id": "future-of-ai-runtimes", "path": "/future-of-ai-runtimes/" }, { "id": "runtime-intelligence", "path": "/runtime-intelligence/" }, { "id": "research-landscape", "path": "/research/landscape/" } ] }, { "id": "future-of-ai-runtimes", "title": "The Future of AI Runtimes", "path": "/future-of-ai-runtimes/", "url": "https://miruntime.com/future-of-ai-runtimes/", "summary": "A restrained timeline separating current capabilities, near-term developments, open research, and long-range MIR scenarios.", "purpose": "A restrained timeline separating current capabilities, near-term developments, open research, and long-range MIR scenarios.", "status": "Forecast and MiRuntime perspective", "statusLabel": "Forecast and MiRuntime perspective", "audience": "Architects, researchers, strategy leaders", "level": "Advanced", "lastReviewed": "2026-06-27", "lastReviewedUtc": "2026-06-27T00:00:00Z", "topics": [ "future", "forecast", "AI runtimes" ], "mainConcepts": [ "future", "forecast", "AI runtimes" ], "sections": [ { "id": "thesis", "label": "Future thesis" }, { "id": "current", "label": "Current capabilities" }, { "id": "near", "label": "Near-term developments" }, { "id": "research", "label": "Open research" }, { "id": "long", "label": "Long-range scenarios" }, { "id": "assumptions", "label": "Assumptions and uncertainty" } ], "references": [ "airi-2026", "test-time-compute-2024", "mcp-spec-2025", "a2a-spec", "vigil-2025", "atlas-rtc-2026" ], "related": [ { "id": "runtime-intelligence", "path": "/runtime-intelligence/" }, { "id": "protocols-ecosystem", "path": "/protocols-ecosystem/" }, { "id": "research", "path": "/research/" } ] }, { "id": "glossary", "title": "Glossary", "path": "/glossary/", "url": "https://miruntime.com/glossary/", "summary": "Searchable definitions for Machine Intelligence Runtime architecture, security, memory, tools, recovery, evidence, and performance.", "purpose": "Searchable definitions for Machine Intelligence Runtime architecture, security, memory, tools, recovery, evidence, and performance.", "status": "Definition", "statusLabel": "Definition", "audience": "All audiences", "level": "Reference", "lastReviewed": "2026-06-27", "lastReviewedUtc": "2026-06-27T00:00:00Z", "topics": [ "glossary", "definitions" ], "mainConcepts": [ "glossary", "definitions" ], "sections": [ { "id": "terms", "label": "Terms" }, { "id": "download", "label": "Glossary data" } ], "references": [], "related": [ { "id": "machine-intelligence-runtime", "path": "/machine-intelligence-runtime/" }, { "id": "developers", "path": "/developers/" }, { "id": "research", "path": "/research/" } ] }, { "id": "runtime-handoff", "title": "AI Runtime Handoff", "path": "/runtime-handoff/", "url": "https://miruntime.com/runtime-handoff/", "summary": "Structured project memory, active file intake, review gates, dispositions, and durable evidence for handoff between human and AI sessions.", "purpose": "Structured project memory, active file intake, review gates, dispositions, and durable evidence for handoff between human and AI sessions.", "status": "Production workflow", "statusLabel": "Production workflow", "audience": "Developers, project owners, AI operators", "level": "Technical", "lastReviewed": "2026-06-27", "lastReviewedUtc": "2026-06-27T00:00:00Z", "topics": [ "handoff", "project memory", "file intake" ], "mainConcepts": [ "handoff", "project memory", "file intake" ], "sections": [ { "id": "purpose", "label": "Why handoff belongs in MIR" }, { "id": "intake", "label": "Active file intake" }, { "id": "package", "label": "Project memory package" }, { "id": "proof", "label": "Proof of use" } ], "references": [], "related": [ { "id": "memory-and-evidence", "path": "/memory-and-evidence/" }, { "id": "developer-evidence-schema", "path": "/developers/evidence-schema/" }, { "id": "developers", "path": "/developers/" } ] }, { "id": "about", "title": "About MiRuntime and Michael Kappel", "path": "/about/", "url": "https://miruntime.com/about/", "summary": "MiRuntime.com’s mission, Michael Kappel’s public operator profile, editorial methodology, correction workflow, source policy, and publication boundaries.", "purpose": "MiRuntime.com’s mission, Michael Kappel’s public operator profile, editorial methodology, correction workflow, source policy, and publication boundaries.", "status": "Editorial method and publication identity", "statusLabel": "Editorial method and publication identity", "audience": "Architects, developers, researchers, reviewers, and collaborators", "level": "Overview", "lastReviewed": "2026-06-27", "lastReviewedUtc": "2026-06-27T00:00:00Z", "topics": [ "about", "Michael Kappel", "methodology", "mission", "corrections" ], "mainConcepts": [ "about", "Michael Kappel", "methodology", "mission", "corrections" ], "sections": [ { "id": "mission", "label": "Mission" }, { "id": "maintainer", "label": "Maintainer" }, { "id": "experience", "label": "Experience" }, { "id": "method", "label": "Editorial method" }, { "id": "corrections", "label": "Corrections" }, { "id": "boundaries", "label": "Boundaries" } ], "references": [ "michael-kappel-portfolio", "michael-kappel-github", "airi-2026", "nist-airmf-2023" ], "related": [ { "id": "research", "path": "/research/" }, { "id": "contact", "path": "/contact/" }, { "id": "accessibility", "path": "/accessibility/" } ] }, { "id": "contact", "title": "Contact Michael Kappel", "path": "/contact/", "url": "https://miruntime.com/contact/", "summary": "Contact Michael Kappel about Machine Intelligence Runtime, software architecture, research, governance, developer implementation, or collaboration.", "purpose": "Contact Michael Kappel about Machine Intelligence Runtime, software architecture, research, governance, developer implementation, or collaboration.", "status": "Contact and operator profile", "statusLabel": "Contact and operator profile", "audience": "Architects, researchers, engineering leaders, developers, collaborators", "level": "Overview", "lastReviewed": "2026-06-27", "lastReviewedUtc": "2026-06-27T00:00:00Z", "topics": [ "contact", "Michael Kappel", "software architecture", "collaboration" ], "mainConcepts": [ "contact", "Michael Kappel", "software architecture", "collaboration" ], "sections": [ { "id": "direct-contact", "label": "Direct contact" }, { "id": "experience", "label": "Experience" }, { "id": "topics", "label": "Discussion topics" }, { "id": "form", "label": "Contact form" }, { "id": "handling", "label": "Data handling" } ], "references": [], "related": [ { "id": "about", "path": "/about/" }, { "id": "privacy", "path": "/privacy/" }, { "id": "research", "path": "/research/" } ] }, { "id": "privacy", "title": "Privacy", "path": "/privacy/", "url": "https://miruntime.com/privacy/", "summary": "Privacy information covering guaranteed theme behavior and operator-recorded hosting, mail, analytics, cookies, logs, retention, backups, and request procedures.", "purpose": "Privacy information covering guaranteed theme behavior and operator-recorded hosting, mail, analytics, cookies, logs, retention, backups, and request procedures.", "status": "Deployment-aware privacy policy", "statusLabel": "Deployment-aware privacy policy", "audience": "All visitors", "level": "Legal and operational", "lastReviewed": "2026-06-27", "lastReviewedUtc": "2026-06-27T00:00:00Z", "topics": [ "privacy", "data handling" ], "mainConcepts": [ "privacy", "data handling" ], "sections": [ { "id": "summary", "label": "Summary" }, { "id": "data", "label": "Data handled" }, { "id": "contact", "label": "Contact submissions" }, { "id": "storage", "label": "Local storage and cookies" }, { "id": "deployment", "label": "Deployment facts" }, { "id": "retention", "label": "Retention and deletion" }, { "id": "rights", "label": "Requests and changes" } ], "references": [], "related": [ { "id": "contact", "path": "/contact/" }, { "id": "accessibility", "path": "/accessibility/" }, { "id": "about", "path": "/about/" } ] }, { "id": "accessibility", "title": "Accessibility", "path": "/accessibility/", "url": "https://miruntime.com/accessibility/", "summary": "Accessibility statement for the MiRuntime theme, including keyboard access, reduced motion, themes, diagrams, testing, and known deployment responsibilities.", "purpose": "Accessibility statement for the MiRuntime theme, including keyboard access, reduced motion, themes, diagrams, testing, and known deployment responsibilities.", "status": "Accessibility statement", "statusLabel": "Accessibility statement", "audience": "All visitors", "level": "Reference", "lastReviewed": "2026-06-27", "lastReviewedUtc": "2026-06-27T00:00:00Z", "topics": [ "accessibility", "WCAG" ], "mainConcepts": [ "accessibility", "WCAG" ], "sections": [ { "id": "commitment", "label": "Commitment" }, { "id": "features", "label": "Implemented features" }, { "id": "testing", "label": "Testing" }, { "id": "limitations", "label": "Known responsibilities" }, { "id": "feedback", "label": "Feedback" } ], "references": [], "related": [ { "id": "contact", "path": "/contact/" }, { "id": "privacy", "path": "/privacy/" }, { "id": "about", "path": "/about/" } ] }, { "id": "architecture-deep-dive", "title": "Architecture Deep Dive", "path": "/architecture-deep-dive/", "url": "https://miruntime.com/architecture-deep-dive/", "summary": "Implementation-oriented architecture guidance for building Machine Intelligence Runtimes with deterministic boundaries, typed authority, recovery, evidence, and production infrastructure.", "purpose": "Connect the seven-layer MIR reference architecture to concrete enterprise architecture practices and deployment decisions.", "status": "Editorial guidance", "statusLabel": "Editorial guidance", "audience": "Platform architects, senior developers, infrastructure teams, AI engineers, enterprise software architects", "level": "Advanced", "lastReviewed": "2026-06-23", "lastReviewedUtc": "2026-06-23T00:00:00Z", "topics": [ "architecture deep dive", "clean architecture", "design patterns", "event-driven runtime", "inference infrastructure", "MLOps", "deployment" ], "mainConcepts": [ "deterministic boundaries", "typed authority", "recoverable execution", "reviewable evidence", "ports and adapters", "runtime orchestration" ], "sections": [ { "id": "why", "label": "Why this section exists" }, { "id": "map", "label": "Architecture map" }, { "id": "principle", "label": "Core principle" }, { "id": "use", "label": "How to use the deep dive" } ], "references": [ "microsoft-clean-architecture", "azure-cloud-design-patterns", "nist-airmf-2023" ], "related": [ { "id": "runtime-architecture", "path": "/runtime-architecture/" }, { "id": "control-plane-runtime-plane", "path": "/control-plane-runtime-plane/" }, { "id": "runtime-intelligence", "path": "/runtime-intelligence/" }, { "id": "performance-hardware", "path": "/performance-hardware/" }, { "id": "governance-and-trust", "path": "/governance-and-trust/" }, { "id": "developers", "path": "/developers/" }, { "id": "developer-runtime-contract", "path": "/developers/runtime-contract/" }, { "id": "developer-evidence-schema", "path": "/developers/evidence-schema/" } ] }, { "id": "clean-architecture-for-mir", "title": "Clean Architecture for Machine Intelligence Runtime", "path": "/clean-architecture-for-mir/", "url": "https://miruntime.com/clean-architecture-for-mir/", "summary": "Apply Clean Architecture, Hexagonal Architecture, and Ports-and-Adapters principles to Machine Intelligence Runtime without placing policy, state, or authority in prompts.", "purpose": "Define inward dependency rules, explicit ports, and capability-first organization for MIR implementations.", "status": "Production practice", "statusLabel": "Production practice", "audience": "Platform architects, senior developers, AI platform teams", "level": "Advanced", "lastReviewed": "2026-06-23", "lastReviewedUtc": "2026-06-23T00:00:00Z", "topics": [ "clean architecture", "hexagonal architecture", "ports and adapters", "dependency inversion", "AI-assisted development" ], "mainConcepts": [ "architectural liquefaction", "dependency rule", "ports", "adapters", "prompt boundary", "capability-first directories" ], "sections": [ { "id": "strictness", "label": "Why AI needs stricter architecture" }, { "id": "layers", "label": "Clean Architecture layer mapping" }, { "id": "ports", "label": "Ports and adapters" }, { "id": "outside-prompt", "label": "What belongs outside the prompt" }, { "id": "capability-first", "label": "Capability-first organization" } ], "references": [ "microsoft-clean-architecture", "nist-airmf-2023", "owasp-prompt-injection-2025" ], "related": [ { "id": "architecture-deep-dive", "path": "/architecture-deep-dive/" }, { "id": "runtime-architecture", "path": "/runtime-architecture/" }, { "id": "developer-runtime-contract", "path": "/developers/runtime-contract/" }, { "id": "governance-and-trust", "path": "/governance-and-trust/" }, { "id": "mir-design-patterns", "path": "/mir-design-patterns/" } ] }, { "id": "mir-design-patterns", "title": "Machine Intelligence Runtime Design Patterns", "path": "/mir-design-patterns/", "url": "https://miruntime.com/mir-design-patterns/", "summary": "Map enterprise design patterns to MIR orchestration, policy, tools, model adapters, recovery, lifecycle, and evidence with compact C# contracts.", "purpose": "Show where established design patterns belong in the seven-layer MIR architecture and which anti-patterns they prevent.", "status": "Production practice", "statusLabel": "Production practice", "audience": "Software architects, senior developers, runtime and platform engineers", "level": "Advanced", "lastReviewed": "2026-06-23", "lastReviewedUtc": "2026-06-23T00:00:00Z", "topics": [ "design patterns", "adapter", "strategy", "saga", "event sourcing", "CQRS", "state machine", "circuit breaker" ], "mainConcepts": [ "pattern placement", "runtime state machine", "typed evidence", "compensation", "provider isolation" ], "sections": [ { "id": "pattern-map", "label": "Pattern map" }, { "id": "placement", "label": "Pattern-to-layer placement" }, { "id": "anti-patterns", "label": "Anti-patterns" }, { "id": "contracts", "label": "Code-oriented contracts" } ], "references": [ "azure-cloud-design-patterns", "microsoft-clean-architecture", "otel-genai" ], "related": [ { "id": "architecture-deep-dive", "path": "/architecture-deep-dive/" }, { "id": "clean-architecture-for-mir", "path": "/clean-architecture-for-mir/" }, { "id": "event-driven-runtime-orchestration", "path": "/event-driven-runtime-orchestration/" }, { "id": "developer-runtime-contract", "path": "/developers/runtime-contract/" }, { "id": "developer-evidence-schema", "path": "/developers/evidence-schema/" } ] }, { "id": "event-driven-runtime-orchestration", "title": "Event-Driven Runtime Orchestration", "path": "/event-driven-runtime-orchestration/", "url": "https://miruntime.com/event-driven-runtime-orchestration/", "summary": "Design asynchronous Machine Intelligence Runtime workflows with durable state, typed events, approvals, checkpoints, recovery, idempotency, and evidence.", "purpose": "Explain why long-running MIR workflows require durable state and event-driven execution rather than an open HTTP request.", "status": "Production practice", "statusLabel": "Production practice", "audience": "Platform architects, distributed-systems engineers, AI runtime teams", "level": "Advanced", "lastReviewed": "2026-06-23", "lastReviewedUtc": "2026-06-23T00:00:00Z", "topics": [ "event-driven architecture", "durable workflow", "human approval", "state machine", "transactional outbox", "idempotency" ], "mainConcepts": [ "durable run", "event sequence", "control loop", "approval queue", "checkpoint", "compensation" ], "sections": [ { "id": "fragility", "label": "Why synchronous execution is fragile" }, { "id": "sequence", "label": "Event sequence" }, { "id": "control-loop", "label": "Control loop" }, { "id": "human-loop", "label": "Human-in-the-loop" }, { "id": "implementation", "label": "Implementation guidance" } ], "references": [ "azure-cloud-design-patterns", "temporal-durable-execution", "otel-genai" ], "related": [ { "id": "architecture-deep-dive", "path": "/architecture-deep-dive/" }, { "id": "control-plane-runtime-plane", "path": "/control-plane-runtime-plane/" }, { "id": "runtime-intelligence", "path": "/runtime-intelligence/" }, { "id": "developer-evidence-schema", "path": "/developers/evidence-schema/" }, { "id": "deployment-tradeoffs", "path": "/deployment-tradeoffs/" } ] }, { "id": "inference-infrastructure", "title": "Inference Infrastructure for Machine Intelligence Runtime", "path": "/inference-infrastructure/", "url": "https://miruntime.com/inference-infrastructure/", "summary": "Understand model-serving concerns—KV cache, batching, prefill, decode, streaming, placement, locality, cost, and failures—without reducing MIR to inference serving.", "purpose": "Define the infrastructure knowledge MIR needs while preserving a provider-neutral model adapter boundary.", "status": "Production practice", "statusLabel": "Production practice", "audience": "AI infrastructure teams, platform architects, performance engineers", "level": "Advanced", "lastReviewed": "2026-06-23", "lastReviewedUtc": "2026-06-23T00:00:00Z", "topics": [ "inference infrastructure", "KV cache", "continuous batching", "prefill", "decode", "vLLM", "Triton", "ONNX Runtime" ], "mainConcepts": [ "model serving boundary", "capacity profile", "streaming", "placement", "safe retry", "provider normalization" ], "sections": [ { "id": "boundary", "label": "MIR is not only model serving" }, { "id": "concerns", "label": "Inference concerns MIR must understand" }, { "id": "adapter-contract", "label": "Model adapter contract" }, { "id": "comparison", "label": "Serving-layer comparison" }, { "id": "measurement", "label": "Measurement discipline" } ], "references": [ "vllm-docs", "triton-architecture", "triton-dynamic-batching", "onnx-runtime" ], "related": [ { "id": "architecture-deep-dive", "path": "/architecture-deep-dive/" }, { "id": "performance-hardware", "path": "/performance-hardware/" }, { "id": "runtime-intelligence", "path": "/runtime-intelligence/" }, { "id": "deployment-tradeoffs", "path": "/deployment-tradeoffs/" }, { "id": "clean-architecture-for-mir", "path": "/clean-architecture-for-mir/" } ] }, { "id": "mlops-lineage-and-agent-drift", "title": "MLOps, Lineage, and Agent Drift", "path": "/mlops-lineage-and-agent-drift/", "url": "https://miruntime.com/mlops-lineage-and-agent-drift/", "summary": "Connect model registries, runtime profiles, evidence, atomic deployment, rollback, and drift controls for long-lived model-driven systems.", "purpose": "Define the operational records and controls needed to understand what was deployed, what ran, and how behavior changes over time.", "status": "Emerging practice", "statusLabel": "Emerging practice", "audience": "MLOps teams, platform architects, governance teams, AI engineers", "level": "Advanced", "lastReviewed": "2026-06-23", "lastReviewedUtc": "2026-06-23T00:00:00Z", "topics": [ "MLOps", "lineage", "model registry", "runtime registry", "atomic deployment", "agent drift", "rollback" ], "mainConcepts": [ "runtime profile versioning", "evidence ledger", "atomic release", "optimization drift", "semantic drift", "environmental drift" ], "sections": [ { "id": "lifecycle", "label": "Deployment is the start" }, { "id": "registries", "label": "Model and runtime registries" }, { "id": "atomic", "label": "Atomic deployment" }, { "id": "taxonomy", "label": "Agent drift taxonomy" }, { "id": "controls", "label": "Drift controls" }, { "id": "status", "label": "Status language" } ], "references": [ "mlflow-model-registry", "nist-airmf-2023", "otel-genai" ], "related": [ { "id": "architecture-deep-dive", "path": "/architecture-deep-dive/" }, { "id": "governance-and-trust", "path": "/governance-and-trust/" }, { "id": "memory-and-evidence", "path": "/memory-and-evidence/" }, { "id": "developer-evidence-schema", "path": "/developers/evidence-schema/" }, { "id": "deployment-tradeoffs", "path": "/deployment-tradeoffs/" } ] }, { "id": "deployment-tradeoffs", "title": "Machine Intelligence Runtime Deployment Trade-offs", "path": "/deployment-tradeoffs/", "url": "https://miruntime.com/deployment-tradeoffs/", "summary": "Compare local, modular monolith, microservices, serverless, cloud-managed, edge, hybrid, and federated MIR deployment shapes while preserving explicit contracts.", "purpose": "Help architects select physical placement based on locality, latency, recovery, authority, evidence, and ownership constraints.", "status": "Editorial guidance", "statusLabel": "Editorial guidance", "audience": "Enterprise architects, infrastructure teams, platform owners, security architects", "level": "Advanced", "lastReviewed": "2026-06-23", "lastReviewedUtc": "2026-06-23T00:00:00Z", "topics": [ "deployment architecture", "modular monolith", "microservices", "serverless", "edge", "federated runtime", "latency" ], "mainConcepts": [ "logical boundary", "physical placement", "latency budget", "locality", "federation", "evidence export" ], "sections": [ { "id": "logical-boundaries", "label": "Preserve logical boundaries" }, { "id": "tradeoffs", "label": "Deployment trade-off table" }, { "id": "latency", "label": "Latency versus purity" }, { "id": "decision", "label": "Decision checklist" } ], "references": [ "microsoft-clean-architecture", "azure-cloud-design-patterns", "nist-airmf-2023" ], "related": [ { "id": "architecture-deep-dive", "path": "/architecture-deep-dive/" }, { "id": "clean-architecture-for-mir", "path": "/clean-architecture-for-mir/" }, { "id": "event-driven-runtime-orchestration", "path": "/event-driven-runtime-orchestration/" }, { "id": "inference-infrastructure", "path": "/inference-infrastructure/" }, { "id": "local-first-control", "path": "/local-first-control/" } ] }, { "id": "teleodynamic-runtimes", "title": "Teleodynamic Runtimes", "path": "/research/teleodynamic-runtimes/", "url": "https://miruntime.com/research/teleodynamic-runtimes/", "summary": "A bounded research program for runtime viability, structural adaptation, goal systems, reflective recovery, benchmarks, and reproducibility without anthropomorphic claims.", "purpose": "Define a cautious research program for runtimes that monitor operating condition, allocate adaptation effort, and propose bounded changes under external policy.", "status": "Research synthesis", "statusLabel": "Research synthesis", "audience": "Researchers, runtime architects, AI-systems engineers, technical reviewers", "level": "Advanced", "lastReviewed": "2026-06-24", "lastReviewedUtc": "2026-06-24T00:00:00Z", "topics": [ "Teleodynamics", "Self-maintenance", "Goal systems", "Structural adaptation", "Reflective control", "Runtime benchmarks", "Reproducibility" ], "mainConcepts": [ "bounded self-maintenance", "viability metrics", "proposal-only adaptation", "external authority", "evidence ladder", "non-anthropomorphic language" ], "sections": [ { "id": "why", "label": "Why this program exists" }, { "id": "map", "label": "Research map" }, { "id": "distinctions", "label": "Core distinctions" }, { "id": "evidence-ladder", "label": "Evidence ladder" }, { "id": "boundaries", "label": "What this program does not claim" }, { "id": "questions", "label": "Open questions" } ], "references": [ "deacon-incomplete-nature-2011", "deacon-teleological-causality-2023", "teleodynamic-learning-2026", "nist-airmf-2023" ], "related": [ { "id": "research", "path": "/research/" }, { "id": "runtime-architecture", "path": "/runtime-architecture/" }, { "id": "runtime-intelligence", "path": "/runtime-intelligence/" }, { "id": "memory-and-evidence", "path": "/memory-and-evidence/" }, { "id": "governance-and-trust", "path": "/governance-and-trust/" }, { "id": "developer-teleodynamic-runtime-profile", "path": "/developers/teleodynamic-runtime-profile/" }, { "id": "runtime-benchmarks-and-evaluation", "path": "/research/runtime-benchmarks-and-evaluation/" }, { "id": "reproducibility-evidence-and-open-questions", "path": "/research/reproducibility-evidence-and-open-questions/" } ] }, { "id": "teleodynamics-and-machine-intelligence", "title": "Teleodynamics and Machine Intelligence", "path": "/research/teleodynamics-and-machine-intelligence/", "url": "https://miruntime.com/research/teleodynamics-and-machine-intelligence/", "summary": "Source-aware definitions of teleodynamics, autopoiesis, enaction, teleonomy, homeostasis, and active inference with careful runtime translations and limitations.", "purpose": "Introduce conceptual foundations while separating biological and philosophical theory from software mechanisms and production claims.", "status": "Research synthesis", "statusLabel": "Research synthesis", "audience": "Researchers, runtime architects, technical readers", "level": "Advanced", "lastReviewed": "2026-06-24", "lastReviewedUtc": "2026-06-24T00:00:00Z", "topics": [ "Teleodynamics", "Autopoiesis", "Enaction", "Teleonomy", "Homeostasis", "Active inference" ], "mainConcepts": [ "constraint coupling", "organizational maintenance", "sensorimotor coupling", "engineered thresholds", "editorial analogy", "testable mechanism" ], "sections": [ { "id": "terms", "label": "Terms and boundaries" }, { "id": "hierarchy", "label": "Deacon hierarchy as editorial mapping" }, { "id": "mechanism", "label": "Metaphor versus mechanism" }, { "id": "implications", "label": "Research implications for MIR" }, { "id": "limitations", "label": "Limitations" } ], "references": [ "deacon-incomplete-nature-2011", "deacon-teleological-causality-2023", "maturana-varela-autopoiesis-1980", "varela-maturana-uribe-autopoiesis-1974", "varela-thompson-rosch-embodied-mind-1991", "friston-free-energy-2010" ], "related": [ { "id": "research", "path": "/research/" }, { "id": "teleodynamic-runtimes", "path": "/research/teleodynamic-runtimes/" }, { "id": "runtime-architecture", "path": "/runtime-architecture/" }, { "id": "runtime-intelligence", "path": "/runtime-intelligence/" }, { "id": "memory-and-evidence", "path": "/memory-and-evidence/" }, { "id": "governance-and-trust", "path": "/governance-and-trust/" }, { "id": "developer-teleodynamic-runtime-profile", "path": "/developers/teleodynamic-runtime-profile/" } ] }, { "id": "teleodynamic-learning-and-structural-adaptation", "title": "Teleodynamic Learning and Structural Adaptation", "path": "/research/teleodynamic-learning-and-structural-adaptation/", "url": "https://miruntime.com/research/teleodynamic-learning-and-structural-adaptation/", "summary": "A two-timescale research model for parameter adaptation, governed structural edits, resource gating, no-op, rollback, and evidence.", "purpose": "Explain how changes to runtime structure differ from optimization inside a fixed hypothesis class and what controls they require.", "status": "Research proposal", "statusLabel": "Research proposal", "audience": "AI researchers, runtime architects, research engineers", "level": "Advanced", "lastReviewed": "2026-06-24", "lastReviewedUtc": "2026-06-24T00:00:00Z", "topics": [ "Teleodynamic learning", "Structural adaptation", "Resource-bounded learning", "No-op", "Continual learning", "Runtime intelligence" ], "mainConcepts": [ "two-timescale control", "parameter state", "discrete structure", "resource gating", "structural edit proposal", "no-op stability" ], "sections": [ { "id": "fixed-evolving", "label": "Fixed model versus evolving structure" }, { "id": "state-model", "label": "Conceptual state model" }, { "id": "loops", "label": "Two-timescale loop" }, { "id": "operators", "label": "Structural edit operators" }, { "id": "no-op", "label": "Why no-op matters" }, { "id": "comparison", "label": "Comparison" }, { "id": "evidence", "label": "Evidence requirements" } ], "references": [ "teleodynamic-learning-2026", "test-time-compute-2024", "tree-of-thoughts-2023", "vigil-2025", "friston-free-energy-2010" ], "related": [ { "id": "research", "path": "/research/" }, { "id": "teleodynamic-runtimes", "path": "/research/teleodynamic-runtimes/" }, { "id": "runtime-intelligence", "path": "/runtime-intelligence/" }, { "id": "runtime-architecture", "path": "/runtime-architecture/" }, { "id": "memory-and-evidence", "path": "/memory-and-evidence/" }, { "id": "developer-teleodynamic-runtime-profile", "path": "/developers/teleodynamic-runtime-profile/" }, { "id": "developer-durable-execution-and-recovery", "path": "/developers/durable-execution-and-recovery/" }, { "id": "runtime-benchmarks-and-evaluation", "path": "/research/runtime-benchmarks-and-evaluation/" } ] }, { "id": "goal-systems-homeostasis-and-self-maintenance", "title": "Goal Systems, Homeostasis, and Self-Maintenance", "path": "/research/goal-systems-homeostasis-and-self-maintenance/", "url": "https://miruntime.com/research/goal-systems-homeostasis-and-self-maintenance/", "summary": "Bounded goal hierarchies, engineered viability metrics, typed goal changes, conflict resolution, risks, and controls for adaptive runtimes.", "purpose": "Show how internal control objectives can support valid operation without creating an open-ended self-preservation interest.", "status": "Research synthesis", "statusLabel": "Research synthesis", "audience": "Runtime architects, governance engineers, researchers", "level": "Advanced", "lastReviewed": "2026-06-24", "lastReviewedUtc": "2026-06-24T00:00:00Z", "topics": [ "Goal systems", "Homeostasis", "Self-maintenance", "Viability metrics", "Goal manipulation", "Runtime governance" ], "mainConcepts": [ "external objective", "derived subgoal", "runtime control objective", "immutable policy", "viability vector", "typed goal change" ], "sections": [ { "id": "hierarchy", "label": "Goal hierarchy" }, { "id": "viability", "label": "Viability vector" }, { "id": "change-policy", "label": "Goal-change policy" }, { "id": "conflicts", "label": "Conflict resolution" }, { "id": "risks", "label": "Risks" }, { "id": "controls", "label": "Controls" } ], "references": [ "deacon-incomplete-nature-2011", "maturana-varela-autopoiesis-1980", "nist-airmf-2023", "owasp-agentic-threats" ], "related": [ { "id": "research", "path": "/research/" }, { "id": "teleodynamic-runtimes", "path": "/research/teleodynamic-runtimes/" }, { "id": "governance-and-trust", "path": "/governance-and-trust/" }, { "id": "runtime-architecture", "path": "/runtime-architecture/" }, { "id": "memory-and-evidence", "path": "/memory-and-evidence/" }, { "id": "developer-tool-connectors-and-policy", "path": "/developers/tool-connectors-and-policy/" }, { "id": "developer-teleodynamic-runtime-profile", "path": "/developers/teleodynamic-runtime-profile/" } ] }, { "id": "reflective-control-and-runtime-recovery", "title": "Reflective Control and Runtime Recovery", "path": "/research/reflective-control-and-runtime-recovery/", "url": "https://miruntime.com/research/reflective-control-and-runtime-recovery/", "summary": "A bounded reflective critic model with trigger conditions, recovery taxonomy, authority separation, checkpoints, and independent validation.", "purpose": "Connect reflective diagnosis to controlled MIR recovery without allowing a critic to become an unchecked authority.", "status": "Research synthesis", "statusLabel": "Research synthesis", "audience": "Runtime architects, reliability engineers, AI researchers", "level": "Advanced", "lastReviewed": "2026-06-24", "lastReviewedUtc": "2026-06-24T00:00:00Z", "topics": [ "Reflective control", "Runtime recovery", "Self-monitoring", "Checkpoints", "Critic loops", "Operator control" ], "mainConcepts": [ "reflective critic", "proposal authority separation", "trigger condition", "recovery taxonomy", "checkpoint", "independent verifier" ], "sections": [ { "id": "critic", "label": "Reflective critic boundary" }, { "id": "triggers", "label": "Trigger conditions" }, { "id": "sequence", "label": "Control sequence" }, { "id": "taxonomy", "label": "Recovery taxonomy" }, { "id": "risks", "label": "Research risks" } ], "references": [ "vigil-2025", "atlas-rtc-2026", "owasp-agentic-threats", "nist-airmf-2023" ], "related": [ { "id": "research", "path": "/research/" }, { "id": "teleodynamic-runtimes", "path": "/research/teleodynamic-runtimes/" }, { "id": "runtime-intelligence", "path": "/runtime-intelligence/" }, { "id": "event-driven-runtime-orchestration", "path": "/event-driven-runtime-orchestration/" }, { "id": "memory-and-evidence", "path": "/memory-and-evidence/" }, { "id": "governance-and-trust", "path": "/governance-and-trust/" }, { "id": "developer-durable-execution-and-recovery", "path": "/developers/durable-execution-and-recovery/" }, { "id": "developer-teleodynamic-runtime-profile", "path": "/developers/teleodynamic-runtime-profile/" } ] }, { "id": "runtime-benchmarks-and-evaluation", "title": "Runtime Benchmarks and Evaluation", "path": "/research/runtime-benchmarks-and-evaluation/", "url": "https://miruntime.com/research/runtime-benchmarks-and-evaluation/", "summary": "A runtime evaluation framework covering task outcomes, recovery, policy, evidence, resource efficiency, structural adaptation, reproducibility, and operator control.", "purpose": "Define how MIR and teleodynamic-runtime proposals should be evaluated beyond model accuracy.", "status": "Editorial guidance", "statusLabel": "Editorial guidance", "audience": "Research engineers, evaluation teams, platform architects, governance teams", "level": "Advanced", "lastReviewed": "2026-06-24", "lastReviewedUtc": "2026-06-24T00:00:00Z", "topics": [ "Runtime benchmarks", "Runtime evaluation", "Reproducibility", "Recovery", "Policy compliance", "Resource efficiency" ], "mainConcepts": [ "end-to-end utility", "first-attempt quality", "recovery rate", "evidence completeness", "no-op stability", "benchmark manifest" ], "sections": [ { "id": "dimensions", "label": "Evaluation dimensions" }, { "id": "suite", "label": "Benchmark suite design" }, { "id": "perturbations", "label": "Perturbation tests" }, { "id": "baselines", "label": "Baselines and ablations" }, { "id": "manifest", "label": "Benchmark manifest" }, { "id": "reporting", "label": "Reporting rules" } ], "references": [ "test-time-compute-2024", "nist-airmf-2023", "nist-genai-profile-2024", "otel-genai" ], "related": [ { "id": "research", "path": "/research/" }, { "id": "teleodynamic-runtimes", "path": "/research/teleodynamic-runtimes/" }, { "id": "runtime-architecture", "path": "/runtime-architecture/" }, { "id": "runtime-intelligence", "path": "/runtime-intelligence/" }, { "id": "memory-and-evidence", "path": "/memory-and-evidence/" }, { "id": "governance-and-trust", "path": "/governance-and-trust/" }, { "id": "developer-testing-machine-intelligence-runtimes", "path": "/developers/testing-machine-intelligence-runtimes/" }, { "id": "developer-observability-and-evidence", "path": "/developers/observability-and-evidence/" } ] }, { "id": "reproducibility-evidence-and-open-questions", "title": "Reproducibility, Evidence, and Open Questions", "path": "/research/reproducibility-evidence-and-open-questions/", "url": "https://miruntime.com/research/reproducibility-evidence-and-open-questions/", "summary": "Replay levels, research-grade evidence packages, claim registers, negative results, and an open agenda for stochastic tool-using runtimes.", "purpose": "Define what can and cannot be reproduced in stochastic, time-dependent, tool-using runtime systems.", "status": "Editorial guidance", "statusLabel": "Editorial guidance", "audience": "Researchers, reviewers, platform teams, auditors", "level": "Advanced", "lastReviewed": "2026-06-24", "lastReviewedUtc": "2026-06-24T00:00:00Z", "topics": [ "Reproducibility", "Evidence", "Claim register", "Negative results", "Runtime evaluation", "Open questions" ], "mainConcepts": [ "exact replay", "functional replay", "partial replay", "evidence package", "claim register", "negative result" ], "sections": [ { "id": "replay", "label": "Replay levels" }, { "id": "package", "label": "Evidence package" }, { "id": "claims", "label": "Claim register" }, { "id": "negative-results", "label": "Negative and null results" }, { "id": "agenda", "label": "Open research agenda" } ], "references": [ "nist-airmf-2023", "nist-genai-profile-2024", "otel-genai", "teleodynamic-learning-2026" ], "related": [ { "id": "research", "path": "/research/" }, { "id": "teleodynamic-runtimes", "path": "/research/teleodynamic-runtimes/" }, { "id": "memory-and-evidence", "path": "/memory-and-evidence/" }, { "id": "runtime-architecture", "path": "/runtime-architecture/" }, { "id": "governance-and-trust", "path": "/governance-and-trust/" }, { "id": "developer-observability-and-evidence", "path": "/developers/observability-and-evidence/" }, { "id": "developer-testing-machine-intelligence-runtimes", "path": "/developers/testing-machine-intelligence-runtimes/" }, { "id": "runtime-benchmarks-and-evaluation", "path": "/research/runtime-benchmarks-and-evaluation/" } ] }, { "id": "report-teleodynamic-machine-intelligence-runtime", "title": "Teleodynamic Machine Intelligence Runtime: A Research Synthesis", "path": "/research/reports/teleodynamic-machine-intelligence-runtime/", "url": "https://miruntime.com/research/reports/teleodynamic-machine-intelligence-runtime/", "summary": "A source-aware synthesis of teleodynamics, bounded goal systems, structural adaptation, reflective recovery, developer contracts, evaluation, risks, and evidence requirements.", "purpose": "Rewrite and filter supplied research reports into a cautious, source-aware architecture synthesis with explicit omitted-claim boundaries.", "status": "Editorial synthesis", "statusLabel": "Editorial synthesis", "audience": "Researchers, senior engineers, runtime architects, technical reviewers", "level": "Advanced", "lastReviewed": "2026-06-24", "lastReviewedUtc": "2026-06-24T00:00:00Z", "topics": [ "Teleodynamic runtime", "Editorial synthesis", "Structural adaptation", "Goal systems", "Reflective recovery", "Runtime benchmarks", "Reproducibility" ], "mainConcepts": [ "editorial research synthesis", "bounded adaptation", "external authority", "viability metrics", "reflective recovery", "evidence requirements" ], "sections": [ { "id": "summary", "label": "Executive summary" }, { "id": "relevance", "label": "Why teleodynamics is relevant" }, { "id": "foundations", "label": "Foundational concepts" }, { "id": "baseline", "label": "MIR baseline" }, { "id": "loops", "label": "Fast and slow adaptation loops" }, { "id": "goals", "label": "Goal hierarchy and viability" }, { "id": "reflection", "label": "Reflective control and recovery" }, { "id": "contracts", "label": "Developer-contract implications" }, { "id": "evaluation", "label": "Benchmark framework" }, { "id": "risks", "label": "Security and alignment risks" }, { "id": "matrix", "label": "Practice versus proposal" }, { "id": "reproducibility", "label": "Reproducibility requirements" }, { "id": "questions", "label": "Open questions" }, { "id": "deferred", "label": "Deferred or omitted claims" }, { "id": "references-note", "label": "Source method" } ], "references": [ "deacon-incomplete-nature-2011", "deacon-teleological-causality-2023", "maturana-varela-autopoiesis-1980", "varela-thompson-rosch-embodied-mind-1991", "friston-free-energy-2010", "teleodynamic-learning-2026", "airi-2026", "nist-airmf-2023", "owasp-agentic-threats" ], "related": [ { "id": "research-reports", "path": "/research/reports/" }, { "id": "research", "path": "/research/" }, { "id": "teleodynamic-runtimes", "path": "/research/teleodynamic-runtimes/" }, { "id": "runtime-architecture", "path": "/runtime-architecture/" }, { "id": "runtime-intelligence", "path": "/runtime-intelligence/" }, { "id": "memory-and-evidence", "path": "/memory-and-evidence/" }, { "id": "governance-and-trust", "path": "/governance-and-trust/" }, { "id": "developer-teleodynamic-runtime-profile", "path": "/developers/teleodynamic-runtime-profile/" }, { "id": "runtime-benchmarks-and-evaluation", "path": "/research/runtime-benchmarks-and-evaluation/" } ] }, { "id": "developer-implementation-guides", "title": "Machine Intelligence Runtime Implementation Guides", "path": "/developers/implementation-guides/", "url": "https://miruntime.com/developers/implementation-guides/", "summary": "A guide map for building lifecycle, adapters, tools, context, recovery, evidence, testing, teleodynamic extensions, and operations around model proposals.", "purpose": "Define the minimum runtime surface and implementation posture for a provider-neutral, evidence-first runtime boundary.", "status": "Editorial guidance", "statusLabel": "Editorial guidance", "audience": "Developers, platform engineers, technical leads", "level": "Technical", "lastReviewed": "2026-06-24", "lastReviewedUtc": "2026-06-24T00:00:00Z", "topics": [ "Implementation guides", "Ports and adapters", "Runtime contract", "Lifecycle", "Evidence-first design" ], "mainConcepts": [ "minimum runtime surface", "provider-neutral core", "deterministic boundary", "capability-first organization", "evidence-first error handling" ], "sections": [ { "id": "surface", "label": "Minimum runtime surface" }, { "id": "map", "label": "Guide map" }, { "id": "posture", "label": "Reference implementation posture" }, { "id": "non-goals", "label": "Non-goals" } ], "references": [ "microsoft-clean-architecture", "azure-cloud-design-patterns", "nist-airmf-2023" ], "related": [ { "id": "developers", "path": "/developers/" }, { "id": "developer-runtime-contract", "path": "/developers/runtime-contract/" }, { "id": "developer-tool-contracts", "path": "/developers/tool-contracts/" }, { "id": "developer-evidence-schema", "path": "/developers/evidence-schema/" }, { "id": "developer-implementation-checklist", "path": "/developers/implementation-checklist/" }, { "id": "architecture-deep-dive", "path": "/architecture-deep-dive/" }, { "id": "teleodynamic-runtimes", "path": "/research/teleodynamic-runtimes/" } ] }, { "id": "developer-quickstart", "title": "Machine Intelligence Runtime Quickstart", "path": "/developers/quickstart/", "url": "https://miruntime.com/developers/quickstart/", "summary": "A coherent conceptual C# quickstart for a reversible dependency-update run with lifecycle state, policy, checkpoint, tool execution, tests, and evidence.", "purpose": "Walk through the smallest complete MIR workflow without implying a downloadable SDK or package.", "status": "Conceptual reference", "statusLabel": "Conceptual reference", "audience": "Application developers and platform engineers", "level": "Intermediate", "lastReviewed": "2026-06-24", "lastReviewedUtc": "2026-06-24T00:00:00Z", "topics": [ "Quickstart", "Dependency update", "Runtime contract", "C#", "Evidence timeline" ], "mainConcepts": [ "reversible workflow", "run request", "runtime contract", "step execution", "evidence event", "terminal state" ], "sections": [ { "id": "scenario", "label": "Scenario" }, { "id": "steps", "label": "Build steps" }, { "id": "contracts", "label": "C# reference contracts" }, { "id": "timeline", "label": "Expected event timeline" }, { "id": "tests", "label": "Quickstart test checklist" } ], "references": [ "microsoft-clean-architecture", "nist-airmf-2023" ], "related": [ { "id": "developers", "path": "/developers/" }, { "id": "developer-runtime-contract", "path": "/developers/runtime-contract/" }, { "id": "developer-tool-contracts", "path": "/developers/tool-contracts/" }, { "id": "developer-evidence-schema", "path": "/developers/evidence-schema/" }, { "id": "developer-implementation-checklist", "path": "/developers/implementation-checklist/" }, { "id": "developer-implementation-guides", "path": "/developers/implementation-guides/" }, { "id": "event-driven-runtime-orchestration", "path": "/event-driven-runtime-orchestration/" }, { "id": "runtime-benchmarks-and-evaluation", "path": "/research/runtime-benchmarks-and-evaluation/" } ] }, { "id": "developer-run-lifecycle-state-machine", "title": "Run Lifecycle State Machine", "path": "/developers/run-lifecycle-state-machine/", "url": "https://miruntime.com/developers/run-lifecycle-state-machine/", "summary": "Explicit run states, transition actors, invariants, optimistic concurrency, idempotency, stale-worker handling, and provider-independent persistence.", "purpose": "Make long-running machine-intelligence work durable, testable, and recoverable through a typed state machine.", "status": "Production practice", "statusLabel": "Production practice", "audience": "Platform engineers, backend developers, reliability engineers", "level": "Advanced", "lastReviewed": "2026-06-24", "lastReviewedUtc": "2026-06-24T00:00:00Z", "topics": [ "Run lifecycle", "State machine", "Optimistic concurrency", "Idempotency", "Durable execution" ], "mainConcepts": [ "created", "provisioning", "running", "awaiting approval", "recovering", "terminal state" ], "sections": [ { "id": "transitions", "label": "State-transition table" }, { "id": "invariants", "label": "Invariants" }, { "id": "concurrency", "label": "Concurrency" }, { "id": "contracts", "label": "C# contracts" }, { "id": "persistence", "label": "Persistence guidance" } ], "references": [ "azure-cloud-design-patterns", "microsoft-clean-architecture" ], "related": [ { "id": "developers", "path": "/developers/" }, { "id": "developer-runtime-contract", "path": "/developers/runtime-contract/" }, { "id": "developer-tool-contracts", "path": "/developers/tool-contracts/" }, { "id": "developer-evidence-schema", "path": "/developers/evidence-schema/" }, { "id": "developer-implementation-checklist", "path": "/developers/implementation-checklist/" }, { "id": "event-driven-runtime-orchestration", "path": "/event-driven-runtime-orchestration/" }, { "id": "developer-durable-execution-and-recovery", "path": "/developers/durable-execution-and-recovery/" }, { "id": "reflective-control-and-runtime-recovery", "path": "/research/reflective-control-and-runtime-recovery/" } ] }, { "id": "developer-model-adapters", "title": "Model Adapters for Machine Intelligence Runtime", "path": "/developers/model-adapters/", "url": "https://miruntime.com/developers/model-adapters/", "summary": "A provider-neutral model boundary for capabilities, streaming, usage, placement, safe retries, normalized errors, and deterministic fake adapters.", "purpose": "Prevent model-provider details from owning lifecycle, authorization, evidence retention, or business use cases.", "status": "Production practice", "statusLabel": "Production practice", "audience": "AI platform engineers, backend developers, infrastructure teams", "level": "Advanced", "lastReviewed": "2026-06-24", "lastReviewedUtc": "2026-06-24T00:00:00Z", "topics": [ "Model adapters", "Provider abstraction", "Streaming", "Capabilities", "Error normalization" ], "mainConcepts": [ "capability profile", "model request", "model candidate", "usage metadata", "normalized failure", "safe retry" ], "sections": [ { "id": "responsibilities", "label": "Adapter responsibilities" }, { "id": "outside", "label": "What stays outside" }, { "id": "contracts", "label": "C# contracts" }, { "id": "failures", "label": "Failure normalization" }, { "id": "tests", "label": "Tests" } ], "references": [ "onnx-runtime", "vllm-docs", "triton-architecture", "microsoft-clean-architecture" ], "related": [ { "id": "developers", "path": "/developers/" }, { "id": "developer-runtime-contract", "path": "/developers/runtime-contract/" }, { "id": "developer-tool-contracts", "path": "/developers/tool-contracts/" }, { "id": "developer-evidence-schema", "path": "/developers/evidence-schema/" }, { "id": "developer-implementation-checklist", "path": "/developers/implementation-checklist/" }, { "id": "inference-infrastructure", "path": "/inference-infrastructure/" }, { "id": "developer-deployment-and-operations", "path": "/developers/deployment-and-operations/" }, { "id": "runtime-intelligence", "path": "/runtime-intelligence/" } ] }, { "id": "developer-tool-connectors-and-policy", "title": "Tool Connectors and Runtime Policy", "path": "/developers/tool-connectors-and-policy/", "url": "https://miruntime.com/developers/tool-connectors-and-policy/", "summary": "Stable tool identity, action envelopes, policy outcomes, credential isolation, MCP boundaries, approvals, and conceptual C# ports.", "purpose": "Treat every model-proposed side effect as a typed, policy-evaluated, credential-scoped operation.", "status": "Production practice", "statusLabel": "Production practice", "audience": "Backend developers, security engineers, platform teams", "level": "Advanced", "lastReviewed": "2026-06-24", "lastReviewedUtc": "2026-06-24T00:00:00Z", "topics": [ "Tool connectors", "Policy engine", "Approvals", "Credentials", "MCP", "Side effects" ], "mainConcepts": [ "stable tool key", "action envelope", "policy outcome", "scoped credential", "approval gateway", "MCP boundary" ], "sections": [ { "id": "identity", "label": "Stable tool identity" }, { "id": "envelope", "label": "Tool action envelope" }, { "id": "policy", "label": "Policy decision" }, { "id": "credentials", "label": "Credentials" }, { "id": "mcp", "label": "MCP boundary" }, { "id": "contracts", "label": "C# contracts" } ], "references": [ "mcp-spec-2025", "owasp-agentic-threats", "owasp-prompt-injection-2025", "nist-airmf-2023" ], "related": [ { "id": "developers", "path": "/developers/" }, { "id": "developer-runtime-contract", "path": "/developers/runtime-contract/" }, { "id": "developer-tool-contracts", "path": "/developers/tool-contracts/" }, { "id": "developer-evidence-schema", "path": "/developers/evidence-schema/" }, { "id": "developer-implementation-checklist", "path": "/developers/implementation-checklist/" }, { "id": "agent-tool-execution", "path": "/agent-tool-execution/" }, { "id": "governance-and-trust", "path": "/governance-and-trust/" }, { "id": "goal-systems-homeostasis-and-self-maintenance", "path": "/research/goal-systems-homeostasis-and-self-maintenance/" } ] }, { "id": "developer-memory-context-and-lineage", "title": "Memory, Context, and Lineage for MIR", "path": "/developers/memory-context-and-lineage/", "url": "https://miruntime.com/developers/memory-context-and-lineage/", "summary": "Attributable context packages, governed memory records, assembly sequence, contamination controls, lineage, and provider-neutral C# ports.", "purpose": "Make every context selection and memory projection attributable, scoped, correctable, and replayable.", "status": "Editorial guidance", "statusLabel": "Editorial guidance", "audience": "Application developers, data engineers, governance teams", "level": "Advanced", "lastReviewed": "2026-06-24", "lastReviewedUtc": "2026-06-24T00:00:00Z", "topics": [ "Context assembly", "Memory governance", "Lineage", "Provenance", "Contamination" ], "mainConcepts": [ "context package", "source hash", "memory scope", "selection reason", "contamination control", "lineage chain" ], "sections": [ { "id": "context", "label": "Context package" }, { "id": "memory", "label": "Memory record" }, { "id": "assembly", "label": "Context assembly" }, { "id": "contamination", "label": "Contamination controls" }, { "id": "lineage", "label": "Lineage" }, { "id": "contracts", "label": "C# contracts" } ], "references": [ "nist-genai-profile-2024", "owasp-prompt-injection-2025", "otel-genai" ], "related": [ { "id": "developers", "path": "/developers/" }, { "id": "developer-runtime-contract", "path": "/developers/runtime-contract/" }, { "id": "developer-tool-contracts", "path": "/developers/tool-contracts/" }, { "id": "developer-evidence-schema", "path": "/developers/evidence-schema/" }, { "id": "developer-implementation-checklist", "path": "/developers/implementation-checklist/" }, { "id": "memory-and-evidence", "path": "/memory-and-evidence/" }, { "id": "mlops-lineage-and-agent-drift", "path": "/mlops-lineage-and-agent-drift/" }, { "id": "reproducibility-evidence-and-open-questions", "path": "/research/reproducibility-evidence-and-open-questions/" } ] }, { "id": "developer-durable-execution-and-recovery", "title": "Durable Execution and Recovery for MIR", "path": "/developers/durable-execution-and-recovery/", "url": "https://miruntime.com/developers/durable-execution-and-recovery/", "summary": "Durable workflow styles, event resumption, retries, checkpoints, rerouting, compensation, idempotency, and conceptual recovery ports.", "purpose": "Ensure inference, tools, approvals, retries, and evidence can safely outlive an HTTP request and survive partial failure.", "status": "Production practice", "statusLabel": "Production practice", "audience": "Platform engineers, backend developers, SRE teams", "level": "Advanced", "lastReviewed": "2026-06-24", "lastReviewedUtc": "2026-06-24T00:00:00Z", "topics": [ "Durable execution", "Recovery", "Checkpoint", "Idempotency", "Compensation", "Transactional outbox" ], "mainConcepts": [ "resumable run", "checkpoint store", "recovery plan", "effect receipt", "dead-letter queue", "compensation" ], "sections": [ { "id": "why", "label": "Why durable execution" }, { "id": "styles", "label": "Compatible implementation styles" }, { "id": "events", "label": "Event sequence" }, { "id": "patterns", "label": "Recovery patterns" }, { "id": "idempotency", "label": "Idempotency" }, { "id": "contracts", "label": "C# contracts" }, { "id": "transaction", "label": "Transactional boundary" } ], "references": [ "azure-cloud-design-patterns", "microsoft-clean-architecture", "nist-airmf-2023" ], "related": [ { "id": "developers", "path": "/developers/" }, { "id": "developer-runtime-contract", "path": "/developers/runtime-contract/" }, { "id": "developer-tool-contracts", "path": "/developers/tool-contracts/" }, { "id": "developer-evidence-schema", "path": "/developers/evidence-schema/" }, { "id": "developer-implementation-checklist", "path": "/developers/implementation-checklist/" }, { "id": "event-driven-runtime-orchestration", "path": "/event-driven-runtime-orchestration/" }, { "id": "developer-run-lifecycle-state-machine", "path": "/developers/run-lifecycle-state-machine/" }, { "id": "reflective-control-and-runtime-recovery", "path": "/research/reflective-control-and-runtime-recovery/" } ] }, { "id": "developer-observability-and-evidence", "title": "Observability and Evidence for AI Runtimes", "path": "/developers/observability-and-evidence/", "url": "https://miruntime.com/developers/observability-and-evidence/", "summary": "Distinguish operational telemetry from reviewer-facing evidence, define correlation identities and event requirements, redact sensitive data, and map to OpenTelemetry.", "purpose": "Make runtime behavior operable while preserving typed explanations of why a run produced an outcome.", "status": "Production practice", "statusLabel": "Production practice", "audience": "Platform engineers, SRE teams, governance engineers, auditors", "level": "Advanced", "lastReviewed": "2026-06-24", "lastReviewedUtc": "2026-06-24T00:00:00Z", "topics": [ "Observability", "Evidence", "OpenTelemetry", "Redaction", "Audit" ], "mainConcepts": [ "trace identity", "run identity", "event sequence", "integrity metadata", "privacy classification", "evidence ledger" ], "sections": [ { "id": "difference", "label": "Observability versus evidence" }, { "id": "correlation", "label": "Correlation model" }, { "id": "events", "label": "Event requirements" }, { "id": "redaction", "label": "Redaction" }, { "id": "contracts", "label": "C# evidence ledger" }, { "id": "otel", "label": "OpenTelemetry mapping" } ], "references": [ "otel-genai", "nist-airmf-2023", "nist-genai-profile-2024" ], "related": [ { "id": "developers", "path": "/developers/" }, { "id": "developer-runtime-contract", "path": "/developers/runtime-contract/" }, { "id": "developer-tool-contracts", "path": "/developers/tool-contracts/" }, { "id": "developer-evidence-schema", "path": "/developers/evidence-schema/" }, { "id": "developer-implementation-checklist", "path": "/developers/implementation-checklist/" }, { "id": "memory-and-evidence", "path": "/memory-and-evidence/" }, { "id": "mlops-lineage-and-agent-drift", "path": "/mlops-lineage-and-agent-drift/" }, { "id": "reproducibility-evidence-and-open-questions", "path": "/research/reproducibility-evidence-and-open-questions/" } ] }, { "id": "developer-testing-machine-intelligence-runtimes", "title": "Testing Machine Intelligence Runtimes", "path": "/developers/testing-machine-intelligence-runtimes/", "url": "https://miruntime.com/developers/testing-machine-intelligence-runtimes/", "summary": "A testing model for deterministic contracts, stochastic behavior, security, recovery, evidence, load, deployment, repeated trials, and fault injection.", "purpose": "Define test layers and evidence expectations for a runtime whose model behavior is probabilistic but controls must remain deterministic.", "status": "Editorial guidance", "statusLabel": "Editorial guidance", "audience": "Developers, QA engineers, security teams, research engineers", "level": "Advanced", "lastReviewed": "2026-06-24", "lastReviewedUtc": "2026-06-24T00:00:00Z", "topics": [ "Runtime testing", "Stochastic tests", "Fault injection", "Security tests", "Golden scenarios" ], "mainConcepts": [ "contract test", "stochastic trial", "fault injection", "evidence assertion", "security scenario", "deployment test" ], "sections": [ { "id": "model", "label": "Testing model" }, { "id": "matrix", "label": "Test matrix" }, { "id": "golden", "label": "Golden scenarios" }, { "id": "trials", "label": "Repeated trials" }, { "id": "faults", "label": "Fault injection" }, { "id": "security", "label": "Security tests" }, { "id": "examples", "label": "C# test example" } ], "references": [ "nist-genai-profile-2024", "owasp-agentic-threats", "owasp-prompt-injection-2025" ], "related": [ { "id": "developers", "path": "/developers/" }, { "id": "developer-runtime-contract", "path": "/developers/runtime-contract/" }, { "id": "developer-tool-contracts", "path": "/developers/tool-contracts/" }, { "id": "developer-evidence-schema", "path": "/developers/evidence-schema/" }, { "id": "developer-implementation-checklist", "path": "/developers/implementation-checklist/" }, { "id": "mlops-lineage-and-agent-drift", "path": "/mlops-lineage-and-agent-drift/" }, { "id": "runtime-benchmarks-and-evaluation", "path": "/research/runtime-benchmarks-and-evaluation/" }, { "id": "reproducibility-evidence-and-open-questions", "path": "/research/reproducibility-evidence-and-open-questions/" } ] }, { "id": "developer-teleodynamic-runtime-profile", "title": "Teleodynamic Runtime Profile", "path": "/developers/teleodynamic-runtime-profile/", "url": "https://miruntime.com/developers/teleodynamic-runtime-profile/", "summary": "An optional research-only extension profile for bounded goal systems, viability metrics, reflection policy, structural-edit proposals, and immutable constraints.", "purpose": "Translate selected teleodynamic research ideas into explicit reviewable fields without granting open-ended autonomy.", "status": "Research proposal", "statusLabel": "Research proposal", "audience": "Research engineers, runtime architects, governance reviewers", "level": "Advanced", "lastReviewed": "2026-06-24", "lastReviewedUtc": "2026-06-24T00:00:00Z", "topics": [ "Teleodynamic runtime profile", "Research proposal", "Goal system", "Viability metric", "Reflective critic", "Structural adaptation" ], "mainConcepts": [ "namespaced extension", "goal node", "viability metric", "reflection policy", "structural edit proposal", "immutable constraint" ], "sections": [ { "id": "status", "label": "Research-only status" }, { "id": "extension", "label": "Extension model" }, { "id": "goals", "label": "Goal system" }, { "id": "viability", "label": "Viability" }, { "id": "reflection", "label": "Reflection" }, { "id": "adaptation", "label": "Structural adaptation" }, { "id": "constraints", "label": "Immutable constraints" }, { "id": "contracts", "label": "C# conceptual types" }, { "id": "evaluation", "label": "Evaluation" }, { "id": "language", "label": "Non-anthropomorphic language" } ], "references": [ "teleodynamic-learning-2026", "deacon-incomplete-nature-2011", "nist-airmf-2023", "owasp-agentic-threats" ], "related": [ { "id": "developers", "path": "/developers/" }, { "id": "developer-runtime-contract", "path": "/developers/runtime-contract/" }, { "id": "developer-tool-contracts", "path": "/developers/tool-contracts/" }, { "id": "developer-evidence-schema", "path": "/developers/evidence-schema/" }, { "id": "developer-implementation-checklist", "path": "/developers/implementation-checklist/" }, { "id": "teleodynamic-runtimes", "path": "/research/teleodynamic-runtimes/" }, { "id": "goal-systems-homeostasis-and-self-maintenance", "path": "/research/goal-systems-homeostasis-and-self-maintenance/" }, { "id": "runtime-benchmarks-and-evaluation", "path": "/research/runtime-benchmarks-and-evaluation/" } ] }, { "id": "developer-deployment-and-operations", "title": "MIR Deployment and Operations", "path": "/developers/deployment-and-operations/", "url": "https://miruntime.com/developers/deployment-and-operations/", "summary": "Operational deployment guidance for logical boundaries, environments, secrets, atomic release manifests, rollback, runbooks, SLOs, and evidence compatibility.", "purpose": "Turn MIR architectural guidance into a concrete operational checklist without prescribing one physical topology.", "status": "Production practice", "statusLabel": "Production practice", "audience": "Platform engineers, SRE teams, technical leads, security teams", "level": "Advanced", "lastReviewed": "2026-06-24", "lastReviewedUtc": "2026-06-24T00:00:00Z", "topics": [ "Deployment", "Operations", "Release manifest", "Rollback", "Runbook", "SLO" ], "mainConcepts": [ "logical boundary", "environment model", "secret isolation", "atomic release", "backward-compatible evidence", "operational runbook" ], "sections": [ { "id": "boundaries", "label": "Logical versus physical architecture" }, { "id": "environments", "label": "Environment model" }, { "id": "configuration", "label": "Configuration and secrets" }, { "id": "manifest", "label": "Atomic release manifest" }, { "id": "rollback", "label": "Rollback" }, { "id": "runbook", "label": "Operational runbook" }, { "id": "slos", "label": "SLOs and metrics" } ], "references": [ "azure-cloud-design-patterns", "nist-airmf-2023", "otel-genai" ], "related": [ { "id": "developers", "path": "/developers/" }, { "id": "developer-runtime-contract", "path": "/developers/runtime-contract/" }, { "id": "developer-tool-contracts", "path": "/developers/tool-contracts/" }, { "id": "developer-evidence-schema", "path": "/developers/evidence-schema/" }, { "id": "developer-implementation-checklist", "path": "/developers/implementation-checklist/" }, { "id": "deployment-tradeoffs", "path": "/deployment-tradeoffs/" }, { "id": "inference-infrastructure", "path": "/inference-infrastructure/" }, { "id": "mlops-lineage-and-agent-drift", "path": "/mlops-lineage-and-agent-drift/" } ] } ] }