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
14 documented, 0 partial, and 0 undocumented product domains.
| Product domain | Status | Primary guides | Maintainer reference |
|---|---|---|---|
| Account and authentication | Documented | /docs/auth-and-account, /docs/app-auth | Implementation referencesrc/features/account, src/lib/auth |
| Analytics | Documented | /docs/analytics, /docs/app-dashboard | Implementation referencesrc/features/analytics, src/app/api/analytics |
| Billing and customer finance | Documented | /docs/billing, /docs/customer-billing, /docs/payments-guide | Implementation referencesrc/features/billing, src/app/api/billing, src/app/api/webhooks |
| Branding | Documented | /docs/branding, /docs/configuration-guide | Implementation referencesrc/features/branding |
| Compliance and audit | Documented | /docs/compliance, /docs/production-safety | Implementation referencesrc/features/compliance |
| Contact and support inbox | Documented | /docs/contact, /docs/communications-and-email | Implementation referencesrc/features/contact, src/app/api/contact |
| Customer operations | Documented | /docs/customers, /docs/customer-billing | Implementation referencesrc/features/customers |
| Customer documentation starter | Documented | /docs/documentation, /docs/documentation-coverage | Implementation referencesrc/features/docs, src/app/docs |
| Notifications and email | Documented | /docs/notifications, /docs/communications-and-email, /docs/background-jobs | Implementation referencesrc/features/notifications, src/app/api/notifications |
| Content and publishing | Documented | /docs/posts, /docs/app-editor, /docs/app-marketing | Implementation referencesrc/features/cms |
| Privacy and cookie consent | Documented | /docs/privacy, /docs/production-safety | Implementation referencesrc/features/privacy, src/lib/tracking |
| Application settings | Documented | /docs/settings, /docs/configuration-guide, /docs/environment-variables, /docs/initial-project-setup | Implementation referencesrc/features/settings |
| Team and permissions | Documented | /docs/team, /docs/security-access-and-admin | Implementation referencesrc/features/team |
| Waitlist | Documented | /docs/waitlist, /docs/app-public | Implementation referencesrc/features/waitlist, src/app/api/waitlist |
Implementation reference3 areas
These Product code locations explain how the documented behavior is implemented. Expand them when you are ready to customize or maintain this area.
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/cms/server/documents/services/editor-upsert.ts
Runtime and route boundaries
Reference coverage includes configuration, API health, and request safety.
src/lib/config.tssrc/app/api/health/ready/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
Reference paths are relative to the Shipflash-Product checkout.
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.