lib/docs/MEMBERS_TRACK_EVENT_CLIENT.md

27 lines
1.1 KiB
Markdown

# Members TrackEvent client
Date: 2026-07-24
Provider source: Members commit
`4d9fbe2` (`agent/track-event-provider`; draft until exact DB scopes land).
The generated Members client exposes only:
- `GET /trackevents` for tenant-bounded list/detail reads, with optional ID,
TrackID, and EventID filters.
- `POST /trackevents` for Owner/Manager creation of one immutable
Track-to-Event association.
The provider requires compound machine API-key plus native member-session
authentication and exact `members:track-event:read` or
`members:track-event:create` machine scope. There is no broad manage scope,
update, delete, Ticket coupling, Salesforce, sf-gate, Cache, credential, or
direct-database client surface.
Members proves both roots against the configured Keenan Vision tenant:
the Track creator and Event organizer must each have an active membership.
Contributors may read only relationships for which they own both roots.
`TrackTopic` remains blocked on a governed Members-to-Research Topic
validation capability. `TrackUser` remains blocked on an explicit
assignment-role vocabulary and grant/revoke lifecycle.