@sdux-vault/engine 0.0.9
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/LICENSE +212 -0
- package/README.md +239 -0
- package/fesm2022/sdux-vault-engine.mjs +4069 -0
- package/fesm2022/sdux-vault-engine.mjs.map +1 -0
- package/package.json +48 -0
- package/types/sdux-vault-engine.d.ts +440 -0
package/LICENSE
ADDED
|
@@ -0,0 +1,212 @@
|
|
|
1
|
+
# NGL Commercial License 1.0
|
|
2
|
+
|
|
3
|
+
**Copyright © 2026 NextGen Luminary (“NGL”)**
|
|
4
|
+
All rights reserved.
|
|
5
|
+
|
|
6
|
+
This NGL Commercial License 1.0 (“**License**”) is a legal agreement between **NextGen Luminary**, its affiliates, or licensors (“**Licensor**”), and the individual or legal entity exercising rights under this License (“**Licensee**”).
|
|
7
|
+
|
|
8
|
+
This License governs the use of proprietary SDuX software components, including but not limited to the SDuX Engine, SDuX Engine npm distributions, SDuX Vault runtime components, and related proprietary source code, as identified and distributed by Licensor.
|
|
9
|
+
|
|
10
|
+
By installing, accessing, or using the Software, Licensee agrees to be bound by the terms of this License.
|
|
11
|
+
|
|
12
|
+
---
|
|
13
|
+
|
|
14
|
+
## 1. Definitions
|
|
15
|
+
|
|
16
|
+
For purposes of this License:
|
|
17
|
+
|
|
18
|
+
- **“Software”** means the proprietary SDuX components provided by Licensor under this License, in source code form, object code form, or binary distribution, as applicable.
|
|
19
|
+
- **“Object Code”** means compiled or executable versions of the Software, including npm-distributed binaries.
|
|
20
|
+
- **“Source Code”** means the human-readable form of the Software, where access is explicitly granted.
|
|
21
|
+
- **“Internal Use”** means use of the Software solely within Licensee’s organization for its own internal business purposes.
|
|
22
|
+
- **“Production Use”** means deployment of the Software in live, customer-facing, revenue-generating, or operational environments.
|
|
23
|
+
- **“Change of Control”** means a merger, acquisition, reorganization, or sale of substantially all assets of Licensee.
|
|
24
|
+
- **“Licensed Extension”** means a Behavior, Controller, module, or other software component that integrates with the Software and declares a runtime license requirement through SDuX Vault or related enforcement mechanisms.
|
|
25
|
+
- **“Extension Author”** or **“Vendor”** means any third party that develops, distributes, or licenses a Licensed Extension for use with the Software.
|
|
26
|
+
- **“License Payload”** means vendor-defined data supplied at runtime for purposes of validating a Licensed Extension, including but not limited to tokens, cryptographic signatures, entitlement metadata, or other opaque validation artifacts.
|
|
27
|
+
- **“Validation Result”** means the boolean approval or denial outcome reported by a Licensed Extension to SDuX Vault runtime enforcement mechanisms.
|
|
28
|
+
- **“FeatureCell”** means a discrete execution unit, pipeline element, or runtime-bound functional component within the Software that may be subject to license validation or gating behavior.
|
|
29
|
+
- **“Terminal State”** means a non-recoverable runtime condition entered following denial or failed validation that requires full reinitialization of affected components.
|
|
30
|
+
- **“Validation Timeout”** or **“License Timeout Window”** means the configured period during which a Validation Result must be reported before automatic denial occurs.
|
|
31
|
+
- **“Deterministic Enforcement”** means the intentional, programmatic license validation behavior whereby activation, denial, suspension, or terminal state transitions occur based on defined runtime rules without discretionary override.
|
|
32
|
+
- **“Runtime License Token”** means any token, key, credential, or structured data representing runtime licensing state or entitlement within the Software.
|
|
33
|
+
|
|
34
|
+
---
|
|
35
|
+
|
|
36
|
+
## 2. Grant of License
|
|
37
|
+
|
|
38
|
+
Subject to the terms and conditions of this License, Licensor hereby grants Licensee a **non-exclusive**, **non-transferable**, **non-sublicensable** license to:
|
|
39
|
+
|
|
40
|
+
- Use the Software solely in **Object Code form** (unless Source Code access is explicitly granted by Licensor);
|
|
41
|
+
- Use the Software solely for **Internal Use** and, where applicable, **Production Use** in accordance with Licensor’s commercial terms;
|
|
42
|
+
- Install and execute the Software only on systems owned or controlled by Licensee.
|
|
43
|
+
|
|
44
|
+
No rights are granted except as expressly stated in this License.
|
|
45
|
+
|
|
46
|
+
---
|
|
47
|
+
|
|
48
|
+
## 3. Third-Party Extensions and Ecosystem Separation
|
|
49
|
+
|
|
50
|
+
The Software may permit integration with Licensed Extensions developed or distributed by third parties.
|
|
51
|
+
|
|
52
|
+
Licensor:
|
|
53
|
+
|
|
54
|
+
1. Does not license, distribute, or control any Licensed Extension unless expressly identified as such;
|
|
55
|
+
2. Makes no representations or warranties regarding compatibility, functionality, entitlement correctness, security, or operational availability of any third-party Licensed Extension;
|
|
56
|
+
3. Does not validate, issue, manage, or enforce third-party commercial licenses;
|
|
57
|
+
4. Has no obligation to provide support, billing services, entitlement tracking, revenue processing, dispute resolution, or marketplace operation services for third-party Licensed Extensions.
|
|
58
|
+
|
|
59
|
+
All commercial relationships between Licensee and any Extension Author are solely between those parties.
|
|
60
|
+
|
|
61
|
+
Use of third-party Licensed Extensions is at Licensee’s sole risk.
|
|
62
|
+
|
|
63
|
+
Nothing in this License creates a partnership, joint venture, agency relationship, revenue-sharing obligation, fiduciary duty, or marketplace operator responsibility between Licensor and any Extension Author or Vendor.
|
|
64
|
+
|
|
65
|
+
---
|
|
66
|
+
|
|
67
|
+
## 4. Restrictions
|
|
68
|
+
|
|
69
|
+
Except as expressly permitted by this License, Licensee shall not, and shall not permit any third party to:
|
|
70
|
+
|
|
71
|
+
- Modify, adapt, translate, or create derivative works of the Software;
|
|
72
|
+
- Reverse engineer, decompile, disassemble, or otherwise attempt to derive source code from the Software;
|
|
73
|
+
- Redistribute, resell, lease, sublicense, or make the Software available to any third party;
|
|
74
|
+
- Use the Software to provide hosted, managed, or service-bureau offerings;
|
|
75
|
+
- Circumvent, disable, or interfere with license enforcement mechanisms or technical safeguards;
|
|
76
|
+
- Remove or alter proprietary notices, labels, or marks;
|
|
77
|
+
- Interfere with, spoof, or manipulate runtime license validation flows, including any call paths that report a Validation Result;
|
|
78
|
+
- Inject, fabricate, tamper with, or misrepresent License Payload data or Runtime License Tokens for the purpose of bypassing enforcement or causing unauthorized activation;
|
|
79
|
+
- Attempt to alter, disable, or circumvent Deterministic Enforcement, Validation Timeout behavior, License Timeout Windows, Terminal State transitions, or other defined runtime gating mechanisms;
|
|
80
|
+
- Extract, reuse, reverse engineer, or repurpose proprietary enforcement logic, telemetry systems, FeatureCell gating logic, or validation infrastructure outside the scope of authorized use under this License;
|
|
81
|
+
- Use the Software to operate, enable, or provide a competing licensing enforcement infrastructure or marketplace that derives from proprietary enforcement components of the Software.
|
|
82
|
+
|
|
83
|
+
Any use of the Software outside the scope of this License constitutes a material breach.
|
|
84
|
+
|
|
85
|
+
---
|
|
86
|
+
|
|
87
|
+
## 5. Ownership and Intellectual Property
|
|
88
|
+
|
|
89
|
+
The Software is **licensed, not sold**.
|
|
90
|
+
|
|
91
|
+
All right, title, and interest in and to the Software, including all intellectual property rights therein, are and shall remain exclusively with Licensor. Licensee acquires no ownership interest in the Software by virtue of this License.
|
|
92
|
+
|
|
93
|
+
No implied licenses are granted under any patents, copyrights, trademarks, or trade secrets of Licensor.
|
|
94
|
+
|
|
95
|
+
Nothing in this License grants any right to use Licensor’s trademarks, service marks, trade names, or branding except as necessary for truthful reference consistent with authorized use.
|
|
96
|
+
|
|
97
|
+
---
|
|
98
|
+
|
|
99
|
+
## 6. Assignment and Change of Control
|
|
100
|
+
|
|
101
|
+
This License **is assignable in its entirety**, without the consent of Licensor, **solely** in connection with a Change of Control, provided that:
|
|
102
|
+
|
|
103
|
+
1. The successor entity agrees in writing to be bound by all terms of this License; and
|
|
104
|
+
2. The assignment includes all copies of the Software in Licensee’s possession.
|
|
105
|
+
|
|
106
|
+
Any other assignment, delegation, or transfer without Licensor’s prior written consent is void.
|
|
107
|
+
|
|
108
|
+
Nothing in this section grants any right to sublicense, redistribute, or relicense the Software.
|
|
109
|
+
|
|
110
|
+
---
|
|
111
|
+
|
|
112
|
+
## 7. Compliance and Audit
|
|
113
|
+
|
|
114
|
+
Licensee agrees to use the Software in compliance with this License and all applicable laws. Licensor may, upon reasonable notice, request written certification of compliance or usage scope solely to verify adherence to this License.
|
|
115
|
+
|
|
116
|
+
Nothing in this section creates any service-level agreement, uptime commitment, validation latency guarantee, or operational availability obligation.
|
|
117
|
+
|
|
118
|
+
---
|
|
119
|
+
|
|
120
|
+
## 8. Platform Enforcement and Deterministic Operation
|
|
121
|
+
|
|
122
|
+
Licensee acknowledges that the Software includes Deterministic Enforcement mechanisms and runtime gating behavior.
|
|
123
|
+
|
|
124
|
+
Where a Licensed Extension requires runtime validation:
|
|
125
|
+
|
|
126
|
+
- Failure to report a Validation Result within the configured Validation Timeout or License Timeout Window may result in automatic denial;
|
|
127
|
+
- A negative Validation Result may cause affected runtime components, FeatureCells, or execution units to enter a Terminal State;
|
|
128
|
+
- Late Validation Results may be ignored;
|
|
129
|
+
- Terminal denial states may not be reversible without full reinitialization.
|
|
130
|
+
|
|
131
|
+
Licensee agrees that such behavior constitutes intended license enforcement and gating functionality and shall not be deemed a defect, failure of performance, service interruption, or breach of warranty.
|
|
132
|
+
|
|
133
|
+
Licensor does not guarantee validation latency, entitlement response time, network availability, or successful completion of any third-party validation process.
|
|
134
|
+
|
|
135
|
+
Licensor shall not be liable for denial, suspension, non-activation, Terminal State outcomes, or related execution impacts resulting from third-party license validation outcomes, Vendor service unavailability, License Payload errors, Runtime License Token corruption, or cryptographic implementation errors by Vendors.
|
|
136
|
+
|
|
137
|
+
Vendors are solely responsible for the secure design, implementation, and operation of their cryptographic, entitlement, and validation systems.
|
|
138
|
+
|
|
139
|
+
---
|
|
140
|
+
|
|
141
|
+
## 9. Security and Ecosystem Integrity
|
|
142
|
+
|
|
143
|
+
Licensor reserves the right, where reasonably necessary to address a material security risk, platform integrity concern, legal compliance requirement, or system stability issue, to:
|
|
144
|
+
|
|
145
|
+
1. Suspend distribution of proprietary components that present material security risk;
|
|
146
|
+
2. Issue updates that modify enforcement behavior or security posture;
|
|
147
|
+
3. Restrict compatibility with extensions that compromise security, violate documented platform policies, or materially degrade system stability.
|
|
148
|
+
|
|
149
|
+
Nothing in this section shall be interpreted as granting Licensor arbitrary termination rights unrelated to breach, nor as creating an obligation to monitor or police third-party extensions.
|
|
150
|
+
|
|
151
|
+
---
|
|
152
|
+
|
|
153
|
+
## 10. API Evolution and Compatibility
|
|
154
|
+
|
|
155
|
+
Licensor may modify internal APIs, enforcement mechanisms, runtime integration points, or compatibility requirements in future versions of the Software.
|
|
156
|
+
|
|
157
|
+
Licensor does not guarantee backward compatibility with any third-party Licensed Extension unless expressly agreed in writing.
|
|
158
|
+
|
|
159
|
+
Licensor reserves the right to publish compatibility guidelines, extension certification programs, or security requirements applicable to integrations with the Software.
|
|
160
|
+
|
|
161
|
+
---
|
|
162
|
+
|
|
163
|
+
## 11. Termination
|
|
164
|
+
|
|
165
|
+
This License shall remain in effect until terminated.
|
|
166
|
+
|
|
167
|
+
Licensor may terminate this License immediately if Licensee breaches any term of this License. Upon termination:
|
|
168
|
+
|
|
169
|
+
- All rights granted to Licensee shall immediately cease;
|
|
170
|
+
- Licensee must discontinue all use of the Software;
|
|
171
|
+
- All copies of the Software must be destroyed or permanently deleted.
|
|
172
|
+
|
|
173
|
+
Sections relating to ownership, restrictions, disclaimers, limitation of liability, governing law, and ecosystem separation shall survive termination.
|
|
174
|
+
|
|
175
|
+
---
|
|
176
|
+
|
|
177
|
+
## 12. Disclaimer of Warranties
|
|
178
|
+
|
|
179
|
+
**THE SOFTWARE IS PROVIDED “AS IS” AND “AS AVAILABLE,” WITHOUT WARRANTY OF ANY KIND.**
|
|
180
|
+
LICENSOR DISCLAIMS ALL WARRANTIES, WHETHER EXPRESS, IMPLIED, OR STATUTORY, INCLUDING BUT NOT LIMITED TO WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AND NON-INFRINGEMENT.
|
|
181
|
+
|
|
182
|
+
LICENSOR DOES NOT WARRANT THAT THIRD-PARTY LICENSED EXTENSIONS, VALIDATION SYSTEMS, ENTITLEMENT SERVICES, RUNTIME LICENSE TOKENS, OR CRYPTOGRAPHIC IMPLEMENTATIONS WILL OPERATE WITHOUT INTERRUPTION, ERROR, DENIAL, LATENCY, OR TERMINATION. LICENSOR DISCLAIMS ALL RESPONSIBILITY FOR THIRD-PARTY ENTITLEMENT SERVICES, CRYPTOGRAPHIC VALIDATION SYSTEMS, OR REMOTE LICENSE VERIFICATION INFRASTRUCTURE.
|
|
183
|
+
|
|
184
|
+
---
|
|
185
|
+
|
|
186
|
+
## 13. Limitation of Liability
|
|
187
|
+
|
|
188
|
+
TO THE MAXIMUM EXTENT PERMITTED BY LAW, IN NO EVENT SHALL LICENSOR BE LIABLE FOR ANY INDIRECT, INCIDENTAL, CONSEQUENTIAL, SPECIAL, OR EXEMPLARY DAMAGES, INCLUDING LOST PROFITS, LOSS OF DATA, LOSS OF GOODWILL, OR BUSINESS INTERRUPTION, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
|
|
189
|
+
|
|
190
|
+
LICENSOR’S TOTAL LIABILITY UNDER THIS LICENSE SHALL NOT EXCEED THE AMOUNT PAID BY LICENSEE FOR THE SOFTWARE, IF ANY, IN THE TWELVE (12) MONTHS PRECEDING THE CLAIM.
|
|
191
|
+
|
|
192
|
+
LICENSOR SHALL NOT BE LIABLE FOR ANY DAMAGES ARISING FROM THIRD-PARTY LICENSE VALIDATION FAILURE, VALIDATION TIMEOUT, ENTITLEMENT REVOCATION, LICENSE PAYLOAD MISCONFIGURATION, RUNTIME LICENSE TOKEN CORRUPTION, CRYPTOGRAPHIC IMPLEMENTATION ERRORS, OR EXTENSION-RELATED TERMINAL DENIAL EVENTS.
|
|
193
|
+
|
|
194
|
+
---
|
|
195
|
+
|
|
196
|
+
## 14. Governing Law and Venue
|
|
197
|
+
|
|
198
|
+
This License shall be governed by and construed in accordance with the laws of the jurisdiction in which Licensor is incorporated, without regard to conflict-of-law principles.
|
|
199
|
+
|
|
200
|
+
Any legal action arising out of or relating to this License shall be brought exclusively in the courts located within that jurisdiction, and the parties hereby consent to personal jurisdiction and venue therein.
|
|
201
|
+
|
|
202
|
+
---
|
|
203
|
+
|
|
204
|
+
## 15. Entire Agreement
|
|
205
|
+
|
|
206
|
+
This License constitutes the entire agreement between the parties regarding the Software and supersedes all prior or contemporaneous agreements, understandings, or communications, whether written or oral, relating to the Software.
|
|
207
|
+
|
|
208
|
+
No amendment or waiver of this License shall be effective unless in writing and signed by Licensor.
|
|
209
|
+
|
|
210
|
+
---
|
|
211
|
+
|
|
212
|
+
**END OF NGL COMMERCIAL LICENSE 1.0**
|
package/README.md
ADDED
|
@@ -0,0 +1,239 @@
|
|
|
1
|
+
# @sdux-vault/engine
|
|
2
|
+
|
|
3
|
+
> Deterministic pipeline execution, orchestration, and state management for the SDuX platform.
|
|
4
|
+
|
|
5
|
+
`@sdux-vault/engine` provides the core runtime engine for SDuX.
|
|
6
|
+
It is responsible for executing pipelines, orchestrating behaviors, and managing deterministic state transitions across the system.
|
|
7
|
+
|
|
8
|
+
---
|
|
9
|
+
|
|
10
|
+
## TL;DR
|
|
11
|
+
|
|
12
|
+
For full documentation, guides, and API references:
|
|
13
|
+
https://www.sdux-vault.com
|
|
14
|
+
|
|
15
|
+
---
|
|
16
|
+
|
|
17
|
+
## Overview
|
|
18
|
+
|
|
19
|
+
SDuX is built as a layered system:
|
|
20
|
+
|
|
21
|
+
```
|
|
22
|
+
shared → core → core-extensions → apps
|
|
23
|
+
└────────────────────→ devtools
|
|
24
|
+
```
|
|
25
|
+
|
|
26
|
+
- **shared** → contracts, types, utilities
|
|
27
|
+
- **core** → runtime engine and orchestration (this package)
|
|
28
|
+
- **core-extensions** → framework integrations (Angular, React, etc.)
|
|
29
|
+
- **apps** → end-user applications
|
|
30
|
+
- **devtools** → observability and debugging
|
|
31
|
+
|
|
32
|
+
---
|
|
33
|
+
|
|
34
|
+
## What This Package Provides
|
|
35
|
+
|
|
36
|
+
- Pipeline execution engine
|
|
37
|
+
- Behavior orchestration system
|
|
38
|
+
- Controller coordination layer
|
|
39
|
+
- Deterministic state transition processing
|
|
40
|
+
- Event-driven execution model
|
|
41
|
+
- Runtime integration foundation
|
|
42
|
+
|
|
43
|
+
---
|
|
44
|
+
|
|
45
|
+
## Key Characteristics
|
|
46
|
+
|
|
47
|
+
- ✅ Deterministic execution model
|
|
48
|
+
- ✅ Framework-agnostic architecture
|
|
49
|
+
- ✅ Composable pipeline behaviors
|
|
50
|
+
- ✅ Predictable state transitions
|
|
51
|
+
- ✅ High-performance runtime orchestration
|
|
52
|
+
|
|
53
|
+
---
|
|
54
|
+
|
|
55
|
+
## Installation
|
|
56
|
+
|
|
57
|
+
```bash
|
|
58
|
+
npm install @sdux-vault/engine
|
|
59
|
+
```
|
|
60
|
+
|
|
61
|
+
---
|
|
62
|
+
|
|
63
|
+
## Usage
|
|
64
|
+
|
|
65
|
+
### Basic Import
|
|
66
|
+
|
|
67
|
+
```ts
|
|
68
|
+
import { createVault } from '@sdux-vault/engine';
|
|
69
|
+
```
|
|
70
|
+
|
|
71
|
+
This enables:
|
|
72
|
+
|
|
73
|
+
- pipeline execution
|
|
74
|
+
- behavior orchestration
|
|
75
|
+
- controller-driven state updates
|
|
76
|
+
|
|
77
|
+
---
|
|
78
|
+
|
|
79
|
+
## Example: Creating a Vault
|
|
80
|
+
|
|
81
|
+
```ts
|
|
82
|
+
import { createVault } from '@sdux-vault/engine';
|
|
83
|
+
|
|
84
|
+
const vault = createVault({
|
|
85
|
+
// configuration
|
|
86
|
+
});
|
|
87
|
+
```
|
|
88
|
+
|
|
89
|
+
---
|
|
90
|
+
|
|
91
|
+
## How It Works
|
|
92
|
+
|
|
93
|
+
This package serves as the execution backbone of SDuX through:
|
|
94
|
+
|
|
95
|
+
- Pipeline orchestration
|
|
96
|
+
- Behavior execution sequencing
|
|
97
|
+
- Controller decision coordination
|
|
98
|
+
- State mutation management
|
|
99
|
+
|
|
100
|
+
It processes:
|
|
101
|
+
|
|
102
|
+
- incoming events
|
|
103
|
+
- pipeline stages
|
|
104
|
+
- controller decisions
|
|
105
|
+
- state updates
|
|
106
|
+
|
|
107
|
+
All in a deterministic and traceable manner.
|
|
108
|
+
|
|
109
|
+
---
|
|
110
|
+
|
|
111
|
+
## Execution Model
|
|
112
|
+
|
|
113
|
+
### Deterministic Processing
|
|
114
|
+
|
|
115
|
+
The engine ensures:
|
|
116
|
+
|
|
117
|
+
- consistent execution order
|
|
118
|
+
- predictable outcomes
|
|
119
|
+
- reproducible state transitions
|
|
120
|
+
|
|
121
|
+
---
|
|
122
|
+
|
|
123
|
+
## Pipeline Architecture
|
|
124
|
+
|
|
125
|
+
Execution is structured around:
|
|
126
|
+
|
|
127
|
+
- FeatureCell pipelines
|
|
128
|
+
- Behavior chains
|
|
129
|
+
- Controller decision layers
|
|
130
|
+
- Orchestrator coordination
|
|
131
|
+
|
|
132
|
+
---
|
|
133
|
+
|
|
134
|
+
## State Management
|
|
135
|
+
|
|
136
|
+
State transitions are:
|
|
137
|
+
|
|
138
|
+
- controlled
|
|
139
|
+
- predictable
|
|
140
|
+
- observable (via devtools)
|
|
141
|
+
- fully deterministic
|
|
142
|
+
|
|
143
|
+
---
|
|
144
|
+
|
|
145
|
+
## Environment Behavior
|
|
146
|
+
|
|
147
|
+
The engine is:
|
|
148
|
+
|
|
149
|
+
- ✅ Production-ready
|
|
150
|
+
- ✅ Framework-agnostic
|
|
151
|
+
- ✅ Compatible with SSR and browser environments
|
|
152
|
+
- ✅ Designed for both simple and complex state systems
|
|
153
|
+
|
|
154
|
+
---
|
|
155
|
+
|
|
156
|
+
## Side Effects
|
|
157
|
+
|
|
158
|
+
This package minimizes side effects and focuses on controlled execution.
|
|
159
|
+
|
|
160
|
+
All state mutations occur through:
|
|
161
|
+
|
|
162
|
+
- defined pipeline stages
|
|
163
|
+
- controlled behavior execution
|
|
164
|
+
- explicit controller decisions
|
|
165
|
+
|
|
166
|
+
---
|
|
167
|
+
|
|
168
|
+
## Development
|
|
169
|
+
|
|
170
|
+
### Build
|
|
171
|
+
|
|
172
|
+
```bash
|
|
173
|
+
npm run build:engine
|
|
174
|
+
```
|
|
175
|
+
|
|
176
|
+
Output:
|
|
177
|
+
|
|
178
|
+
```
|
|
179
|
+
dist/engine
|
|
180
|
+
```
|
|
181
|
+
|
|
182
|
+
---
|
|
183
|
+
|
|
184
|
+
## Test
|
|
185
|
+
|
|
186
|
+
```bash
|
|
187
|
+
npm run test:engine
|
|
188
|
+
```
|
|
189
|
+
|
|
190
|
+
---
|
|
191
|
+
|
|
192
|
+
## Verify
|
|
193
|
+
|
|
194
|
+
```bash
|
|
195
|
+
npm run verify
|
|
196
|
+
```
|
|
197
|
+
|
|
198
|
+
Includes:
|
|
199
|
+
|
|
200
|
+
- linting
|
|
201
|
+
- formatting
|
|
202
|
+
- type checking
|
|
203
|
+
- tests
|
|
204
|
+
|
|
205
|
+
---
|
|
206
|
+
|
|
207
|
+
## Publishing
|
|
208
|
+
|
|
209
|
+
See `RELEASE.md` for full publishing instructions.
|
|
210
|
+
|
|
211
|
+
---
|
|
212
|
+
|
|
213
|
+
## Ecosystem
|
|
214
|
+
|
|
215
|
+
- `@sdux-vault/shared` — core contracts, types, and utilities
|
|
216
|
+
- `@sdux-vault/core` — execution engine for pipelines and orchestration
|
|
217
|
+
- `@sdux-vault/addons` — optional runtime extensions
|
|
218
|
+
- `@sdux-vault/core-extensions/angular` — Angular integration layer
|
|
219
|
+
- `@sdux-vault/devtools` — observability and debugging layer
|
|
220
|
+
|
|
221
|
+
---
|
|
222
|
+
|
|
223
|
+
## Tree Shaking & Side Effects
|
|
224
|
+
|
|
225
|
+
This package is designed to be:
|
|
226
|
+
|
|
227
|
+
- tree-shakeable
|
|
228
|
+
- side-effect controlled
|
|
229
|
+
|
|
230
|
+
Only intentional execution paths trigger state changes.
|
|
231
|
+
|
|
232
|
+
---
|
|
233
|
+
|
|
234
|
+
## License
|
|
235
|
+
|
|
236
|
+
For full licensing details:
|
|
237
|
+
https://www.sdux-vault.com/docs/welcome/license#license-texts
|
|
238
|
+
|
|
239
|
+
MIT © SDuX Vault
|