Product
Documentation for the customer-facing astrology API product: the product app, the account and access backend, and the commercial rules around API usage.
The product app goal sheet records requested product scope, pages, backend responsibilities, and delivery milestones. It is a living plan; unchecked items are proposed work, not implemented behavior.
The product backend guide documents the Kotlin/JVM Spring Boot service that currently implements Google sign-in, backend token pairs, and persisted login sessions. Profile, API-key, usage, payment, and redeem-code behavior is modeled in the schema but not yet exposed by the service.
Guides
| Area | Guide | Status |
|---|---|---|
| Product app | Goals, pages, and milestones | Proposed scope; partial backend implementation |
| Backend service | Overview and documentation map | Implemented sign-in and sessions; other features planned |
| Authentication | Google sign-in, token pairs, and sessions | Implemented |
| HTTP API | Routes, examples, and error contract | Implemented sign-in, smoke, and docs routes |
| Database | PostgreSQL schema and ownership rules | Schema implemented; manual application |
| Production design | Spring Boot container with Supabase PostgreSQL | Local pieces implemented; production path proposed |
| Local development | Setup, configuration, and commands | Implemented |
| Native builds | GraalVM native image and reflection | Implemented |
Conventions
- Keep each feature guide and its diagrams together in the feature directory.
- State whether behavior is implemented, proposed, or unresolved. Do not turn a proposed architecture into a claim of deployed behavior.
- Link schema changes to the owning SCHEMA.md and keep the executable migration in sync.
- Treat the product app goal sheet as the source of product intent; treat the backend guide as the source of implemented service behavior.