Technical FAQ: event‐pipeline & The Volnux Transition - nshaibu/volnux GitHub Wiki

1. What exactly is the event-pipeline?

It is the reference executor for PointyLang. Its primary role is to validate the abstract syntax tree (AST) of a .pty script and ensure that result-streaming (|->), parallel (||) and sequential execution (->) follow the logical intent of the user.

2. Why does the event-pipeline implementation use recursion?

To accurately represent the Fractal Tree nature of Volnux, the early prototype used recursive calls to handle nested contexts and branching. While this is mathematically elegant and ensures deep-state integrity, it introduces overhead and stack-depth limitations for extremely long workflows.

3. How does this evolve in the full Volnux Engine?

The full Volnux Engine replaces the recursive core with an Asynchronous Task-Loop.

• The Transition: We are moving from "Function Calls" to "Task States" stored in the VolnuxPoolManager.
• The Result: This eliminates recursion-depth errors and allows for Soft-Preemption, as we can pause the loop at any "tick," save the state to Redis, and resume it later.

4. Does the bare-bones executor handle checkpointing?

No. The event-pipeline is a volatile, in-memory executor. Checkpointing is a first-class service in the full Volnux stack, handled by the ContextFactory and the RehydrationManager, which allows for state recovery after a node crash.