@devexcelsior/healing-geo/README.md

Location-aware healing instruction logic for resilient UI recovery

# @devexcelsior/healing-geo

🛡️ Commercial license required  
📩 Contact: curtnpuckett@gmail.com

This package enables location-aware healing behavior in UI recovery systems.

Use it to route recovery instructions based on:

- Device location
- Region-specific fallbacks
- Geofenced workflows
- Contextual UI overrides in field deployments

---

## Features

- Inject healing logic based on geolocation
- Works with `@devexcelsior/healing-sdk-core`
- Extendable with mobile and kiosk-specific logic
- Minimal runtime footprint

---

## Use Cases

- Kiosk-based error handling (location-dependent)
- Field units triggering unique healing flows
- Geo fallback: if in clinic X, use instruction Y
- Compliance workflows triggered by region


---


## 🧠 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.