How christian-mar/fde_project works
This is a small Python claims-data exploration starter, not yet a claim-adjudication product. The user runs main.py, which loads sample claims, handler decisions, policies and policy wording, then prints individual claims and summary tables. The data module also supports tiny and held-out evaluation sets. A separate configuration module creates an OpenRouter-compatible client, but the shown workflow only checks whether its key exists; no model request or claim decision is implemented. Relationships below follow the sampled entry point and loader; no unsampled runtime behavior is assumed.
Main entry points: data.py Dataset loader · main.py CLI workflow · config.py API configuration · explore.py Data summaries
Components 12
CLI exploration
- CLI workflow
main.py - Data summaries
undercover/explore.py
Claims datasets
- Dataset loader
undercover/data.py - Claim queue
data/claims.json - Handler decisions
data/evals/decisions.json - Held-out set
data/evals/held_out_claims.json - Held-out labels
data/evals/held_out_decisions.json - Policy records
data/policies.json - Policy wording
data/policy_wording.md
Model configuration
- API configuration
undercover/config.py
Other components
- User
- OpenRouter API
Connections 11
- User → CLI workflow: runs
README.md - CLI workflow → API configuration: checks key
main.py - CLI workflow → Dataset loader: loads datasets
main.py - Dataset loader → Claim queue: reads queue
undercover/data.py - Dataset loader → Handler decisions: reads labels
undercover/data.py - Dataset loader → Held-out set: reads alternate claims
undercover/data.py - Dataset loader → Held-out labels: reads alternate labels
undercover/data.py - Dataset loader → Policy records: reads policies
undercover/data.py - Dataset loader → Policy wording: reads wording
undercover/data.py - CLI workflow → Data summaries: prints summaries
main.py - API configuration → OpenRouter API: configures client
undercover/config.py