pome223/missionos

pome223/missionos

Agent

This maintainer fixture freezes the PX4 Action Feasibility behavior that must survive the MissionOS Core extraction tracked by internal Epic #99.

pome223/missionos

Agent

This contract describes the deterministic multi-hazard verification boundary used by PX4 recovery proposals. It is a maintainer implementation contract, not a claim that the current simulation models are physically calibrated.

pome223/missionos

Agent

This contract routes an explicit failed verifier verdict to one new approval-pending Recovery proposal. It does not retry the failed dispatch, reuse the prior approval, or execute the proposed recovery.

pome223/missionos

Agent

This contract defines how MissionOS may use ADK v2 RequestInput to pause and resume orchestration around an existing Form 2A human approval. ADK transports the response; it does not create, infer, consume, or broaden approval.

pome223/missionos

Agent

This contract covers the ControlLoop used by the legacy-agent Gateway profile. It does not describe the separate MissionOS conversation proposal, canonical HITL, guarded-execution, or bounded-recovery workflows.

pome223/missionos

Agent

This contract permits the canonical approval HITL graph to invoke an existing MissionOS execution boundary once. ADK orders the nodes; MissionOS still owns approval validation, deterministic rules, dispatch authority, idempotency, executor invocation, receipts, observations, verification, and progress.

pome223/missionos

Agent

This contract covers the explicit legacyagent Gateway profile. It does not change the production MissionOS conversation proposal graph or give ADK any MissionOS approval, dispatch, execution, or verifier authority.

pome223/missionos

Agent

This contract makes the ADK v2 conversation graph the default primary proposal generator. It does not move MissionOS approval, dispatch, execution, receipt, verifier, or recovery authority into ADK.

pome223/missionos

Agent

This inventory defines the completion boundary for the MissionOS ADK v2 migration. A Runner is an ADK application/session entrypoint; it is not by itself evidence of legacy orchestration.

pome223/missionos

Agent

This contract defines the persistence evidence required before MissionOS can enable ADK v2 workflow restart or resume. Redis stores ADK orchestration state; it does not become MissionOS approval, dispatch, execution, verifier, or audit truth.

pome223/missionos

Agent

This document describes the current MissionOS agent wiring. It is intentionally more precise than the human-facing concept docs.

pome223/missionos

Agent

MissionOS should make evidence easy to audit. Each artifact category below names its authoritative schema and the code that owns it. Prefer these exact shapes over ad hoc dicts.

pome223/missionos

Agent

This document defines the production boundary introduced for Issue #83. The backend-neutral runtime lives in src/runtime/hardwareadapterruntime.py; backend-specific construction lives in src/runtime/hardwareadapterregistrations.py.

pome223/missionos

Agent

A design proposal for a test collection that checks whether a PX4 robotics bench setup follows a shared hardware-control contract. PX4 is flight-control software, and a conformance corpus is a set of cases used to check expected behavior.

pome223/missionos

Agent

Use explicit claim language. Do not collapse separate facts. This is the field dictionary for the claim boundary; the enforcement code is src/runtime/runtimeclaimevidence.py and src/runtime/hardwareadaptercontract.py.

pome223/missionos

Agent

This repository remains private until the extracted MissionOS CLI is verified to behave like the current boiled-claw CLI for the supported MissionOS operator workflow.

pome223/missionos

Agent

MissionOS code should preserve these boundaries.

pome223/missionos

Agent

This procedure resumes the pinned Cosmos Policy LIBERO experiment only after a human has accepted the NVIDIA model terms and the approved Hugging Face token has been stored in Google Cloud Secret Manager. Never put an access token in a command, local credential store, log, issue, checkpoint manifest, VM metadata, or…

pome223/missionos

Agent

This contract defines the MissionOS dispatchref baseline that must be used before an ADK workflow can approach an external execution boundary. It does not give ADK, an LLM, or a completed graph node approval or dispatch authority.

pome223/missionos

Agent

Runtime changes require runtime verification. Unit tests are useful, but they do not replace a smoke test against the affected production boundary.

pome223/missionos

Agent

MissionOS has two explicit production-capable Gateway profiles. They are separate route surfaces, not middleware visibility modes.

pome223/missionos

Agent

Use this diagnostic after policy-input delivery and native model-forward evidence exist, but before interpreting a negative Repair cohort as a model capability result. The probe asks whether changing only the task instruction changes the native GR00T prediction at one frozen observation.

pome223/missionos

Agent

This record publishes a bounded negative measurement from the governed same-world Repair path. The post-observation-amended cohort completed at 0/5 loops: five naturally occurring asymmetric partial failures were each given one approved Repair attempt, with no automatic retry, and none improved the target predicate.

pome223/missionos

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.