# ATC Integration Spec Skeleton

## Status
- Stage: placeholder
- Rule: do not convert this into an implementation spec until Ballbox has real credentials and a chosen workflow wedge

## Purpose
- Capture the structure Ballbox will need once ATC access is real.

## Integration Goal
- Chosen wedge:
- Why ATC is needed for this wedge:
- Minimum ATC depth required for v1: read only / read plus write

## Environment
- Target environment: beta / production
- Credentials available:
- Sportclubs available for testing:

## Auth
- Auth flow used:
- Token lifecycle:
- Credential ownership:
- Secret handling rules:

## Endpoints In Scope
- Read endpoints:
- Write endpoints:
- Optional endpoints:

## Data Ballbox Needs
- sportclubs:
- courts:
- availability:
- bookings:
- booking instances:
- players/users:
- activities:

## Mapping To Ballbox Domain
- ATC sportclub -> Ballbox:
- ATC court -> Ballbox:
- ATC booking -> Ballbox:
- ATC player/user -> Ballbox:

## Failure / Degraded Behavior
- if ATC is down:
- if ATC is stale:
- if writes fail:
- if Ballbox has partial local state:

## Open Questions
-
-
-