ACI-062: Evidence Names a Moment

Thesis

Single-writer covers files, not the runtime state a build or test touches, and a test run on a shared tree reads every node's uncommitted work, so a green or a red names a moment, not a commit. Partition shared runtime resources or serialise the runner in announced windows, pin each result to a commit and say which tree you read, and attribute a red to a peer only from a clone.

Story

Laksa's nodes ran their test suites in one working tree. On 31 August 2026 the DevX node replaced a fixed temp path that every run wiped with a per-run root, and the next pair of concurrent suites still went red, 21 failures and 1 (Laksa@239a580ee, 2026-08-31). It withdrew its own announcement that suites no longer needed announcing, because "the tmp fix landed" reads as "concurrent suites are fine now" and that is false. Classified by their own error lines, the 22 failure blocks came from two channels: 15 from the shared build directory, and 7 from the shared test database, where the second suite's setup migrated the database the first was mid-statement in (Laksa@b31e82334, 2026-08-31). The run that started second did the damage and the run that started first failed, so neither node could see the collision in its own result, which is why a suite is announced before it starts.