rungs command protection
Reviews rungs runs that execute registered gates or write module files, gates and records into a repository, and keeps doctor and the docume
Reviews rungs runs that execute registered gates or write module files, gates and records into a repository, and keeps doctor and the documented previews unreviewed.
command.rungs · v1.0.0 · Other extensions
- Protection rules
- 3
- Permission checks
- 3
- Mapped commands
- 3
Overview
What this coverage does
Reviews rungs runs that execute registered gates or write module files, gates and records into a repository, and keeps doctor and the documented previews unreviewed.
Key facts
- Catalog ID
command.rungs- 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
- 85c5e82
- Protection model
- 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.
Showing 3 of 3 operations
- Reviewed Guard intercepts the command for review before it runs.High
rungs add backlog
rungs module install
- Default floor
- Reviewed by default. Guard intercepts the command for review before it runs.
- Detector mode
- review
- What it matches
- Identifies `rungs add`, which writes module files, the gate registry, the install record and the rendered harness instruction files into the target repository. `--dry-run` reports the same plan and writes nothing, and is the only preview form.
- Documented safe variants
rungs add dry runskip this operation when they are the documented preview or help form.- Permission ID
- command.rungs.permission.add
- Reviewed Guard intercepts the command for review before it runs.High
rungs check
rungs gate execution
- Default floor
- Reviewed by default. Guard intercepts the command for review before it runs.
- Detector mode
- review
- What it matches
- Identifies `rungs check`, which executes every command gate registered in .ai/gates.toml — commands the repository owns, not rungs — and appends one line per gate to the local .ai/.gate-ledger.jsonl. check has no preview form; --dry-run is not read.
- Permission ID
- command.rungs.permission.check
- Reviewed Guard intercepts the command for review before it runs.High
rungs upgrade --apply
rungs module upgrade
- Default floor
- Reviewed by default. Guard intercepts the command for review before it runs.
- Detector mode
- review
- What it matches
- Identifies `rungs upgrade --apply`, which rewrites stale and missing module files, replaces gate registry blocks and updates the install record. Without --apply, upgrade only prints the plan; it never reads --dry-run, so `--apply --dry-run` still writes.
- Permission ID
- command.rungs.permission.upgrade
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.rungs
- Guard enforcement ID
- command.rungs
- Source path
- contributions/extensions/command.rungs.json
- Contribution digest
sha256…a9e165
Action classes
rungs gate execution commandrungs module install commandrungs module upgrade commandTechnical 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 rungs runs that execute registered gates or write module files, gates and records into a repository, and keeps doctor and the documented previews unreviewed. 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. 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: rungs add backlog (reviewed by default); rungs check (reviewed by default); rungs upgrade --apply (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.rungs 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.