What problem does it solve? Agents working with the Fianu compliance platform need a correct, canonical contract for reading ticket state and posting approval activities, including subtle pitfalls like the auth-token actor convention and the config.resolved_approvers lookup that silently break naive implementations. ## Core Features & Use Cases - Ticket data model reference: Documents the Ticket, Condition, and Activity schemas, including the gotcha that approvers live in config.resolved_approvers rather than a top-level field. - Read and write API contract: Covers GET endpoints for tickets, conditions, and activities, plus the POST /tickets/:uuid/activities endpoint for approved, denied, and comment actions. - Actor convention and queue iteration: Enforces that the actor is set by the bearer token (never the request body) and defines batch processing rules with rate limiting and pagination. - Use Case: An autonomous agent polls open tickets, checks whether its identity (bot|fianu-agent) appears in a condition's resolved_approvers, and posts an approval activity with an audit-trail metadata payload. ## Quick Start Ask the agent to list all open Fianu tickets and post a comment activity on the one targeting a specific control entity.
