Compliance Auditor

Overview

Cron-triggered compliance audits that combine web search for regulatory updates, MCP tools for framework documentation, and retrieval queries for internal policies and audit history. The scanner uses extended reasoning (32k budget) for thorough analysis and stores findings for trend tracking. A reporter agent transforms raw findings into executive summaries with traffic-light compliance scores.

Use cases

Architecture

Main template files

Install these files with connic init my-project --templates=compliance-auditor. The CLI places agent definitions in a folder named after the template under agents/.

compliance-auditor/
  agents/
    compliance-scanner.yaml
    audit-reporter.yaml
  tools/
    compliance_tools.py
  schemas/
    audit-report.json
  requirements.txt
  README.md

Get started

Install the template, create a Connic project, and deploy through a connected Git repository or the CLI.

1. 1

   Install and scaffold

   Install the SDK and create a project from this template.

   terminal

   Copy

   pip install connic-composer-sdk
   connic init my-project --templates=compliance-auditor

   Then cd my-project

2. 2

   Deploy

   Choose a deployment method. A connected Git repository deploys on push; use the CLI for projects without a connected Git repository.

   Git integration

   1. 1

      In Connic: Project Settings → Git & Environments, connect the GitHub repository

   2. 2

      On the same page, map a branch (e.g. main) to the Production environment

   3. 3

      Push the scaffolded project to that repository

   terminal

   Copy

   git add .
   git commit -m "Add Compliance Auditor template"
   git push origin main

   CLI deploy

   1. 1

      In Connic: Project Settings → API Keys & MCP Auth, create an API key and copy project ID

   2. 2

      Run connic login in the project folder

   3. 3

      Use connic dev to try with hot-reload, connic test to run suites, or connic deploy for production

   terminal

   Copy

   connic login
   connic dev     # Ephemeral dev env with hot-reload
   connic test    # Run declarative test suites
   connic deploy  # Deploy to production

3. 3

   Connect and configure

   Add a Cron connector with a schedule expression (e.g. every Monday at 9 AM) and an optional prompt for the audit scope. Use a connic/* model, or add BYOK credentials under Project Settings → LLM Provider.

   Full connector setup guideQuickstart guideConnector docs