What problem does it solve? Agents working with the Fianu compliance platform need a single canonical reference for reading and writing versioned entities — controls, policies, policy exceptions, and gates — without guessing endpoint shapes or misunderstanding the draft-then-approval lifecycle. ## Core Features & Use Cases - Entity reads: Fetch controls, policies, policy exceptions, and gates by key, with branching logic based on a ticket's targetEntityType. - History and schema discovery: Retrieve policy change history per control and discover evidence schemas via GET /controls/:key/schemas?producer=.... - Draft creation with approval flow: Create entities through POST /create/control and POST /create/policy, which produce drafts and automatically open approval tickets rather than publishing immediately. - Use Case: An agent processing an approval ticket for a policy exception fetches the exception, its parent policy, and the parent control, then reviews the policy's change history to detect repeated relaxations before recommending approval. ## Quick Start Ask the agent to fetch the Fianu control with a given entity key and summarize its Rego rule, policy template, and version history.
