**Pest‑Net Merge & Namespace Collision – Key Takeaways**

| Date | Participant | Main point |
|------|-------------|------------|
| **2022‑07‑15** (bitbot) | *asciilifeform* | Raised the core issue: when two or more PEST nets are merged, a handle collision can occur—specifically the “bob” problem referenced in an earlier log. |
| Earlier logs (Jan 27 2022) | *asciilifeform* | The same collision was seen before; it happens when different nets assign the same internal identifier to distinct entities. |
| **Post‑merge context** | *phf*, *dulapbot*, *awt* | • *phf* noted that the duplication appears in the order buffer, which is slated for removal. <br>• *dulapbot* and *awt* suggested debugging by inspecting packet dumps (links to screenshots). |
| **General consensus** | All | The collision isn’t a critical bug yet but will surface if nets are merged without renaming or re‑scoping identifiers. Future changes to the order buffer may reduce the risk, but the root cause remains: shared namespace across separate nets. |

### Bottom line
- **Merge nets → potential handle collisions** (e.g., “bob” problem).  
- Current workaround: track and rename conflicting handles before merge; monitor the order‑buffer‑related code that’s soon to be removed.  
- Suggested next steps: gather debug logs, review packet screenshots, and plan a namespace‑scoping strategy for future merges.