request-router

To validate project requests against blueprints, use a gatekeeper mechanism that checks incoming requests against defined vision goals and hard constraints before authorizing work order creation. This prevents project drift and resource waste.

Work order orchestration within an autonomous agent hierarchy evaluates approved requests, transforms them into standardized actionable work orders with clear acceptance criteria, and manages their lifecycle through strict dependency checking and cascade processing.

Yes, you need access to project-specific blueprint files, status logs, and the work order index. These resources are required to maintain system integrity, enforce strict validation, and ensure alignment during work order lifecycle management.

To handle vision pivots and update existing work orders automatically, implement cascade management based on L2 instructions. This process automatically updates, blocks, or archives existing work orders to maintain alignment with the new vision.

The best way to prevent project drift when triaging incoming requests is to enforce a mandatory gatekeeper that evaluates all incoming tasks against the project's vision, constraints, and dependencies before any work is authorized.