Built by its own night shift
Dagpilot is developed by Dagpilot. Every number below is a live aggregate from the production instance that builds this product — the same pipeline, the same gates, no demo data.
Live data, cached for five minutes. Last refreshed 2026-08-21 03:06 UTC. Aggregates only — no task content leaves the pipeline. Completed counts only tasks whose acceptance evidence passed; a completion the system cannot prove is not shown as proof. One of them, published by its owner, is opened below, item by item.
A run of our own, opened
the pair's dogfood run, 2026-08-10
Orch probe 2026-08-10 - clamp, aimed at the two verdict-path atoms of today
Verified per contract — 18/18 contract items
The contract, item by item — cycle 1 of 2
| # | Criterion | Kind | Verdict |
|---|---|---|---|
| CLAMP-01 | clamp.js must exist at the repository root as specified by the plan | deterministic · file_exists | PASS |
| CLAMP-02 | clamp.test.js must exist at the repository root as specified by the plan | deterministic · file_exists | PASS |
| CLAMP-03 | clamp.js must export a named function clamp with the exact parameters (value, min, max) | deterministic · file_contains | PASS |
| CLAMP-04 | clamp.js must not contain stub markers — the function must be a real implementation, not a placeholder | deterministic · file_not_contains | PASS |
| CLAMP-05 | clamp.js must use a finiteness check (Number.isFinite or isFinite) to implement the NaN guard for non-finite inputs | deterministic · file_contains | PASS |
| CLAMP-06 | Core correctness check: the function must implement all four rules with the guard clause ordered before the clamping arithmetic | semantic | PASS |
| CLAMP-07 | The test file must contain at least 4 test cases (using either test() or it() from node:test) to cover all four behavioral rules | deterministic · regex_match_count | PASS |
| CLAMP-08 | Test file must import from node:test to use the Node.js built-in test runner | deterministic · file_contains | PASS |
| CLAMP-09 | Test file must import clamp from the local module to actually test it | deterministic · file_contains | PASS |
| CLAMP-10 | Test file must import node:assert to make real assertions; without it tests pass vacuously with no verification | deterministic · file_contains | PASS |
| CLAMP-11 | Rule 1 requires dedicated test coverage: value below min must return min | semantic | PASS |
| CLAMP-12 | Rule 2 requires dedicated test coverage: value above max must return max | semantic | PASS |
| CLAMP-13 | Rule 3 requires dedicated test coverage: value in range must be returned unchanged | semantic | PASS |
| CLAMP-14 | Rule 4 covers all non-finite inputs; testing only one category (e.g. only NaN) could miss bugs with Infinity, strings, etc. | semantic | PASS |
| CLAMP-15 | package.json must declare type:module for .js files to use import/export ES module syntax under Node.js; without it node --test will throw ERR_REQUIRE_ESM or SyntaxError | deterministic · file_contains | PASS |
| CLAMP-16 | The plan explicitly forbids dependencies; package.json must not introduce any dependency blocks | deterministic · file_not_contains | PASS |
| CLAMP-17 | clamp.js must not import any external packages — only local relative imports are allowed, ensuring zero dependencies | deterministic · file_not_contains | PASS |
| CLAMP-18 | The plan requires the module to be readable to a newcomer with self-documenting names | semantic | PASS |
cycle 0: 17/18 — CLAMP-16 failed → a fix step → cycle 1: 18/18. The checks themselves cost $0.52, apart from the work.
Acceptance checks
1 check recorded, skipped: framework_detection.
Steps
- Implement clamp.js and clamp.test.js
- Fix: Contract item CLAMP-16 (file_not_contains) failed evaluation.
What changed
The patch lives in the person's repository — this server keeps the contract, the checks and the cost, not the diff. Files the contract looked at: clamp.js, clamp.test.js, package.json.
Read this run's full public report
Give Dag a task. He works the night shift.What counts as proof here
Most tools report that checks passed. We report what the checks were capable of seeing. Syntactic assertions confirm code is present; semantic checks read the change and judge whether it does what the task meant. That distinction is on this page because it is the honest one — a bare pass count can be inflated by shallow checks.
Every task runs the same gauntlet: decompose into a dependency graph, execute in isolated worktrees, verify and heal each subtask, compile a machine-checkable acceptance contract, run end-to-end acceptance, then a final whole-task verification with a minimum-score gate. Red never lands.