Skip to Content

Rule 32 Pack & rrc_rule32 Skill

This page documents the RRC oil & gas vertical — one of the five packs installed on AEGIS. The mechanisms (packs, skills, routers, HITL rules) are domain-neutral.

The rule_32 pack and the rrc_rule32 skill cover Form R-32 filings for flaring and venting exceptions under Texas Administrative Code 16 TAC 3.32. A user reaches this capability in a general-mode conversation through the flaring router — which carries a watch/file pair: monitoring questions go to flaring_watch (see Flaring Pack), and preparing an application goes to rrc_rule32. There is no dedicated “Rule 32 agent” to pick anymore.

How it is reached

MechanismValue
Packrule_32 (packs/rule_32/manifest.yaml)
Skill keyrrc_rule32
Routerflaringrrc_rule32 (filing) / flaring_watch (monitoring)
Compliance domainrule_32
Entity typesWell

The effective LLM model is tenant-configured via Platform Settings (box default anthropic/claude-sonnet-5).

Regulatory Context

Rule 32 (16 TAC 3.32) governs the flaring and venting of natural gas in Texas. The pack’s assessment recipe resolves thresholds from rule_versions for SWR_32:

ParameterDefault
Renewal notice window (renewal_notice_days)30 days
Volume warning fraction (volume_warning_fraction)0.80 of the authorized period cap
Disposition Code 10Flared gas
Disposition Code 11Vented gas

Operators file a Form R-32 to obtain authorization for flaring or venting. The skill also tracks federal EPA requirements that overlap with the state rule.

Unlike Rule 37 (well placement), Rule 32 addresses what happens to natural gas that cannot be captured, processed, or sold. Flaring (burning) is preferred over venting (releasing unburned) because venting releases methane, a potent greenhouse gas.

Skills in the pack

The rule_32 pack declares ten skills. Some are code-backed (orchestration.skills.rule32.*); rule32_gas_composition, rule32_emissions, and rule32_readiness_check are declarative descriptors (context_table, emissions_calc, readiness_check).

Skill keyItemPurpose
rule32_exception_typeException Type DeterminationClassify emergency / initial / extension / permanent; determine applicable R-32 provisions
rule32_auth_reviewCurrent Authorization ReviewQuery existing R-32 authorizations; show history, volumes, durations; flag expirations
rule32_volume_analysisFlaring Volume AnalysisPull production/flaring data; compute current volumes vs. authorized limits; project when limits are reached
rule32_gas_compositionGas Composition AnalysisCompile H2S, BTU, CO2, N2, NGL data; flag against pipeline/R-32 requirements
rule32_pipeline_assessmentPipeline Availability AssessmentResearch gathering infrastructure; document proximity, capacity, connection timeline
rule32_economic_analysisEconomic Feasibility AnalysisDraft capture-alternative economics (pipeline, compression, reinjection, on-site use)
rule32_form_r32Form R-32 PopulationPre-fill R-32 fields from entity data and analysis results
rule32_emissionsEmissions Impact EstimateCalculate CO2e using EPA factors; generate ESG/GHGRP reporting data
rule32_timelineCompliance TimelineCompute the R-32 deadline calendar (authorization duration, extension windows, CFO triggers)
rule32_readiness_checkFiling Readiness CheckValidate required R-32 fields and supporting-documentation completeness

Checklist & assessment

The pack’s checklist template defines these ten items (indices 0–9) with min_required_items 0, 1, 2, 4, 6, 8, 9. The assessment recipe runs a deadline_window check against the authorization’s expiration date (renewal_notice_days) and a cumulative_limit check summing flared volume_mcf against the period cap (authorized_volume_mcf, not the Mcf/day cap — comparing a multi-day total against a daily cap would fabricate violations). Auth-only rows with no governing well are stamped as FlaringAuthorization and named by authorization_number (INT-1 parity).

HITL Checkpoints

HITL travels with the rrc_rule32 skill as a seeded require_hitl rule:

Rule keyCheckpointTrigger
skill:rrc_rule32:pre_filingpre_filingR-32 filing assembly, before RRC submission

There is intentionally no emissions HITL rule for rrc_rule32 — emissions is a model-supplied calculation (rule32_emissions), not a filing gate. The single gate is pre_filing on filing assembly. The approval_node is fail-closed and pauses (awaiting_hitl) rather than proceed unreviewed.

Skill-scoped tools

Once rrc_rule32 is loaded, its code-block tools become available — notably rule32_filing_assembly (the HITL-gated mutation). The read-only flaring_watch skill reuses these code-block implementations under the distinct tool names flaring_volume_status and emissions_screening.

Known open regression: the Rule 32 filing path can 500 on the 25-superstep recursion limit after the sonnet-5 model bump (docs/specs/R40b-rule32-filing-recursion-500.md).

FormFull NamePurpose
R-32Application for Exception to Statewide Rule 32Primary application for flaring/venting authorization
PRMonthly Production ReportMonthly filing that includes gas disposition (flared, vented, sold) — its own form_pr pack
RuleScopeRelevance
OOOObNew and modified sources after Nov 15, 2021Methane emission limits — the separate epa_oooob pack (the fifth installed pack)
GHGRP Subpart WFacilities exceeding 25,000 MT CO2e/yearAnnual greenhouse-gas reporting for petroleum and natural gas systems

Disposition Codes

CodeMeaningRegulatory Impact
10Flared (burned)Requires R-32 authorization above de minimis levels
11Vented (released unburned)Most scrutinized — direct methane emission

Example Interaction

In a general conversation:

“We need to file a flaring exception for the Howard Unit wells. We’ve been flaring since completion and the pipeline connection isn’t ready.”

The agent pulls the flaring router, disambiguates to rrc_rule32 (filing, not monitoring), loads the skill, and then reviews authorizations and volumes, assesses gas composition and pipeline availability, estimates CO2e, assembles the R-32 package, and pauses at the pre_filing HITL checkpoint.

Last updated on