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.

platform-protocol

The contract between products and the Plenipo platform when many products are being built at once: the escalation ladder a product climbs before asking for a platform change, the shape of a platform request, what the platform steward guarantees back, and the rule that filing a request never blocks the product. Reach for it whenever a product needs something the platform does not yet do. USE FOR: deciding whether a gap is yours or the platform's, understanding what a triage verdict means, knowing why a shim is tagged. DO NOT USE FOR: actually filing the request (/deliver:request-platform-change) or triaging the queue (/steward:triage-requests).

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.