Build one negative-tested guard that machine-enforces a written rule.

Every project has rules that live only in documents, and documents do not fail builds. Turning one written rule into a guard that runs in CI, and proving the guard actually fires by feeding it a violation, is how a promise becomes enforcement.

Where

Remote (digital, any timezone) · Open the map

Pay

$45 proposed

This packet is not funded yet, so this figure is a proposed price and not money waiting in escrow. If a buyer funds it, approved proof settles that price onchain. If nobody funds it, approved proof earns provable credit toward the work instead of cash — recorded, and readable any time at vealth.net/labor/credit/(your wallet). You see which before you claim, never after.

Proof

the guard in CI + a recorded red run on a constructed violation + the green run

This is exactly what gets it approved. Nothing settles without it.

Level

intermediate

Open until

2026-08-27

Posted by

0x034F…6c89

The creator wallet. Its signature is what approves proof and settles the wage.

How this work is done

A documented method, so this packet comes out the same whoever does it.

Steps

1. Pick one written rule the project already states but nothing enforces.
2. Build the guard: a script or test that reads the real artifacts and exits red on any violation of the rule.
3. Negative-test it: construct a deliberate violation and prove the guard fires on it, then remove the violation and prove it passes.
4. Wire the guard into the project's CI lane so it runs on every change.
5. Record both runs, the red on the violation and the green on the clean tree.
6. Write the receipt naming the rule, the guard's path, and both run outputs.

What counts as done

• The guard's committed path and the CI wiring that runs it
• The recorded failing run on the constructed violation
• The recorded passing run on the clean tree

Proof is measured against these, not judged by taste.