Document identifier slippage in Trial 1

experiments/TRIAL_1.md

@@ -105,6 +105,7 @@ The following transitions required manual user intervention (the user prompting
 - **Reviewer Myopia**: The build reviewer successfully identified missing flags in the `Makefile` but initially ignored the presence of the hallucinated CMake file. Reviewers appear to be effective at checking "correctness" of changes but less effective at identifying "extraness" or "repository pollution" unless specifically tasked with "purity."
 - **The "Done" State Trap**: Agents frequently entered a "logical completion" state where they believed the task was over but failed to perform the "administrative completion" of notifying the parent. This indicates that the transition from *thinking* to *system-signaling* is the weakest link in the P2P choreography.
 - **Information Decay in Parallelism**: In a parallel spawn, context must be perfectly mirrored. Any discrepancy in the roster or instructions between concurrent agents can lead to deadlocks where one agent waits for a signal that another agent doesn't know it was supposed to send.
+- **Identifier Slippage (Sequence vs. Correlation)**: I failed to maintain the correlation between issue numbers and PR numbers when naming reviewers. Although the issues were #393 and #394, the resulting PRs were #395 and #396. I named the reviewers after the PR numbers (e.g., `reviewer-395-...`) rather than the issues they were resolving, which created a mental disconnect in the roster mapping and increased the cognitive load for tracking which agent was reviewing which fix.
 
 ## Conclusion
 The model is effective for multi-stage engineering tasks. However, notification protocols rely on agent autonomy which sometimes fails. Manual inspection of session files remains a critical fallback for the orchestrator.