# Tenant Admin Control Plane Feature Index

This feature area defines the PoC control-plane model for managing clients and tenant restaurants through two API surfaces: admin and client.

For this feature:
- `client` = customer organization
- `tenant` = restaurant/store
- one client can have many tenants
- one tenant maps to one Redshift database
- bootstrap is a separate workflow triggered after tenant creation

## Responsibility Summary

- `admin` creates and lists customer organizations (`clients`)
- `client` creates, lists, and bootstraps its own restaurant tenants (`tenants`)

## Documents

- `feature-proposal.md` - business/domain scope, lifecycle, API scope, and control-plane rules
- `api-contract.md` - PoC API contract with request/response examples
- `data-model.md` - proposed relational model, constraints, and migration direction
- `implementation-notes.md` - backend implementation checklist

## Current Scope

In scope:
- admin client creation and listing
- client-scoped tenant creation and listing for the authenticated client
- client bootstrap trigger for authenticated-client tenants
- client get tenant by id for authenticated-client tenants
- tenant system-name configuration for bootstrap input
- case-insensitive system normalization and deduplication per tenant

Out of scope:
- authentication and authorization design
- user-to-tenant access model
- detailed client scoping and claims model
- bootstrap internal orchestration redesign
- secrets storage and integration credentials
- advanced onboarding workflow states
- rigid source-type classification such as POS/KDS/Inventory

## Notes

- This is a feature-level planning area, not yet split into `epics/` or `slices/`.
- If this grows into a longer-lived roadmap, it can later be reorganized into epics and slices without changing the current document intent.