README
U
Callback
U
Guard
U
TransitionAction
T
AuditRecord
T
BatchReport
T
BudgetReport
- ::buildBuilder::build
- ::newBuilder::new
- ::on_enterBuilder::on_enter
- ::on_exitBuilder::on_exit
- ::transitionBuilder::transition
- ::transition_doBuilder::transition_do
- ::transition_ifBuilder::transition_if
- ::transition_if_doBuilder::transition_if_do
- ::getContextManager::get
- ::newContextManager::new
- ::setContextManager::set
T
DispatchOutcome
T
DuplicateTransition
- ::audit_logEngine::audit_log
- ::checkpointEngine::checkpoint
- ::contextEngine::context
- ::historyEngine::history
- ::last_errorEngine::last_error
- ::metricsEngine::metrics
- ::reset_metricsEngine::reset_metrics
- ::restoreEngine::restore
- ::sendEngine::send
- ::stateEngine::state
- ::try_sendEngine::try_send
- ::try_send_allEngine::try_send_all
- ::try_send_with_budgetEngine::try_send_with_budget
- ::try_send_with_retryEngine::try_send_with_retry
T
EngineConfig
- ::defaultEngineOptions::default
T
EngineSnapshot
- ::copyExecutionMetrics::copy
- ::zeroExecutionMetrics::zero
T
GraphSummary
T
HistorySummary
T
JournalAggregate
T
JournalEntry
- ::open_incidentsJournalFilter::open_incidents
- ::ticket_eventsJournalFilter::ticket_events
T
JournalLevel
T
RetryAttempt
T
RetryMode
- ::newRetryPolicy::new
T
RetryReport
T
SlaEvaluation
T
SlaTarget
T
TicketJournalSummary
T
Transition
T
TransitionError
T
TransitionRecord
T
ValidationReport
- ::acknowledgeWorkflowJournal::acknowledge
- ::acknowledge_ticketWorkflowJournal::acknowledge_ticket
- ::append_auditWorkflowJournal::append_audit
- ::count_levelWorkflowJournal::count_level
- ::criticalWorkflowJournal::critical
- ::entriesWorkflowJournal::entries
- ::errorWorkflowJournal::error
- ::for_ticketWorkflowJournal::for_ticket
- ::has_criticalWorkflowJournal::has_critical
- ::infoWorkflowJournal::info
- ::latest_for_ticketWorkflowJournal::latest_for_ticket
- ::newWorkflowJournal::new
- ::unacknowledged_incidentsWorkflowJournal::unacknowledged_incidents
- ::warningWorkflowJournal::warning
V
aggregate_journals
V
assert_invariant
V
branching_states
V
duplicate_transition_entries
V
evaluate_sla
V
format_journal_level
V
format_transition_error
V
format_transition_log
V
graph_summary
V
has_open_at_least
V
history_summary
V
journal_line
V
latest_matching
V
level_counts
V
query_journal
V
sla_status
V
successful_transitions
V
summarize_ticket
V
to_mermaid
V
validate
V
validate_report
V
workflow_risk_score

#Workflow Benchmark Corpus

This directory is a deterministic scenario benchmark for moon-fsm. It is designed to make the project scope and behavior reviewable without depending on wall-clock timing, CPU model, or a network service.

The checked-in CSV contains 44 representative workflow cases across four common engineering domains:

approval and review workflows
order fulfillment and cancellation
device boot, fault, and recovery flows
support ticket assignment, escalation, reopening, and closure

The extended support cases also cover customer waiting, cancellation, terminal-event storms, and long reopen loops. The runnable examples extend those scenarios with examples/support_workflow for customer operations and examples/incident_workflow for incident commander assignment, mitigation, rollback, journal ingestion, SLA checks, runbook handover, and closure review.

Each case records the initial state, initial context, event sequence, expected final state, successful transition count, and rejected-event count. The executable runner in main.mbt uses the same cases as typed data and verifies the expected history length and audit-entry count after every scenario.

Run the benchmark from the module root:

moon run benchmarks

This is a behavioral scenario benchmark, not a claim about throughput across hardware. It complements the unit tests by exercising longer, realistic paths and explicit failure/recovery branches.