Process View

The Process View describes simulation, testing, file management, contributor access, and real-time collaborative editing.

Activity Diagram - Simulation Flow

The main simulation execution flow when a user runs a Turing Machine. Sprint 2 now computes complexity metrics alongside the simulation.

Activity Diagram - Test Execution Flow

The batch test execution process using the Marker engine added in Sprint 2.

Activity Diagram - File Save and Versioning

The file persistence flow with automatic version management added in Sprint 2.

Activity Diagram - Bidirectional Sync

The synchronization process between the visual diagram and code editor. Sprint 2 extended this with multi-tape variant awareness.

Activity Diagram - Collaborative Editing Session

The editor enables Yjs collaboration for the owner and invited contributors of a saved document. Collaboration state is room-synchronized; saving a durable file version remains a separate action.

Activity Diagram - User Authentication Flow

The OAuth authentication process using Better-Auth.

Activity Diagram - Dashboard Document Management

The document lifecycle from the home dashboard added in Sprint 2.

Sequence Diagram - File Save with Versioning

Detailed sequence for saving a machine document with version control.

Sequence Diagram - Test Execution

Detailed sequence for running test cases through the Marker engine.

Sequence Diagram - Invite and Collaborate

Contributor management uses the authenticated file API. Once the saved-file editor confirms that the user is an owner or contributor, the browser connects to the Yjs room; the room connection does not replace saving a file version.

Sequence Diagram - Simulation Step

Detailed sequence of a single simulation step with multi-tape support.

State Machine Diagram - Editor Interaction Modes

The different interaction modes in the diagram editor.