Implementating exception handling policies for workflow management system
Why this work is in the frame
A frame that forgets how it found something cannot be audited. These are the routes that admitted this work.
Bibliographic record
Abstract
Exceptions are deviations from the normal execution of the program. They occur frequently in programs. In modern programming languages exceptions are separated from the normal execution using try-catch blocks and whenever an exception is raised then the catch blocks either recover from the exception in some way. or log the exception and abort. A workflow can be characterized as a long-running process. Exceptions occur in workflows but it is more expensive to abort the workflow as much work may be lost. Many proposals for describing workflows have been made. Some address exception handling, but few of these cleanly separate the description of the normal workflow from exceptions, and none present clear implementation details. Our approach to modeling and handling exceptions relies on continuations, listeners as exception handlers, and on policies, or strategies, for continuation. This model leads to a very flexible design and implementation of workflow. We present the details behind the implementation. Our work has been validated in a small prototype written in Java, though our approach and design are independent of the programming language.
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.
Full frame distilled prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.
Codex and Gemma teacher scores by category
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.000 | 0.000 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.000 | 0.001 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.001 | 0.001 |
| Open science | 0.000 | 0.000 |
| Research integrity | 0.000 | 0.000 |
| Insufficient payload (model declined to judge) | 0.000 | 0.000 |
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 it