Technical Reference¶
Business documentation stops at product behavior. For APIs, schemas, and deployment, use the service repositories under novAIcarius.
Repository map¶
| Repository | Domain | Dev port (typical) |
|---|---|---|
| Kitten-Frontend-Repo | React SPA | 5173 |
| Kitten-Account-Repo | Auth, users | 8011 |
| Kitten-Organization-Repo | Orgs, hierarchy | 8012 |
| Kitten-Billing-Repo | Plans, subscriptions | 8013 |
| Kitten-AI-Chat-Repo | Chat, vision | 8014 |
| Kitten-Spending-Repo | Token ledger | 8002 |
| Kitten-Device-Repo | Stations, devices | 8017 |
| Kitten-Document-Repo | Files, MCP | 8000 |
| Kitten-Board-Repo | Boards | 8000 |
| Kitten-Remarkable-Repo | reMarkable | 5000 / 8004 |
| Kitten-Infrastructure-Repo | Nginx, Postgres, monitoring | 80 |
API prefixes (preferred)¶
/api/v1/account/*/api/v1/organization/*/api/v1/billing/*/api/v1/device/*/api/v1/document/*(incl./mcp/)/remarkable/,/remarkable-api/
Legacy un-prefixed routes may still exist during migration.
Deployment docs¶
See Kitten-Infrastructure-Repo README. To publish this documentation site to a private server, follow .github/DEPLOY.md in the Kitten-Documentation repository.