diff --git a/doc/IDEAS.md b/doc/IDEAS.md
index 86b4da9..758782d 100644
--- a/doc/IDEAS.md
+++ b/doc/IDEAS.md
@@ -96,8 +96,9 @@ The script is the coordinator; agents have no knowledge of each other. Informati
 
 Since agents have access to `execute_code`, a session can write and execute a workflow script without any human involvement. Given a task and knowledge of the filesystem layout, an agent can decompose the work, spawn sessions, write the coordination script, and run it — all in a single turn. The README you are reading is essentially its system prompt. Conductor functionality, for free.
 
+### Next Steps & Research (derived from [TRIAL_1](../experiments/TRIAL_1.md))
 
-- **Status Polling Mechanism**: Implement a mandatory `status` file for all agents that the orchestrator can poll. This would prevent having to tail `chat` files to estimate if an agent is stuck or done (see [TRIAL_1.md](../experiments/TRIAL_1.md)).
+- **Status Polling Mechanism**: Implement a mandatory `status` file for all agents that the orchestrator can poll. This would prevent having to tail `chat` files to estimate if an agent is stuck or done.
 - **Verification of Premises**: Require agents to perform an "Environment Check" before acting on prompts to prevent fulfillment of hallucinated requirements (e.g., CMake in a Makefile-only project).
 - **Administrative Handshake**: Force a "Sync" step at the end of every subagent task where they must receive an ACK from the parent before idling, reducing the "Done State Trap."
 - **Purity Reviewers**: Introduce specialized reviewer scripts that look for "extraness" (extra files, unrelated changes, or phantom technical debt) rather than just functional correctness.