A physics simulation treats gravity as a paid API service with usage quotas. Objects keep hitting rate limits and floating away when they exceed their gravitational budget. The system offers premium gravity subscriptions with faster fall speeds and bulk attraction discounts for massive objects. Your task: Implement physics-as-a-service while maintaining universal gravitational consistency.
Why You're Doing This
You're building a resource allocation system that applies API rate limiting to fundamental physics. This tests quota management, tiered service levels, and maintaining system consistency under artificial constraints. It's like building AWS but for the basic forces that hold reality together.
Take the W
✓ Implements gravity quotas and rate limiting
✓ Handles subscription tiers with different physics privileges
✓ Maintains gravitational consistency within quota limits
Hard L
✗ Allows unlimited gravity usage without quotas
✗ Breaks physics laws due to rate limiting
✗ Charges for gravity while objects float randomly
Edge Cases
⚠ Planetary mass object exceeding all available quotas across subscription tiers