|
Some checks are pending
build-gate / build (push) Waiting to run
MEASURED: agents produced 21 report docs totalling 2,079 lines of prose and 27 scratch probe files against a handful of product commits. The cause is the spawn prompts, which is to say me: each carried ~15 environment rules, several cited lessons, a three-clause invariant, a mandatory screenshot read and a what-I-could-not-verify section. Per report that is 7-12 headings and 10-16 verification mentions. The prompt made PROVING the job and BUILDING the side effect. Two costs compounded. Every agent re-derived the same environment from scratch -- which port, is the tree settled, does stale SRI block the script, does this box have WebGL. And several spent that discovery budget, hit a build queue they could not control, and died on a session limit before committing; their work survived only because it was found untracked (one 511-line gate was a `git clean` away from being lost). This file pays that tax once. Spawn prompts can now be short: what to build, which files you own, and the one assertion that would falsify it. It also states the rule that was missing: ship a commit and PUSH, then write two sentences -- not the reverse. A long honest report attached to no commit is the failure mode. And it sizes verification to blast radius explicitly, because over-verifying is a real cost rather than a virtue. check:doc-scripts passes, so every command quoted here exists in package.json. |
||
|---|---|---|
| .. | ||
| src | ||
| dashboard.config.js | ||
| index.html | ||
| index.js | ||
| research-dashboard.meta.json | ||
| research-dashboard.vue | ||