Rules clarification: are operations on the NumPy-backed arrays reachable through flopscope.numpy inside the intended accounting boundary?

Want to +1 this as clarity here would be appreciated. At the moment, the public leaderboard appears to be significantly determined by who can build the fastest native backend for uninstrumented, residual billed operations.

EDIT: Given the impending Phase 1 deadline, this ambiguity has immediate competitive consequences. Stopping work on native optimization risks falling further behind if the accounting remains unchanged, while continuing risks substantial wasted effort if the approach is later prohibited or repriced.

3 Likes