Project
GateKeeper
Token-based API entitlement layer for racing data APIs: resolves per-request, per-customer access (country/discipline/data-type/venue) from admin-defined packages and overrides, with a two-tier push-invalidated cache.
D:\Projects\Project-Gate Keeper\GateKeeper
Overview
Re-synced with docs/OVERVIEW.md and added a link to the new Database reference page
Quick Reference
Replace the inline HTTP API section with a pointer to the new dedicated API Reference page, to avoid maintaining the same endpoint contracts in two places
Known Issues & Discrepancies
Initial known-issues page: discrepancies against the original design doc plus what's intentionally not built yet — derived from docs/PROJECT_DOCUMENTATION.md §11-12
API Reference
New dedicated API page with exact endpoint contracts (request/response DTOs) read directly from AdminEndpoints.cs, MeetingsEndpoint.cs, and the route table in Program.cs — supersedes the summary version in Quick Reference
Architecture & Technical Reference
Initial technical deep-dive: data model, resolution algorithm, caching, request pipeline — derived from docs/PROJECT_DOCUMENTATION.md and a read of GateKeeper.Cache source (including the in-progress configurable-TTL change)
Database
New page: full table-by-table DB reference, derived from docs/gatekeeper-db-documentation.md, adding the data_types and api_request_logs tables that were missing from Architecture's summary
User Guide
New page: hands-on run/configure/onboard walkthrough describing each step, derived from README.md — distinct from the conceptual Overview page; runnable command examples deliberately left in README.md rather than duplicated here