1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
/// The `manager` module serves as an organizational component within the application.
///
/// This module can encompass functionalities or utilities specifically aimed at managing
/// and coordinating various aspects of the system. It could include handling resources,
/// configurations, workflows, or other management-related tasks.
///
/// The functions and structures within this module should be designed to streamline
/// the management of the application logic and ensure reusability, scalability, and
/// maintainability of the codebase.
///
/// Example Usage:
///
/// ```ignore
/// use crate::manager;
/// // Access functions and structures defined in the `manager` module
/// ```
///
/// Ensure that all submodules or functionalities added to this module are well-documented
/// and adhere to the established coding conventions.
/// The `manager_v2` module owns the lifecycle of v2 rolling simulations:
/// the simulation store, the per-simulation factor tapes, and the bounded
/// snapshot cache. It is the only thing the api layer talks to for v2.
/// The `model` module is typically used to define and manage the core
/// data structures and associated logic used by the application.
///
/// This module may include definitions for application-specific models,
/// such as structures representing entities or components, and may also
/// implement traits or methods for processing or manipulating these models.
///
/// Ensure that this module adheres to the application’s domain requirements
/// and is used effectively for encapsulating the core business data.
///
/// The `model_v2` module defines the v2 rolling-simulation session types:
/// the resolved simulation parameters, the simulation document, and the
/// conversion from the v2 request DTO. Kept apart from `model` because
/// `/api/v1/chain` and its stored shape are frozen (ADR 0001 section 12).
/// The domain snapshot in the shape the ClickHouse warehouse stores, and the
/// tape generation it is filed under.
///
/// The `state_handler` module is responsible for managing and encapsulating all
/// logic related to the application state. It defines functionality to manipulate,
/// update, and retrieve the current state of the application.
///
/// This module is designed to provide a clear separation of concerns, handling
/// state-specific logic independently of other components in the project. It may
/// include state transitions, validation, and utility methods for accessing state
/// information.
///
/// Ensure that this module is imported and utilized whenever the application
/// needs to interact with or modify its state.
///
/// Additional Notes:
/// - This module provides abstractions to ensure consistency in state management.
/// - Error handling and validation mechanisms may be included to handle invalid
/// state transitions and ensure the integrity of the state.
///
/// This module, `store`, encapsulates the functionality and implementation for
/// managing and interacting with a storage system. It can be used for storing,
/// retrieving, and processing various types of data based on the specific implementations
/// provided within this module.
///
/// Typically, the `store` module may include submodules, structs, traits, or functions
/// to support operations such as:
/// - Reading from and writing to the store.
/// - Managing the lifecycle of stored data.
/// - Querying and updating data.
///
/// Users of this module should refer to its public items to utilize its functionality effectively.
pub use crate;
pub use SessionManager;
pub use SimulationManager;
pub use ;
pub use ;
pub use ;