JSPM

@devexcelsior/runtime-transparency-clause

0.0.3
  • ESM via JSPM
  • ES Module Entrypoint
  • Export Map
  • Keywords
  • License
  • Repository URL
  • TypeScript Types
  • README
  • Created
  • Published
  • Downloads 22
  • Score
    100M100P100Q11134F
  • License BUSL-1.1

Runtime Transparency Clause enforcement and attribution module for agentic fallback systems. Includes governance terms, commercial notice, and audit conditions required for licensing compliance.

Package Exports

  • @devexcelsior/runtime-transparency-clause
  • @devexcelsior/runtime-transparency-clause/dist/index.js

This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (@devexcelsior/runtime-transparency-clause) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.

Readme

@devexcelsior/runtime-transparency-clause

🛡️ AGPL-3.0-only license
📩 Commercial inquiries: curtnpuckett@gmail.com

This package declares the Runtime Transparency Clause as a software-enforceable licensing requirement.
It enables runtime validation, audit injection, and policy enforcement for agentic fallback systems.

Features

  • Bundles the full Runtime Transparency Clause as Markdown and runtime-accessible text
  • Provides programmatic access to clause metadata for SDK and UI integration
  • Enables visibility and enforceability of fallback audit expectations
  • Embeddable into CI/CD, compliance dashboards, or runtime healing infrastructure
  • Acts as a licensing witness module in regulated environments

Use Cases

  • Prove adherence to fallback governance terms at runtime
  • Inject clause visibility into devtools, dashboards, or agent UIs
  • Lock fallback or healing execution behind clause validation
  • Protect fallback clause IP via enforceable software dependency
  • Gate agent orchestration or recovery automation on runtime audit compliance

📜 Runtime Transparency Clause

Public Transparency Clause for High-Regulation AI Integrations

This clause formalizes the expectation that any organization pursuing a license for the Healing SDK (or related systems) must adhere to baseline transparency standards around fallback behavior, runtime governance, and auditability.

It is a precondition for evaluation, piloting, or integration of any self-healing, agentic, or recovery-aware UI system offered under commercial license.

Clause Requirements

  1. Runtime Fallback Disclosure

    • All fallback behaviors (e.g. retries, LLM arbitration) must be documented and disclosed during pilot and production phases.

  2. Auditability Requirements

    • Healing and recovery actions must be telemetrically logged, runtime-attributable, and auditable by internal or external review.

  3. Governance Ownership

    • An internal stakeholder must be assigned for:
      • Recovery logic oversight
      • Clause and license conformance
      • Agentic governance accountability

  4. No Silent Experimentation

    • Internal POCs, agent orchestration, or fallback patterns derived from this SDK — even without source reuse — violate licensing intent if unlicensed.

Enforcement Boundary

Any fallback governance, telemetry, or agent orchestration system materially resembling this clause — released after June 12, 2025 — will be considered presumptively derivative unless proven independently developed.

Unauthorized replication through shell vendors, alternate naming, or rebranded tooling will trigger full IP enforcement.

This boundary ensures foundational fallback infrastructure is not silently absorbed or relabeled without license.

🧠 Agentic Governance Backbone

Runtime AI systems require transparent, auditable fallback.
This SDK embeds the governance clause that enables that.

It is the backbone of regulated self-healing infrastructure.

🛡️ License

This package is licensed under the GNU Affero General Public License v3.0 only (AGPL-3.0-only)

Use in production, hosted services, or commercial applications without AGPL compliance requires a commercial license.

  • If you modify and use this in a hosted service: you must open source your modifications under AGPL, or obtain a license.
  • You may not replicate fallback orchestration, arbitration, or replay behavior in proprietary infrastructure without permission.

📩 To request a commercial license: curtnpuckett@gmail.com

🚫 Prohibited Use (Without License)

This package may not be used in systems that:

  • Execute fallback in production environments
  • Automate recovery logic via inference or replay
  • Implement trust-weighted arbitration or signal routing
  • Replicate fallback clause architecture in devtools, agents, or SDKs
  • Rebuild functionality via reverse engineering or “cleanroom” mimicry

All derivative behavior — even under alternate names — remains protected.
Commercial license required for all non-AGPL use.

📎 Attribution & Anti-Containment Clause

The following behaviors require explicit attribution and licensing:

  • Reuse of fallback trees, arbitration logic, or replay sequences
  • Shell-vendor repackaging or silent internal use
  • Embedding clause logic in assistants, SDKs, or edge runtimes
  • Framing this architecture as independent or open source if derived

You may not strip attribution, rename clause logic, or obscure origin.

© 2025 Curt Puckett
All rights reserved across fallback infrastructure, healing orchestration, and agentic runtime systems.