03 / DENGEL GUARD
A new commit needs new proof.
The agent that wrote the code and the verifier have separate jobs. Guard gives reviewers the checks for the exact commit and holds a proposal if the candidate or its base changes.
Candidate changed
HEAD b72c9de- Commit tested
a91f8c2- New candidate
b72c9de- Checks for the new commit
- Unverified
- Landing
- On hold
01 HOW GUARD WORKS
From candidate to signed receipt.
Review a managed Git proposal in the web panel, including work pushed from an agent’s checkout. Managed Build has its own independent verification step before delivery.
- 01 / VERIFY
Check the exact code.
For a managed Build, a separate verifier reconstructs the candidate from its base and patch and runs the required checks. The checks yield a verified, failed, or inconclusive verdict. Missing required evidence leaves the verdict inconclusive.
- 02 / DECIDE
Apply delivery policy.
For a managed Git proposal, the change page shows its stated purpose, affected files, and check results tied to the head commit. Dengel checks that both the candidate and main still match before offering the merge.
- 03 / LAND
Let a person say yes.
An authorized reviewer confirms the exact proposal in the panel. On successful delivery, Dengel’s signed receipt records the resulting commit and tree.
02 WHY GUARD
Checks should follow the change.
An agent may fix one check and push again while a reviewer is reading the proposal. The new head can invalidate the earlier evidence even if the branch name is the same. Guard ties the evidence to a commit so the reviewer can tell which version was tested.
In the panel, a reviewer can see what changed, which checks ran, and who must approve. If main moved, the proposal gives them a concrete next step: rebase and propose again.
Verified. Then approved.
Verification answers whether the candidate met its required checks.
Delivery answers whether that candidate may update the current target with the right human approval.
NEXT IN THE FACTORY
