Overview
The Compliance & Governance tools enable agents to perform regulatory validation and approval workflows across multiple compliance frameworks. These tools ensure all high-risk operations maintain audit trails, segregation of duties, and regulatory compliance. Supported regulatory frameworks:- SOX (Sarbanes-Oxley): Segregation of duties requirements
- ASIC RG94: NAV tolerance and valuation frequency requirements
- AIFMD: Alternative Investment Fund Managers Directive compliance
Regulatory Frameworks
SOX Compliance (Sarbanes-Oxley)
Enforces segregation of duties to prevent conflicts of interest. Key rules:- Same user cannot initiate and approve transactions
- Risk-based approval chains required
- All actions logged with immutable audit trails
- Enforcement through role-based access control
ASIC RG94
Australian Securities and Investments Commission guidance for fund managers. Validates:- Net Asset Value (NAV) tolerance within acceptable ranges
- Valuation frequency requirements (daily/weekly based on fund type)
- Consistent valuation methodologies
- Timely disclosure of pricing discrepancies
AIFMD
European Union regulatory framework for Alternative Investment Fund Managers. Ensures:- Proper valuation procedures documented
- Fair pricing of fund assets
- Risk management compliance
- Regular compliance reporting
Quick Start
Basic Compliance Check
Approval Workflow
Tool Reference
check_compliance
Validates actions against regulatory requirements before execution. Input Schema:approval: Multi-level approval requestsvalidation: Data validation operationstransaction: Financial transactionsoverride: Regulatory override requestsreport: Compliance reporting
compliant=true: Action passes all checks, safe to proceedcompliant=false, requires_approval=true: Userequest_approvaltoolcompliant=false, requires_approval=false: Action violates mandatory rules
request_approval
Creates an approval request for high-risk actions or compliance overrides. Input Schema:override: Manager or Compliance Officervalidation: Compliance Officertransaction(high-value): Director or Officerapproval: Next approval level up
submit_approval
Submits an approval or rejection decision for a pending request. Enforces segregation of duties. Input Schema:- Approver must have required role
- Cannot approve request initiated by same user (SOX segregation)
- Request must not be expired
- Comments required for rejections
get_pending_approvals
Retrieves pending approval requests for a specific user based on their role. Input Schema:low: Routine validationsmedium: Standard transactionshigh: High-value or sensitive operationscritical: Multi-level approvals or regulatory overrides
generate_compliance_report
Generates regulatory compliance reports for audit and governance purposes. Input Schema:-
sox_audit: SOX compliance audit
- Segregation of duty violations
- Approval chain completeness
- User access changes
- High-risk transaction approvals
-
rg94_validation: ASIC RG94 validation
- NAV variance by fund
- Valuation frequency compliance
- Pricing discrepancies
- Fund-specific metrics
-
aifmd: AIFMD compliance
- Valuation procedure adherence
- Risk management compliance
- Fee disclosure accuracy
- Leverage limits
-
agent_activity: Agent action summary
- Tool usage statistics
- Approval rates
- Error counts
- User activity summary
-
approval_workflow: Approval process audit
- Pending request count
- Approval time metrics
- Rejection rates
- Role-based distribution
verify_audit_integrity
Verifies the integrity of the audit trail using cryptographic hashing to detect tampering. Input Schema:- Uses SHA-256 blockchain-inspired hash chaining
- Each event contains hash of previous event
- Verifies entire chain integrity
- Returns error at first tampering detection
- Prevents retroactive audit manipulation
Approval Workflow Details
Request Lifecycle
- Create:
request_approvalinitiates request withrequired_role - Pending: Request appears in approver’s queue via
get_pending_approvals - Approve/Reject:
submit_approvalwith decision - Expire: Requests expire after 48 hours if not processed
- Log: All transitions recorded in audit trail
Role-Based Access
Approval routing based on risk level and action type:| Action Type | Risk Level | Required Role | Approval Time |
|---|---|---|---|
| validation | low | Analyst | 4 hours |
| validation | medium | Manager | 4 hours |
| transaction | low | Manager | 2 hours |
| transaction | high | Director | 1 hour |
| override | any | Compliance Officer | 2 hours |
| approval | critical | Officer+ | 30 min |
Segregation of Duties
- Initiator cannot approve own requests
- Same role cannot form full approval chain
- Director approval bypasses Manager approval
- All decisions require documented justification
Error Handling
Common Errors
Compliance Check Fails:Best Practices
- Always Check Compliance First: Call
check_compliancebefore executing high-risk operations - Include Context: Provide detailed
action_dataandreasonfor approval requests - Monitor Expiry: Check
expires_aton approval requests before submitting - Segregate Duties: Ensure approvers differ from requesters
- Audit Regularly: Generate compliance reports weekly for governance oversight
- Verify Integrity: Run
verify_audit_integritymonthly to detect tampering
Configuration
All tools authenticate via JWT token in RunnableConfig:- Supabase authentication
- User role verification
- Audit trail access
- Report generation