Guided first use
Try GoLive deployment CLI protection
Reviews the GoLive plan executions that carry an explicit destructive or live confirmation flag. GoLive already refuses account writes witho Follow the three steps below with your own setup — nothing on this page runs on your machine or changes a policy.
Step 1 · Check fit
What this coverage governs
Reviews the GoLive plan executions that carry an explicit destructive or live confirmation flag. GoLive already refuses account writes without an approved plan id, recomputes that plan's identity before running, and deletes only resources it recorded as its own; the confirmation flags themselves are passed by the caller on the human's behalf, so `golive apply` with --confirm-destroy, --confirm-live or --confirm-dns is where an independent review adds something. The read-only surface (`golive help`, `version`, `update-check`, `detect`, `menu`, `doctor`, `plan`, `teardown`, `verify`, `status`, `handoff`) is outside these rules: `teardown` is the inverse plan and deletes nothing, and `plan` is what prints the plan id a human approves.
External — off until you opt in
This coverage stays off until you explicitly enable it from your Guard workspace controls. Reading this page never changes your policy; activation happens in Guard itself.
Harness support
No harness compatibility profile is published yet. Check the Guard harness guide for what your setup uses.
Are you the publisher? Complete this section in your Studio — until then this stays unknown for readers instead of being guessed.
Catalog version 1.0.0 · source snapshot 54b61c819e
Step 2 · Set up
Install and activate
No reviewed setup steps are published for this coverage yet. Install Guard itself, then return here after the publisher publishes a guide — or ask for one. Are you the publisher? Complete this section in your Studio.
New to Guard? Start with Install Guard. Already installed? Skip install — this coverage stays off until you enable it from your workspace controls.
Activation happens in your Guard workspace. This page links to it; it never enables the coverage for you.
Missing the setup information you need? Request setup documentation — the publisher reviews requests before anything is published here.
Step 3 · Verify the result
Run a safe test and compare
Safe fixture inputs
No published safe fixture yet. Try the coverage against a harmless command of your own — not production traffic.
Are you the publisher? Complete this section in your Studio — until then this stays unknown for readers instead of being guessed.
Expected outcome
No expected outcome published yet. Guard surfaces what it matched — the rule and its decision — in its own activity view; compare that with this coverage’s stated rules to inspect the actual decision.
Are you the publisher? Complete this section in your Studio — until then this stays unknown for readers instead of being guessed.
Outcome reporting
This coverage has no claimed publisher page yet, so outcome reports are not collected. You can still verify the result locally against the expected outcome above.