@devexcelsior/healing-ui-overlay
Version:
Visual overlay component to display fallback suppression, license expiration, or runtime governance warnings in healing-enabled applications.
101 lines (64 loc) • 3.62 kB
Markdown
# @devexcelsior/healing-ui-overlay
🛡️ **Commercial license required**
📩 Contact: [curtnpuckett@gmail.com](mailto:curtnpuckett@gmail.com)
This package provides a visual overlay to warn users when healing is suppressed by governance, license, or policy.
It is used in fallback-aware UIs to maintain trust and signal runtime transparency.
## Features
- Lightweight UI component that displays suppression messages
- Supports custom messages and branding
- React-compatible with fallback-aware SDKs
- Can be toggled via session context or healing governor decisions
- Optional auto-mount mode for fail-closed UX recovery
## Use Cases
- Display “Fallback Blocked” or “License Expired” overlays
- Warn users about degraded healing capabilities in test or trial mode
- Prevent silent failure in environments where healing is unavailable
- Embed transparency messaging in compliance-sensitive products
- Improve UX clarity around healing permission or trust status
## 🧠 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.