Documentation Coverage
Use this release inventory to confirm that every shipped product domain has an owning guide and code-backed evidence.
On this page
Current coverage
13 documented, 0 partial, and 0 undocumented product domains.
| Product domain | Status | Primary guides | Source roots |
|---|---|---|---|
| Account and authentication | Documented | /docs/auth-and-account, /docs/app-auth | src/features/account, src/lib/auth |
| Analytics | Documented | /docs/analytics, /docs/app-dashboard | src/features/analytics, src/app/api/analytics |
| Billing and customer finance | Documented | /docs/billing, /docs/customer-billing, /docs/payments-guide | src/features/billing, src/app/api/billing, src/app/api/webhooks |
| Branding | Documented | /docs/branding, /docs/configuration-guide | src/features/branding |
| Compliance and audit | Documented | /docs/compliance, /docs/production-safety | src/features/compliance |
| Contact and support inbox | Documented | /docs/contact, /docs/communications-and-email | src/features/contact, src/app/api/contact |
| Customer operations | Documented | /docs/customers, /docs/customer-billing | src/features/customers |
| Customer documentation starter | Documented | /docs/documentation, /docs/documentation-coverage | src/features/docs, src/app/docs |
| Notifications and email | Documented | /docs/notifications, /docs/communications-and-email, /docs/background-jobs | src/features/notifications, src/app/api/notifications |
| Content and publishing | Documented | /docs/posts, /docs/app-editor, /docs/app-marketing | src/features/posts |
| Application settings | Documented | /docs/settings, /docs/configuration-guide, /docs/environment-variables | src/features/settings |
| Team and permissions | Documented | /docs/team, /docs/security-access-and-admin | src/features/team |
| Waitlist | Documented | /docs/waitlist, /docs/app-public | src/features/waitlist, src/app/api/waitlist |
Coverage evidence
Representative feature boundaries
Coverage starts from real domain ownership rather than marketing claims.
src/features/account/server/queries/account.tssrc/features/billing/server/checkout/service.tssrc/features/posts/server/posts/services/editor-upsert.ts
Runtime and route boundaries
Reference coverage includes configuration, API health, and request safety.
src/lib/config.tssrc/app/api/health/route.tssrc/lib/security/rate-limit/policy.ts
Database contract
Table coverage comes from the canonical migration and generated application types.
supabase/migrations/20260426000000_init.sqlsrc/lib/supabase/types.ts
Release rule
- A new src/features domain must be assigned to a customer-facing guide before release.
- Partial or undocumented domains fail the documentation coverage contract.
- Environment variables, API methods and paths, and migration tables must match the checked-out application source.
- Stale code evidence is checked during documentation release validation.