tia-handoff

tia-handoff — prepare the gate, let a human act (class GATE)

The harness is an assistant up to the gate, never an autonomous commissioner. Anything that touches the physical controller, the network, secrets, or safety stops here: this skill assembles the approval envelope (requires_human_action) — what can be done, what the human must do, the plan + hash, and the exact resume call — and then stops.

Errors and reporting

• First call tia_ping: continue only if it reports reachable:true and activated:true. activated:null with a busy detail means a job is still running: poll tia_job_status with the jobId you hold, or wait and ping again. Otherwise stop, quote its detail and hint verbatim and say that nothing was changed (prerequisites: tia_guide {"topic":"gotchas"}).
• If no tia_* tool is available, the tia MCP is not connected: say so and stop. Never continue from memory and never work around it with hand-made HTTP calls (they bypass the MCP's gate checks).
• On a tool error (isError:true), quote its error and kind verbatim, relay its hint, and state what was done and what was not. Apply only the remedy the hint or this skill names, at most once; otherwise stop and ask.
• Never report success after an error, never retry a refused call with changed arguments, and never cross a human gate: relay a requires_human_action answer verbatim and wait for the human.
• status:"running" or kind:"busy" is not a failure: poll tia_job_status {jobId}. After a timeout, check the state before repeating anything.

When to use

• After tia-verify is clean and the user wants to download / deploy / go online / scan / commission.
• Whenever a step needs a secret (master secret, UMAC, an upload / block / certificate password), a password-policy decision, or touches F (safety).

The gates (and the tool that fronts each)