Using Ring FinOps & Regulatory Agents

The ring-finops-team plugin provides 3 specialized FinOps agents: 2 for Brazilian financial compliance and 1 for infrastructure cost estimation. Use them via Task tool with subagent_type:.

Remember: Follow the ORCHESTRATOR principle from ring:using-ring. Dispatch agents to handle regulatory complexity; don't implement compliance manually.

3 FinOps Specialists

0. Infrastructure Cost Estimator (Customer Onboarding)

ring:infrastructure-cost-estimator (v5.0)

Architecture: Skill Orchestrates → Agent Calculates

SKILL gathers ALL data (including environment selection + Helm configs) → Agent calculates per-environment breakdown

How it works:

1. •Skill asks products: "Which products does customer need?" (Access Manager always included)
2. •Skill collects: Repo path, TPS, total customers
3. •Skill asks environment: "Which environments to calculate?" (Homolog, Production, or Both)
4. •Skill reads LerianStudio/helm: Only for selected products
5. •Skill asks per component: "Shared or Dedicated?" for each (VPC, EKS, PostgreSQL, Valkey, etc.)
6. •Skill asks backup policy: "What backup retention for Production?" (Homolog always minimal)
7. •Skill collects billing: Unit, price, volume
8. •Skill dispatches: Agent with products + actual Helm values + environments + backup config
9. •Agent calculates: Per-environment costs including backup costs (minimal for Homolog, full for Production)
10. •Agent returns: Side-by-side Homolog vs Production breakdown + backup costs + combined profitability

Backup Policy Differences:

Products Available:

Data source: git@github.com:LerianStudio/helm.git

Sharing Model Definitions:

• •SHARED = Schema-based multi-tenancy (same instance, different schemas per customer)
• •DEDICATED = Fully isolated instance (no other customers on this infrastructure)

Per-Component Sharing Model:

| Component | Sharing | Isolation | Customers | Cost/Customer |
|-----------|---------|-----------|-----------|---------------|
| EKS Cluster | SHARED | Namespace per customer | 5 | R$ 414 (÷5) |
| PostgreSQL | DEDICATED | Own RDS instance | 1 | R$ 1,490 (full) |
| Valkey | SHARED | Key prefix per customer | 5 | R$ 130 (÷5) |

Output (7 sections):

1. •Discovered Services
2. •Infrastructure Components (per-component breakdown)
3. •Cost by Category (compute, database, network, storage, backups %)
4. •Backup Costs by Environment (Homolog minimal vs Production full)
5. •Shared vs Dedicated Summary (clear separation)
6. •Profitability Analysis
7. •Summary

Example dispatch (with per-component sharing + backup config):

Task tool:
  subagent_type: "ring:infrastructure-cost-estimator"
  model: "opus"
  prompt: |
    Calculate infrastructure costs and profitability.

    ALL DATA PROVIDED (do not ask questions):

    Infrastructure:
    - Repo: /path/to/repo
    - Helm Source: LerianStudio/helm
    - TPS: 100
    - Total Customers on Platform: 5

    Actual Resource Configurations (READ from LerianStudio/helm):
    | Service | CPU Request | Memory Request | HPA | Source |
    |---------|-------------|----------------|-----|--------|
    | onboarding | 1500m | 512Mi | 2-5 | midaz |
    | transaction | 2000m | 512Mi | 3-9 | midaz |
    | auth | 500m | 256Mi | 3-9 | access-manager |
    | ... | ... | ... | ... | ... |

    Component Sharing Model:
    | Component | Sharing | Customers |
    |-----------|---------|-----------|
    | EKS Cluster | SHARED | 5 |
    | PostgreSQL | DEDICATED | 1 |
    | Valkey | SHARED | 5 |
    | DocumentDB | SHARED | 5 |
    | RabbitMQ | SHARED | 5 |

    Backup Configuration:
    | Environment | Retention | Snapshots | PITR | Expected Cost |
    |-------------|-----------|-----------|------|---------------|
    | Homolog | 1-7 days | Automated only | No | ~Free |
    | Production | 7 days | Daily (7) | Yes | R$ 38-175/month |

    Billing Model:
    - Billing Unit: transaction
    - Price per Unit: R$ 0.10
    - Expected Volume: 1,000,000/month

Skill: ring:infrastructure-cost-estimation - Reads LerianStudio/helm at runtime, orchestrates data collection.

1. FinOps Analyzer (Compliance Analysis) - Regulatory

ring:finops-analyzer

Specializations:

• •Brazilian regulatory compliance analysis
• •BACEN (Central Bank) requirements:
  • •COSIF (accounting chart of accounts)
  • •CADOCs (financial instruments catalog)
• •RFB (Federal Revenue) requirements:
  • •e-Financeira (financial reporting)
  • •SPED (electronic data exchange)
• •Open Banking specifications
• •Field mapping & validation

Use When:

• •Analyzing regulatory requirements (Gate 1-2)
• •Validating field mappings for compliance
• •Understanding BACEN/RFB specifications
• •Planning compliance architecture
• •Determining required data structures

Output: Compliance analysis, field mappings, validation rules

Example dispatch:

Task tool:
  subagent_type: "ring:finops-analyzer"
  model: "opus"
  prompt: "Analyze BACEN COSIF requirements for corporate account reporting"

2. FinOps Automation (Template Generation)

ring:finops-automation

Specializations:

• •Template generation from specifications
• •.tpl file creation for Reporter platform
• •XML template generation
• •HTML template generation
• •TXT template generation
• •Reporter platform integration

Use When:

• •Generating regulatory report templates (Gate 3)
• •Creating BACEN/RFB compliant templates
• •Building Reporter platform files
• •Converting specifications to executable templates
• •Finalizing compliance implementation

Output: Complete .tpl template files, ready for Reporter platform

Example dispatch:

Task tool:
  subagent_type: "ring:finops-automation"
  model: "opus"
  prompt: "Generate BACEN COSIF template from analyzed requirements"

Regulatory Workflow: 3-Gate Process

Brazilian regulatory compliance follows a 3-gate workflow:

Gate 1: Compliance Analysis

Agent: ring:finops-analyzer Purpose: Understand requirements, identify fields, validate mappings Output: compliance analysis document

Dispatch when:

• •Starting regulatory feature
• •Need to understand BACEN/RFB specs
• •Planning field mappings

Gate 2: Validation & Confirmation

Agent: ring:finops-analyzer (again) Purpose: Confirm mappings are correct, validate against specs Output: validated specification document

Dispatch when:

• •Ready to confirm compliance understanding
• •Need secondary validation
• •Before moving to template generation

Gate 3: Template Generation

Agent: ring:finops-automation Purpose: Generate executable .tpl templates from validated specifications Output: complete .tpl files for Reporter platform

Dispatch when:

• •Specifications are finalized & validated
• •Ready to create Reporter templates
• •Need production-ready compliance files

Supported Regulatory Standards

BACEN (Central Bank of Brazil)

• •COSIF – Chart of accounts and accounting rules
• •CADOCs – Financial instruments and derivatives catalog
• •Manual de Normas – Regulatory requirements

RFB (Brazilian Federal Revenue)

• •e-Financeira – Electronic financial reporting
• •SPED – Electronic data exchange system
• •ECF – Financial institutions data

Open Banking

• •API specifications – Data sharing standards
• •Security requirements – Auth and encryption
• •Integration patterns – System interoperability

Decision: Which Agent?

When to Use FinOps Agents

Use ring:infrastructure-cost-estimator for:

• •✅ "How much will this cost on AWS?" – Auto-discovers from docker-compose
• •✅ "Which components are shared vs dedicated?" – Per-component cost attribution
• •✅ "What's the cost breakdown by category?" – Compute, database, network percentages
• •✅ "Is this deal profitable?" – Calculates revenue, cost, and gross margin
• •✅ Customer onboarding – Full detailed breakdown + profitability analysis
• •✅ Break-even analysis – Shows minimum volume needed to cover costs

Use ring:finops-analyzer for:

• •✅ Understanding regulations – What does BACEN require?
• •✅ Compliance research – How do we map our data?
• •✅ Requirement analysis – Which fields are required?
• •✅ Validation – Does our mapping match the spec?

Use ring:finops-automation for:

• •✅ Template creation – Build .tpl files
• •✅ Specification execution – Convert analysis to templates
• •✅ Reporter platform prep – Generate deployment files
• •✅ Production readiness – Finalize compliance implementation

Dispatching Multiple FinOps Agents

If you need both analysis and template generation, dispatch sequentially (analyze first, then automate):

Workflow:
Step 1: Dispatch ring:finops-analyzer
  └─ Returns: compliance analysis
Step 2: Dispatch ring:finops-automation
  └─ Returns: .tpl templates

Note: These must run sequentially because automation depends on analysis.

ORCHESTRATOR Principle

Remember:

• •You're the orchestrator – Dispatch agents, don't implement compliance manually
• •Don't write BACEN specs yourself – Dispatch analyzer to understand
• •Don't generate templates by hand – Dispatch automation agent
• •Combine with ring:using-ring principle – Skills + Agents = complete workflow

Good Example (ORCHESTRATOR):

"I need BACEN compliance. Let me dispatch ring:finops-analyzer to understand requirements, then ring:finops-automation to generate templates."

Bad Example (OPERATOR):

"I'll manually read BACEN documentation and write templates myself."

Reporter Platform Integration

Generated .tpl files integrate directly with Reporter platform:

• •Input: Validated specifications from ring:finops-analyzer
• •Output: .tpl files (XML, HTML, TXT formats)
• •Deployment: Direct integration with Reporter
• •Validation: Compliance verified by template structure

Available in This Plugin

Agents (3):

• •ring:infrastructure-cost-estimator (Infrastructure cost estimation)
• •ring:finops-analyzer (Regulatory Gates 1-2)
• •ring:finops-automation (Regulatory Gate 3)

Skills (7):

• •using-finops-team (this skill - plugin introduction)
• •infrastructure-cost-estimation (AWS cost estimation methodology)
• •regulatory-templates (overview/index skill)
• •regulatory-templates-setup (Gate 0: Setup & initialization)
• •regulatory-templates-gate1 (Gate 1: Compliance analysis)
• •regulatory-templates-gate2 (Gate 2: Field mapping & validation)
• •regulatory-templates-gate3 (Gate 3: Template generation)

Note: If agents are unavailable, check if ring-finops-team is enabled in .claude-plugin/marketplace.json.

Integration with Other Plugins

• •ring:using-ring (default) – ORCHESTRATOR principle for ALL agents
• •ring:using-dev-team – Developer specialists
• •ring:using-pm-team – Pre-dev workflow agents

Dispatch based on your need:

• •General code review → default plugin agents
• •Regulatory compliance → ring-finops-team agents
• •Developer expertise → ring-dev-team agents
• •Feature planning → ring-pm-team agents