PANIC!: An interactive AI playground for creating feedback loops of generative AI models
Bibliographic record
Abstract
PANIC! v3.0.0 - Ash Framework Migration (October 2024) Major architectural migration to the Ash Framework, representing a complete modernization of PANIC!'s codebase. Architecture SQLite + Ash Framework + GenServer Declarative resource definitions with Ash Integrated authentication via AshAuthentication Major Changes Ecto contexts → Ash domains: Business logic now organized in declarative domains Ecto schemas → Ash resources: Data modeling with powerful built-in querying Custom auth → AshAuthentication: Standardized authentication with multiple strategies Finitomata FSM → GenServer-based NetworkRunner: Simplified process architecture Terminology update: 'Prediction' → 'Invocation' for clearer semantics Benefits of Ash Framework Declarative resource definitions: Attributes, relationships, and actions defined in one place Powerful query interface: Composable queries with filtering, sorting, and loading Built-in authorization: Policy-based access control integrated into resources Code interfaces: Type-safe functions generated from resource definitions Extensibility: Easy to add new capabilities through Ash's extension system Technical Improvements Better separation of concerns with domain-driven design More maintainable codebase with less boilerplate Type-safe interfaces throughout the application Improved test architecture using Ash generators This version brings PANIC! into the modern Elixir ecosystem while maintaining backward compatibility with SQLite data storage. The Ash Framework provides a solid foundation for future development and makes the codebase significantly more maintainable.
Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.003 | 0.009 |
| Meta-epidemiology (narrow) | 0.001 | 0.001 |
| Meta-epidemiology (broad) | 0.001 | 0.002 |
| Bibliometrics | 0.001 | 0.000 |
| Science and technology studies | 0.001 | 0.002 |
| Scholarly communication | 0.004 | 0.005 |
| Open science | 0.003 | 0.007 |
| Research integrity | 0.001 | 0.003 |
| Insufficient payload (model declined to judge) | 0.093 | 0.014 |
Machine scores (provisional)
The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.
Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".