Glossary
Shared definitions for how we talk about traction, scope, and measurement, aligned with the technical documentation and public roadmap language.
- Qualified usage
- Repeat workflow completion with retained artifact history and meaningful stage completion, not signups, page views, or waitlists alone. Used internally and in roadmap gates to measure real product use.
- Active developer (roadmap sense)
- A unique builder or operator who completes repeat workflow runs inside a defined time window, per the measurement framework we publish, not a vanity DAU count.
- Deployed dApp (counted honestly)
- A production or testnet application whose contract generation and deployment flow completed through the Hyperkit workflow with deployment records and artifacts retained in the system.
- High-fit ICP
- Interview and sales target profile: typically fast shipping cadence, multi-chain or chain-adjacent work, recurring audit/simulation/deploy coordination cost, and budget or tooling influence, as described in technical documentation.
- Falsification rule
- Internal benchmark: if structured interviews with high-fit users fail to confirm recurring pain or spend at the stated threshold, we treat the workflow hypothesis as falsified for that segment rather than overriding it with narrative.
- Current product truth vs maturity direction
- Present-tense scope is the AI-native workflow system on supported Studio paths. Longer-term direction is toward a verifiable application-factory scale, credible as roadmap, not claimed as fully shipped everywhere.