2.0 KiB
2.0 KiB
Role Misdirection Recovery
Use this procedure when a prompt intended for one role is sent to another Cursor window or agent role.
Immediate Stop
- Stop the receiving role from acting outside its assigned scope.
- Do not reinterpret the prompt for the current role.
- Do not run execution, approval, service, network, Nginx, Docker, firewall, or token-handling commands.
- Do not continue mutation-stage work from any role until ORCHESTRATOR reviews the incident.
Audit
- Identify the intended role, actual receiving role, workspace path, and time window.
- Review modified files and recent evidence.
- Check whether any secrets were written to files, logs, commits, or chat.
- Check whether any PC/VPS commands, approvals, service changes, Nginx/Docker changes, website changes, or firewall/network changes were executed.
- Check
sync-state/heartbeat-*.jsonandsync-state/error-*.mdfor sync health.
Correction
- CORRECTION records findings in
handoff/CORRECTION.mdand blocks dependent tasks if needed. - ORCHESTRATOR reviews cross-role edits and either adopts or corrects them.
USER_STATUS.mdmust show a paused state and a single safe next action.- Executor handoffs must explicitly say whether their tasks are blocked or allowed.
- Task files must not be left in
readywhen role ownership or authorization is uncertain.
Resume Criteria
Work may resume only when:
- ORCHESTRATOR records the corrected active state.
- Any affected task status is reconciled.
- No secret leak or unsafe mutation remains unresolved.
- Sync health is not blocked.
- Any execution or authorization work receives fresh explicit user authorization targeted to the correct role and workspace.
Prevention Checklist
- Each Cursor window starts with a visible role marker.
- Before sending an execution prompt, the user and agent verify role, workspace, and handoff.
- Authorization prompts echo the target role and exact allowed action.
- Verifier roles refuse executor/orchestrator work.
- Execution agents refuse work outside their assigned task file.