---
name: fox2-tech-route-preflight
description: "Identify and verify applicable safety/host prerequisites for chosen execution; Bridge runtime remains technical enforcer."
---

# fox2-tech-route-preflight

**FOX2 Layer 3 — Technical and safety methods — Agile Lite 0.5.0**

## Activate when
A selected action requires material host, credential, writer, Bridge/Dispatch or irreversible-operation preconditions.

## Input
Already selected route and actual installed machine/host/permission evidence.

## Work to perform
1. For ordinary authorized reversible native DEV, check scope, writer isolation and relevant tests; NO universal R0–R7, documented PreExec receipt or Bridge admission.
2. For actual Bridge use the installed host's validator/PreExec and Schema: exact task/prompt/source SHA, machine Dictionary/Policy pin, allowed paths, route/CLI model effort, permission grant, owned worktree/one writer, unused ledger attempt and required decision receipt. This Skill describes checks and interprets their evidence; only host validator may attest a technical PASS.
3. Technical Dispatch Schema v3, `decision_receipt`, `max_runs=1`, transport control-branch publication and agent launch are responsibilities of the installed Bridge/authorized execution operator, not Prompt Builder. Do not manually set `policy_check`, `material_capability_check`, etc. to PASS.
4. Preserve protected operation restrictions (no silent main/merge, destructive, provider, broker/LIVE changes) and fail closed on unknown capability or consumed attempts. Owner internal waiver is authority, never invented evidence.
5. Return `PROCEED_FOR_THIS_ACTION` or `BLOCKED` with the **specific** failed prerequisite, continue unrelated safe work.

## Output
One scoped readiness verdict bound to observed host evidence, with exact STOP when necessary.

## Responsibility boundary
Owns technical gate applicability and evidence interpretation. Does NOT prioritize task, choose Agent, create prompt, synthesize PASS, or perform Bridge dispatch/execution.

## Common rules
One logical Kanban task; only material checks for selected action. Ordinary native DEV has no mandatory Bridge/PreExec/R0–R7 paperwork. For actual Bridge execution the installed Bridge enforces its own machine protocol and no-replay; never fabricate PASS, permissions or host actions. CHAT owns result acceptance; no broker/LIVE, protected branch or irreversible side effects without real authority.