Agent
This is a separately preregistered diagnostic follow-up to the completed one-chunk semantic-direction observation. It does not revise or reinterpret that result. It asks whether a longer, three-chunk closed-loop trajectory shows local motion aligned with the failed target named by the instruction.
Agent
Before another L4 session, MissionOS must establish that both the task-specific LeRobot checkpoint and its gated Cosmos processor dependency are accessible. This is an admission check only. It creates no approval, dispatch authority, execution evidence, or Semantic Repair claim.
Agent
This control asks whether one restored partial-success simulator state was recoverable through the same 7D LIBERO action interface and within the same 720-action ceiling used by the GR00T diagnostic trials. It separates a policy failure from the alternative explanation that the saved state, predicate, action…
Agent
The generic registry, Gateway lifecycle, shared conformance suite, and Core verifier are specified in docs/agents/backend-neutral-adapter-runtime.md.
Agent
This guide is the maintainer checklist for adding a partner-owned hardware adapter to MissionOS. It is not a field-test authorization and not a claim that MissionOS can safely operate a partner robot or drone.
Agent
This repository still contains a legacy internal codename in code identifiers, runtime strings, service names, and simulator integration points. The remaining legacy strings are not credentials or private evidence, but they should be renamed deliberately so the public codebase presents one coherent MissionOS identity.
Agent
This document records a second-object diagnostic Repair fixture for the public Cosmos Policy and VLA-0 comparison. It is a simulator experiment contract, not evidence of a live MissionOS Repair loop or physical execution.
Agent
This boundary allows a deterministic skill registry to execute a Repair without being represented as model inference. It preserves the authority sequence.
Agent
This diagnostic path creates an explicit failed simulator state before the normal MissionOS Repair authority path begins. It exists to avoid treating a millimetre-scale predicate-boundary miss as a representative VLA recovery problem.
Agent
MissionOS is designed around an LLM-in-the-loop chat path. LLM-backed ADK paths default to hosted DeepSeek V4. Gemini remains a supported hosted path. Ollama/Gemma is the local no-spend path, but it is slower and role-dependent.
Agent
This is the merge gate for pull requests that change missionos chat, the Gateway, planner or recovery agents, task state, runtime adapters, approval or dispatch, operate, watch, map, or their evidence contracts.
Agent
This note resolves the publication-safe part of public issue #66. It compares a blocked Recovery candidate fixture with a verified reference fixture through the same production Core adapter.
Agent
This contract adds an optional Nvblox-derived perception evidence surface for MissionOS obstacle-aware claims. It does not make Nvblox an approval authority, dispatch authority, executor, verifier, physical runtime, or delivery-completion source.
Agent
This page documents the opt-in Nova Carter simulator profile for MissionOS. It is an agent-facing runtime contract, not a public proof report.
Agent
This contract binds one live VLM observation to one exact camera frame and one independently observed LaserScan candidate. It is evidence for recovery deliberation. It does not approve, dispatch, execute, verify mission completion, or create physical authority.
Agent
Treat each migration into this repository as a publication event.
Agent
This document describes the maintained horizontal-route runtime boundary and the contracts that must survive future refactors.
Agent
A guide for moving a PX4/Gazebo software-in-the-loop drone runtime toward real hardware. PX4 is flight-control software, Gazebo is a robot simulator, and software-in-the-loop means testing in simulation.
Agent
Agent-facing reference for the recovery-delegation surfaces: two-phase reflex/deliberation split, perception claims, shadow measurement, and action promotion. Read docs/concepts/recovery-delegation.md first for the plain-language model; this page is the field/env/module map.
Agent
This contract implements the Issue #36 separation without moving hosted-model output into the authority path.
Agent
Agent "repair-diagnostic-contract" from pome223/missionos, covering repair diagnostic contract, purpose, required axes, failure classification and authority and claim boundary.
Agent
Agent "replay-bundle-contract" from pome223/missionos, covering anonymized recovery replay bundle contract, purpose, production sources, publication boundary and per-epoch chain.
Agent
A Japanese-language snapshot of a MissionOS repository's status as of July 25, 2026, including its public version, branch position, supported systems, and evidence limits. MissionOS is a control system for coordinating AI-driven operations.
Agent
This page documents the TurtleBot3 simulator path for the ROS2/Nav2 hardware adapter work. It exists because the TurtleBot4/Create3 stack reached controller and dock-specific blockers before proving meaningful /odom motion. TurtleBot3 is the lower-friction simulator target for getting one end-to-end MissionOS -> Nav2…