Seed Data

AEGIS provides multiple seed scripts that populate the database and knowledge graph with sample data for development and demos. This page documents each seed script, what it creates, and how to run it. The entities these scripts write (wells, leases, operators, …) are the oil & gas set — a second installed vertical would ship its own seed data against its own runtime entity_type_definitions.

Seed Scripts Overview

Running All Seeds

After starting infrastructure with docker compose up -d and ensuring all services are running:

# 1. Seed the knowledge graph (requires KG service running on port 8003)
curl -X POST http://localhost:8003/seed
 
# 2. Seed checklists, rules, and demo data
cd services/orchestration-engine
poetry run python -m orchestration.seed_checklists
poetry run python -m orchestration.seed_rules
poetry run python -m orchestration.seed_demo_data

Seed Identity (R42e)

Since R42e, seeds write real identities that satisfy the platform’s uuid FKs to users(id) — no more free-text sentinel strings:

The system users themselves are seeded by core migration 031_identity_normalization.sql and re-converged by auth-service on every boot — see the schema page.

Knowledge Graph Seed

Endpoint: POST http://localhost:8003/seed

File: services/knowledge-graph-service/src/knowledge_graph/seed.py

Creates a realistic Permian Basin scenario in the tenant’s per-tenant Apache AGE graph (tenant_<hex>_oilgas; the dev tenant’s is tenant_00000000000000000000000000000001_oilgas). This is the most comprehensive seed script, building the full entity topology.

Entities Created

Relationships Created

The seed data connects entities with edges including:

• OPERATED_BY — wells, leases, facilities to operators
• LOCATED_IN — wells to leases and fields
• LOCATED_ON — wells to wellpads
• COMPLETED_IN — wells to formations
• GOVERNED_BY — wells to regulations
• OFFSET_TO — bidirectional between nearby wells
• FLARES_AT — authorizations to wells/leases
• PRODUCES_TO — wells to facilities
• FEEDS_INTO — facilities to pipeline routes
• CONNECTS_TO — infrastructure projects to leases

Demo Scenarios

The seed data supports three demo scenarios:

1. Compliance blast radius: Mitchell Ranch 1H -> Pad A -> Tank Battery -> Gathering Line
2. Infrastructure failure: Delaware Basin Compressor -> 3 wells, third-party operator
3. Planning surface: Howard R-32 expiring -> Howard Connector -> Spraberry system

Well Production Data

Every well includes full Form PR production data with 12 months of history:

{
    "production_oil_bbls": 5100.0,
    "production_gas_mcf": 10800.0,
    "production_casinghead_mcf": 420.0,
    "production_condensate_bbls": 85.0,
    "production_water_bbls": 2400.0,
    "gas_sold_mcf": 9200.0,
    "gas_used_on_lease_mcf": 380.0,
    "gas_flared_mcf": 1100.0,
    "gas_vented_mcf": 120.0,
    "producing_days": 30,
    "allocation_method": "test",
    "form_pr_period": "2026-02",
    "production_history_12m": [
        {"period": "2026-02", "oil_bbls": 5100, "gas_mcf": 10800, ...},
        {"period": "2026-01", "oil_bbls": 5300, "gas_mcf": 11200, ...},
        ...
    ]
}

Skill Registry Seed — retired

Checklist Template Seed

Command: poetry run python -m orchestration.seed_checklists (from services/orchestration-engine/)

File: services/orchestration-engine/src/orchestration/seed_checklists.py

Creates one checklist template per discovered pack. The template content (items, min_required_items) lives in the pack manifests (services/orchestration-engine/src/orchestration/packs/<name>/manifest.yaml, R41 B2) — the seeder just discovers packs and upserts, so adding or removing a pack changes the seed set with zero seeder edits.

Templates Seeded

Checklist Item Structure

Each item defines:

• index — Order within the checklist
• name — Human-readable item name
• item_type — data, document, form, artifacts, or validation
• completion_method — auto (agent-only) or hybrid (agent + human)
• agent_can — What the agent is capable of doing for this item
• user_must — What the human user is responsible for
• required_for_submission — Whether this item blocks filing submission

Example Rule 37 checklist items:

Rule Version Seed

Command: poetry run python -m orchestration.seed_rules (from services/orchestration-engine/)

File: services/orchestration-engine/src/orchestration/seed_rules.py

Populates the rule_versions table with statewide and field-specific rules.

Rules Seeded

Each rule version includes structured rule_data as JSONB with the actual regulatory parameters (distances, thresholds, deadlines, etc.).

Demo Data Seed

Command: poetry run python -m orchestration.seed_demo_data (from services/orchestration-engine/)

File: services/orchestration-engine/src/orchestration/seed_demo_data.py

Seeds realistic compliance data for a 15-minute demo walkthrough.

What Gets Seeded

• 25 wells with Permian Basin API numbers and compliance status distribution: 60% green (compliant), 25% amber (action needed), 15% red (overdue).
• Compliance status records in the compliance_status table for 4 domains per well (Rule 37, Rule 32, Form PR, Flaring).
• Pre-built Rule 37 checklist at ~40% completion for Mitchell Ranch 1H.
• Flare events with burn rate data for the flaring dashboard.
• Chart-ready historical data for compliance trends and deadline distributions.

Compliance Distribution

The demo data creates a realistic distribution of compliance statuses: