boards-api
Manages ticket-platform integrations within tenant organisations. Stores per-tenant provider configurations (Azure Boards, Linear, Jira), exposes a vendor-neutral ticket abstraction, ingests inbound webhooks from providers, and generates ticket backlogs from contract artefacts (OAS uploads, OAS diffs, verification specs, compatibility drift, subscription events). Boards-service is the fourth governance surface of the API-First prerequisite stack (gateway, security, catalogue, boards). Tickets are the durable carrier of work state — including persona-generated output once Tier 3 AI personas ship — so every ticket records its origin (human or persona) and its source artefact (OAS, verification spec, subscription event) for audit and lineage. Providers follow a state lifecycle: Pending → Active → Disabled. Tickets follow: New → Active → Resolved → Closed (with a Cancelled terminal). Provider tokens are write-only — never returned in responses.