Engagement Principles
PhysXQ is a tool, not a slot machine. These are the lines we won't cross — written down so you can hold us to them.
Compute is the only resource you ever buy.
No abstract currencies, no gem packs, no "credits" that obscure real cost. Population size, cloud-burst minutes, parallel runs. If you can't price a feature in seconds-of-GPU, we don't sell it.
No artificial scarcity.
No "only 3 seats left at this tier." No countdown timers we control. No fake waitlists. If something is limited, it's because it's actually limited.
No FOMO mechanics.
No daily-login streaks that punish absence. No expiring rewards. No "miss this and it's gone forever." Your work waits for you.
No variable-ratio reward schedules.
Every progress bar shows real progress. Every fitness graph shows real fitness. No randomized dopamine drips, no surprise loot, no pulled-lever mechanics borrowed from gambling.
Engagement comes from work, not pressure.
Real discovery moments. Real progress visualization. AI commentary that explains what's happening, not what to feel. Achievements earned through actual work, never through purchasable shortcuts.
Inventor's Forge will never optimize for planned obsolescence.
The Forge improves your inventions on three axes: performance, application diversity, cost-down engineering. It will refuse to suggest changes that exist solely to shorten product lifespan, sabotage user repair, or lock customers into recurring purchases. This is a hard architectural boundary, not a guideline.
Social proof, not social pressure.
The creator economy lets you share what you've built. It will not show you what your friends are doing to make you feel behind. No leaderboards designed to demoralize. No "people like you also bought."
Your data is yours.
Inventor's Forge submissions are private by default and stay that way. No model training on your IP without explicit, granular consent. Export everything, anytime, in standard formats.
If we ever cross one of these lines, tell us at [email protected]. We will respond, publicly. We'll publish a quarterly report listing any near-misses and what we changed.