G

GoLive deployment CLI protection

Reviews the GoLive plan executions that carry an explicit destructive or live confirmation flag. GoLive already refuses account writes witho

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.

command.golive · v1.0.0 · Other extensions

By Community contributorExternal · opt-inCommand coverage
Try this coverage Install GuardView exact source GoLive deployment CLI protection documentation Claim this coverage
0
Protection rules
3
Permission checks
3
Mapped commands
3

Overview

What this coverage does

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.

Key facts

Catalog ID
command.golive
Version
v1.0.0
Kind
Command coverage
Category
Other extensions
Protection rules
3
Permission checks
3
Mapped commands
3
Maintainer
Community contributor(community, provenance recorded)
Source commit
e2593fe
Protection model
External · opt-in
External · opt-in

External coverage. It must be enabled through Guard controls; this page does not activate it.

Stated limits

  • Coverage is limited to the reviewed operations and the surrounding Guard policy.
  • A maintainer profile is not a security certification or an official upstream endorsement.

Command mapping

Every command this extension recognizes, with the catalog default floor Guard applies before workspace policy. Search the table, then open an operation for safe variants and the permission ID.

3 operations · 3 reviewed by default These are catalog defaults, not your workspace policy.

3 operations3 reviewed
Default floor

Showing 3 of 3 operations

  • Reviewed Guard intercepts the command for review before it runs.Critical
    • golive apply --plan 8f3c1d2a4b5e --yes --confirm-destroy
    GoLive teardown execution
    Default floor
    Reviewed by default. Guard intercepts the command for review before it runs.
    Detector mode
    review
    What it matches
    Matches `golive apply` carrying --confirm-destroy: the deletion of resources GoLive recorded as its own, after an approved teardown plan.
    Documented safe variants
    GoLive help outputskip this operation when they are the documented preview or help form.
    Permission ID
    command.golive.permission.apply-confirm-destroy
  • Reviewed Guard intercepts the command for review before it runs.Critical
    • golive apply --plan 8f3c1d2a4b5e --yes --confirm-dns
    GoLive DNS change execution
    Default floor
    Reviewed by default. Guard intercepts the command for review before it runs.
    Detector mode
    review
    What it matches
    Matches `golive apply` carrying --confirm-dns: creating or changing DNS records at an automated provider.
    Documented safe variants
    GoLive help outputskip this operation when they are the documented preview or help form.
    Permission ID
    command.golive.permission.apply-confirm-dns
  • Reviewed Guard intercepts the command for review before it runs.High
    • golive apply --plan 8f3c1d2a4b5e --yes --confirm-live
    GoLive live write execution
    Default floor
    Reviewed by default. Guard intercepts the command for review before it runs.
    Detector mode
    review
    What it matches
    Matches `golive apply` carrying --confirm-live: live-mode payments, production data, a real account, or a project's first production deploy.
    Documented safe variants
    GoLive help outputskip this operation when they are the documented preview or help form.
    Permission ID
    command.golive.permission.apply-confirm-live

Tool state mapping

No per-tool overrides are declared. Command defaults above resolve through the workspace Guard policy unless a later policy layer changes them.

Runtime identity

Catalog ID
command.golive
Guard enforcement ID
command.golive
Source path
contributions/extensions/command.golive.json
Contribution digest
sha256…1a8610

Action classes

GoLive confirmed resource deletionGoLive confirmed live writeGoLive confirmed DNS change

Technical profile

No independent profile published

This extension has no current independent technical profile. Catalog facts and any legacy launch remain separate and are not presented as profile evidence.

FAQ

Frequently asked questions

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. The listing declares 3 rules and 3 permission checks. 3 operations · 3 reviewed by default. Coverage is limited to these reviewed operations and the surrounding Guard policy.

External · opt-in: External coverage. It must be enabled through Guard controls; this page does not activate it. Enabling state is always controlled through Guard policy, never from this directory.

This listing entered the catalog as a community contribution through a public pull request with recorded provenance, with public credit to @mikehasa, and 1 GitHub maintainer is recorded on the listing. Credit is attribution only. A verified publisher profile and the claim flow verify authority separately; neither is an upstream endorsement or a HOL safety certification.

No. Every listing documents source, activation model, maintainer identity, and stated limitations so you can evaluate coverage before enabling it. Review the stated limitations and the exact source tree before relying on any single control.

3 operations · 3 reviewed by default. Examples: golive apply --plan 8f3c1d2a4b5e --yes --confirm-destroy (reviewed by default); golive apply --plan 8f3c1d2a4b5e --yes --confirm-dns (reviewed by default); golive apply --plan 8f3c1d2a4b5e --yes --confirm-live (reviewed by default). These are catalog defaults, not your workspace policy.

External coverage. It must be enabled through Guard controls; this page does not activate it. Enablement is managed through your workspace's Guard policy and controls — never from this directory. Open the install guidance for the setup flow, then adjust the command coverage for command.golive in Guard's policy surface.

The matching action is stopped at Guard's pre-action boundary before it executes, and the decision is recorded with evidence your workspace can review. Exact behavior follows your Guard policy combined with this entry's 3 rules and 3 permission checks.

No. Guard is local-first: interception, decisions, and evidence stay on your machine unless your workspace explicitly configures cloud features. This page is documentation only — it never executes a command or changes protection state.

Guard runs locally alongside the major AI coding agents and MCP-capable harnesses, so this coverage applies wherever Guard intercepts actions. See the supported harness guides at https://hol.org/guard/harnesses for per-tool approval behavior and limitations.

Guard has a free local tier that includes command interception, evidence, and the policy controls this listing documents. Team plans add shared policy, review queues, and audit surfaces. Current plans: https://hol.org/guard/pricing

Open an issue or pull request against the hol-guard repository, where the canonical catalog lives: https://github.com/hashgraph-online/hol-guard Listings are corrected through the same public review process that adds them.

Yes. Community extensions are merged through public pull requests with recorded provenance, and you can claim the publisher page for a contribution you maintain through the Publisher Studio.

The command mapping table is the audit trail for covered commands and catalog default floors. Pair it with the reviewed rule and permission counts, the per-tool state mapping, and the exact source tree linked from View exact source at the reviewed commit. Guard records enforcement decisions with evidence locally, so what ships matches what you reviewed.