Court Behavior is Configuration,
Not Code
Multiple configurable domains across a layered overlay hierarchy. Every federal court's local rules, forms, fees, and deadlines expressed as governed configuration — no code changes, no deployments, no forks.
Layered Overlay Hierarchy
Configuration resolves bottom-up. Each layer can override keys from the layer below. The highest applicable layer wins.
22 Configurable Domains
Every aspect of court behavior is expressed as a typed configuration component, organized across seven domains.
Case Management
Filing
Financial
Scheduling
Routing
Notices
Governance
Package Lifecycle
Every configuration change follows a governed pipeline with validation gates at each stage.
Validation Gates
- Schema validation passes
- Source refs required on every override
- No unapproved aliases in state machine
- Fixture tests pass against snapshot
Overlay Configuration Examples
Court-specific deadlines, fees, and case opening rules expressed as governed configuration overlays.
# District Court — Deadline Overlay
# Example: local civil rule deadlines
overlay:
scope: district
layer: District
version: 1.3.0
deadlines:
opposition:
days: 14
calendar: court-business-days
source_ref: "Civ. L.R. 7-2(a)"
reply:
days: 7
calendar: court-business-days
source_ref: "Civ. L.R. 7-3(a)"# Bankruptcy Court — Fee Rules Overlay
# Example: bankruptcy-specific fee configuration
overlay:
scope: bankruptcy
layer: Bankruptcy
version: 2.1.0
fee_rules:
petition:
base_amount: configured-per-court
currency: USD
waiver_eligible: true
creditor_noticing:
per_creditor: configured-per-court
currency: USD
note: "Per creditor noticing surcharge"# District Court — Case Opening Model
# Example: case opening configuration
overlay:
scope: district
layer: District
version: 1.0.0
case_opening_model:
opener: attorney
case_number_assignment: instant
requires_coversheet: true
auto_assign_judge: true
nature_of_suit_validation: strictAI-Assisted Operations
AI assistants and human operators work with court configuration safely through governed protocols.
AI Resources
Read-only access to configuration, workflow state, audit trails, and reports.
AI Operations
Executable operations — mutations require human approval before execution.
Validates a court overlay against the Federal Core schema
Promotes a court overlay from staging to production
Rolls back a court overlay to a previous snapshot
Executes the security regression tests against a target tenant
Generates a human-readable diff between two configuration snapshots
Analysis Templates
Pre-built analysis workflows for common operational scenarios.
Analyzes a proposed overlay change against court local rules and federal policy
Evaluates whether a court package is ready for pilot based on test coverage, regression results, and configuration completeness
Triages a production incident by correlating audit trail events, workflow status, and recent configuration changes
See configuration in action
Walk through a live overlay resolution for your court type. See how local rules, forms, and deadlines become governed configuration.