lo-opportunity-radar

To detect token waste during code review, run a structured token-savings pass that flags unnecessary cost drivers like repeated large reads, oversized payloads, noisy summaries, and overly broad searches, yielding compact, actionable findings for reducing operational costs.

A deterministic service opportunity in automation workflows is stable-input, ordered-output work that should be implemented as a deterministic service rather than handled manually, ensuring repeatable processes are routed for automated execution.

You route advisory findings to a backlog idempotently by applying surface-eligibility and routing passes to direct material improvements via the router, ensuring downstream advisory routing promotes them into work items without duplication.

Yes, advisory routing works with implementation proposals and post-implementation verification by applying structured passes during proposal review, advisory authoring, bridge verdicts, and session wrap-up to review artifacts for defects and inefficiencies.

The best way to identify candidates for deterministic services during artifact review is to perform a dedicated deterministic-service pass that checks for stable-input/ordered-output work and recommends the right operational surface like hooks, benchmark checks, or scripts for automation.

You should not trade away code quality for token savings when a defect pass identifies correctness issues, ensuring you always check for correctness without trading away quality for efficiency before optimizing token costs.