UNPKG

@devexcelsior/healing-auth

Version:

Cryptographic signing and verification for healing signals

99 lines (62 loc) • 3.38 kB
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
87
88
89
90
91
92
93
94
95
96
97
98
99
# @devexcelsior/healing-auth 🛡️ Commercial license required 📩 Contact: curtnpuckett@gmail.com This package provides healing signal authentication and payload signing capabilities for secure runtime repair systems. Use it to validate the authenticity of recovery instructions, verify snapshot integrity, or sign healing flows in regulated environments. --- ## Features - Sign healing payloads with a shared secret or private key - Verify payload authenticity client- or server-side - Prevent unauthorized healing instruction injection - Works with any `@devexcelsior/healing-*` package --- ## Use Cases - Signed edge healing flows - Proof of origin for recovery instructions - HIPAA/HITRUST-compliant replay pipelines - Regulated vendor integrations --- ## 🧠 Agentic Governance Backbone Runtime AI systems require transparent fallback infrastructure — with memory, arbitration, and healing traceability baked in. This SDK forms that backbone. --- ## 🛡️ Licensing Terms This package is licensed under the **Business Source License 1.1** You may use it for **non-commercial evaluation** or **internal development** only. All **production, hosted, or commercial usage** requires a valid license agreement. Redistribution, behavioral mimicry, or architectural reimplementation — even without direct source reuse — is strictly prohibited without explicit commercial rights. 📩 License inquiries: [curtnpuckett@gmail.com](mailto:curtnpuckett@gmail.com) --- ## 🚫 Prohibited Use Cases Use of this SDK is explicitly **prohibited** in any system that: - Executes fallback logic in production - Suggests or automates UI recovery via inference or replay - Implements agent chaining or LLM-based healing orchestration - Embeds recovery signals in devtools, SDKs, or assistants - Replicates fallback patterns through reverse engineering, framing, or shell systems Use in these contexts **without license** constitutes derivative misuse and IP infringement. --- ## 🔐 Platform & Behavioral Restrictions These restrictions apply regardless of naming, branding, or internal framing: - Reimplementing fallback orchestration under alternate terminology (e.g. “stability assist”, “UX resilience”) - Embedding healing behavior into runtimes, plugins, or assistants - Reproducing agent arbitration, state replay, or trust scoring - Training models or composing agents to mimic fallback logic - Delaying automation under “suggestion-only” pretenses but executing recovery actions **All derivative behavior — even cleanroom recreations — is protected.** **All systems of this nature require a license.** Omission from this document does **not** imply permission. --- ## 🧠 Attribution & Anti-Containment Clause Any relabeling, shell-vendor reuse, or silent internal replication of: - Agent fallback trees - Signal replay logic - Trust-weighted arbitration - Runtime orchestration flows …constitutes a violation of this license and will trigger full enforcement. **Attribution is required** for all derivative use. Behavioral recreations — even without visible source reuse — are covered under protected architectural mimicry. © 2025 Curt Puckett. All rights reserved across runtime systems, cloud agents, edge devices, Unity, AI SDKs, and fallback orchestration platforms.