Skip to content

abrahamferga/harness

v0.3.0MIT

Always-on control plane: what the Plenipo platform already gives you (so you never rebuild it), how any Plenipo product is run and proven, the workflow.json/settings.json pair, config + guardrail validation, and the conductor that drives the scout -> define -> shape -> deliver loops end to end. Keep enabled in every loop.

loop-discipline

The operating rules every loop in this marketplace runs under: the five-level verification ladder (deterministic → rule → field truth → model-as-judge → human), the six named terminal states, the five loop anti-patterns, and the design families that keep an unattended loop honest. Reach for it before claiming something is done, when a loop is spinning, or when deciding how far to verify. USE FOR: grading how strong your evidence actually is, choosing a stopping rule, naming why a loop ended, calling out a self-approving or runaway loop. DO NOT USE FOR: how to run or test a Plenipo product specifically (plenipo-runbook) or what the platform provides (plenipo-platform).

License
MIT
Read SKILL.md at the source

Pinned to revision a2ee8094fc23, so it is the text this page describes rather than whatever the author pushed since.

Files

Every link opens the file at its source, pinned to the revision this page describes.