What problem does it solve? Teams managing Fianu compliance entities need a repeatable, version-controlled way to author and deploy controls, policies, exceptions, gates, and indexes from source repositories instead of making ad-hoc API calls, while avoiding duplicate deployments and approval-ticket churn. ## Core Features & Use Cases - Dual deployment paths: Deploy entities via the fianu console deploy CLI with on-disk YAML packages or via the Terraform provider resources (fianu_control, fianu_policy, fianu_gate, fianu_index), both targeting the same POST /entities/artifacts/deploy endpoint. - Idempotency guidance: Explains the SHA256 content-hash gate so unchanged inputs return action: "skipped", and clarifies which edits trigger new versions versus no-ops. - Format selection and edge cases: Provides a decision flow for choosing YAML versus Terraform, plus handling for path renames, cross-format drift, and pending approval tickets. - Use Case: A platform engineer adds a new control package to an envs/dev/controls/ directory, runs fianu console test and fianu console plan, then deploys with fianu console deploy, producing a draft entity and an approval ticket without touching unchanged entities. ## Quick Start Ask the agent to deploy the controls in your ./envs/dev/controls directory to Fianu using the console CLI and explain which entities were created, updated, or skipped.