Firestore Data Model
Firestore is the control plane for users, jobs, entitlements, application
Job Document
Each processing request has one jobs/ document. App uploads,
Glossary
Product and tennis
Security Model
AceSense uses Firebase Authentication for identity, Security Rules for direct
Observability
AceSense's non-GPU control plane is observed through Cloud Logging, Firebase
Testing Strategy
Tests live with each independently deployable repository. There is no single
Cost & Capacity
This page documents the cost controls visible in the non-GPU repositories. It
Analysis JSON Schema
This schema is owned by the excluded GPU-backend contract and was not
Doc Components
Reusable React components available in every Markdown page.
Agent API & MCP
Pay-per-minute REST and MCP endpoints that let AI agents submit tennis videos to the AceSense GPU pipeline and retrieve coaching reports.
Analytics
The repository audit found PostHog wired into three web surfaces: landing,
SEO & Discovery
What's wired so AceSense shows up in Google, Perplexity, ChatGPT, and Claude search — and how to keep it that way.