Platform Dependencies
Features this venture requires from the platform.
Platform Dependencies
| Feature ID | Feature | Why | Type |
|---|---|---|---|
| AUTH-001 | User registration | Practitioner accounts — validated, not anonymous | Service |
| USER-001 | User profiles | Practice history, validation status, learning arc | Service |
| AI-002 | Conversational AI | Practice recommendation, pattern recognition from outcomes | Service |
| NOTE-001 | Email notifications | Practice reminders and streak maintenance | Service |
| MKTG-001 | Marketing automation | Practitioner acquisition and reactivation sequences | Service |
Context
- Platform feature matrix — Full capability register
- Agency capabilities — The capability loops Better Practice trains
- Navigation first principles — How good judgement compounds
- Journey priorities — Practice alignment with what actually matters
- AI orchestration — Personalized practice recommendation engine
- Scoreboard reality — Validation that practice is producing real outcomes
- First principles — Unit economics of validated practice at scale
- Critical path — What must be true before practices compound
- Marketing automation — Practitioner acquisition and reactivation
- Business artifacts — The deliverable types that prove practice impact
- Standards — Shared naming that makes practices portable across contexts
- Agency — The capability Better Practice compounds
- Science principles — Validation methodology behind evidence-based practice
- Software protocols — The agent protocol layer practice recommendations run on
- Platform — The practice delivery layer
- Behavioural biases — What blocks practice adoption and how to design around it
- Consulting AI model — How AI-validated practice becomes a business model
- Verifiable intent — How practice completion can be verified and rewarded
- Matrix thinking — Practice maps across capability dimensions and time horizons
- Journey priorities — Which practices compound fastest toward the north star
- Systems thinking — The reasoning framework behind evidence-based practice design
- Smart contracts — The protocol layer enabling verified practice completion
- Purpose — Why this venture exists and what validated practice must deliver
- Community — The practitioner network that validates practice impact
- Collective agency — How validated practice compounds at group level
- Tokenization — How validated practice completions become credentialed proof
Questions
What is the minimum validation threshold that distinguishes a Better Practice recommendation from generic self-help advice?
- Which dependency — USER-001 (practice history) or AI-002 (pattern recognition) — is more critical to practice quality?
- If the AI recommendation engine were removed, would practitioners still pay for the community validation alone?
- At what validation depth does Better Practice become a credential rather than a product?