Merge pull request #79 from Phuire-Research/UI

UI

README.md

@@ -17,7 +17,7 @@ The inspiration for STRX was that of Redux and its origin via the FLUX design pa
 * [ActionStrategy](https://github.com/Phuire-Research/STRX/blob/main/ActionStrategy.md) - Created in 2018, this is the governing concept that allows for the Unified Turing Machine to have a strong halting quality. Likewise the direct analog of higher order logic and universal transformer.
 * [Axium](https://github.com/Phuire-Research/STRX/blob/main/Axium.md) - Governing concept that contains the set of concepts that formalizes each axium.
 * [Concept](https://github.com/Phuire-Research/STRX/blob/main/Concept.md) - The programming abstraction of a concept that is decomposable to the sum of its parts via: state, qualities, principles, and mode.
-* [Stage](https://github.com/Phuire-Research/STRX/blob/main/Stage.md) - Introducing the stage design pattern. A specific helper function to prevent action overflow in action dispatches in subscriptions. 
+* [Stage Planner](https://github.com/Phuire-Research/STRX/blob/main/StagePlanner.md) - Introducing the stage planner paradigm. A specialized helper function to prevent action overflow when dispatching actions in subscriptions. 
 * [Spatial Ownership](https://github.com/Phuire-Research/STRX/blob/main/SpatialOwnership.md) - Streamlines the complex nature of the ActionStrategy as it relates to itself and other axiums. This is what allows STRX to be a graph computation paradigm.
 * [Unified Turing Machine](https://github.com/Phuire-Research/STRX/blob/main/The-Unified-Turing-Machine.md) - The governing concept for this entire framework.
 
@@ -88,7 +88,7 @@ const plan = axium.stage(
         expect(counter.count).toBe(3);
         // Comment in if testing the halting ability of log and setCount stage is commented out.
         // setTimeout(() => {done();}, 1000);
-        staged.close();
+        plan.conclude();
       } else if (
         (axiumState.lastStrategy === experimentCountingTopic ||
         axiumState.lastStrategy === experimentPrimedCountingTopic) &&

Stage.md → StagePlanner.md

@@ -1,4 +1,4 @@
-## Stage
+## Stage Planner
 ### Abstract
 This is derived from the newly created UnifiedSubject to handle the main point of vulnerability that a recursive machine carries. As the main point of dispatching new actions in the system would traditionally be informed via the subscription to listen to state changes. This Design Pattern allows one to safely dispatch in a tightly patterned subscription. This design pattern watches each stage for the potential of a runaway configuration which would normally prevent this machine from halting. But since the Unified Turing Machine was created to be halting complete. The UnifiedSubject internally watches each stage of your application independently and the actions that it dispatches via the supplied dispatch function. If a similar action is dispatched in rapid Succession denoted by its type and no debounce option. That plan will conclude and be added to the axium's badPlans property.
 
@@ -55,7 +55,7 @@ export class UnifiedSubject extends Subject<Concept[]> {
 ```
 * Dispatcher - This is the supplied dispatch function that is made available each stage.
 * Staging - The interface that you will be interacting with when setting up your stages, noting placement of concepts and the dispatch function.
-* UnifiedSubject - This is a specialized subject for utilized within STRX to allow for this staging paradigm. This is made available via the createAxium function and likewise within your principles via the concept$ property. Note that your plan will be an array of functions even with just one stage.
+* UnifiedSubject - This is a specialized subject for utilized within STRX to allow for this stage planner paradigm. This is made available via the createAxium function and likewise within your principles via the concept$ property. Note that your plan will be an array of functions even with just one stage.
 
 ## Example
 ```typescript