AceSense Documentation

Private engineering and operations documentation for the AceSense platform.

Start here

• What is true right now: Current State — what is deployed, what is blocked, what each sport actually measures. Start here before trusting anything else on this site.
• New engineer: 5-minute quickstart
• System map: C4 model
• Deploying: deployment guide
• Incident: debugging quickstart
• API integration: API reference

Repository map

Repository	Responsibility
acesense-frontend	Flutter app for web and native platforms
acesense-auth-function	Cloud Functions, REST API, MCP, jobs, billing, admin callables
acesense-api-hosting	Firebase Hosting rewrites for api.acesense.io
acesense-admin	Internal operations UI
acesense-landing	Public marketing and discovery surface
acesense-docs	This private Docusaurus site and its auth gate
acesense-launchpad	Private fundraising/strategy tool and its auth gate
acesense-annotate	Local annotation tool
acesense-brand	Shared visual identity and tokens
acesense-gpu-backend	GPU analysis runtime; excluded from this audit

Do not put commit hashes or mutable deployment versions in this landing page; they become wrong without helping a reader find the source of truth.

Platform invariants

• Firebase project: acesense-prod.
• Cloud Functions region: europe-west1.
• Owners cannot create or forge job lifecycle fields directly.
• Upload authorization is server-side and checks consent, entitlement, and quota.
• One shipped client upload creates one job; physical client chunking is deferred.
• Docs and launchpad require an admin session before their bundles are served.
• GPU internals belong to the GPU repository and its explicitly scoped docs.

Keeping docs honest

last_verified means a page was checked against the relevant source/config, not merely edited. Run:

cd acesense-docs
node scripts/check-links.mjs --strict
node scripts/check-freshness.mjs
cd website && pnpm test

See Contributing before publishing changes.