Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Pre-deployment governance for release and infrastructure rollout requests. Use when an agent or workflow proposes shipping code/config/infrastructure changes...
Pre-deployment governance for release and infrastructure rollout requests. Use when an agent or workflow proposes shipping code/config/infrastructure changes...
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Then review README.md for any prerequisites, environment setup, or post-install checks. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Then review README.md for any prerequisites, environment setup, or post-install checks. Summarize what changed and any follow-up checks I should run.
consensus-deployment-guard is the final safety gate before deployment execution.
validates deployment requests against a strict JSON schema (reject unknown fields) evaluates hard-block and rewrite policy flags for release risk patterns runs deterministic persona-weighted voting (or aggregates external votes) returns one of: ALLOW | BLOCK | REQUIRE_REWRITE writes decision artifacts for replay/audit
Hard-block examples: required tests not passing CI status failed rollback artifact missing when required incompatible schema migration error budget already breached Rewrite examples: production rollout not using canary when policy requires it initial rollout percentage above policy limit production deploy missing explicit human confirmation gate CI still pending schema compatibility unknown
runtime binaries: node, tsx network behavior: none in guard decision logic environment config read by this package: CONSENSUS_STATE_FILE, CONSENSUS_STATE_ROOT filesystem writes: consensus board/state artifacts under configured state path
invoke(input, opts?) -> Promise<OutputJson | ErrorJson> Modes: mode="persona" (default): use local deterministic persona defaults for internal voting mode="external_agent": consume external_votes[], aggregate deterministically, and enforce policy
npm i consensus-deployment-guard
node --import tsx run.js --input ./examples/input.json
npm test Coverage includes schema rejection, hard-block paths, rewrite paths, allow paths, idempotent retries, and external-agent aggregation behavior. See also: SECURITY-ASSURANCE.md for threat model, runtime boundaries, and deployment hardening guidance.
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Largest current source with strong distribution and engagement signals.