@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 dependency.
It enables runtime validation, audit injection, and fallback policy enforcement for agentic UI systems.

Features

• Includes the full Runtime Transparency Clause in both Markdown and programmatic formats
• Exposes clause metadata for SDKs, UIs, and compliance tooling
• Enables runtime visibility of fallback expectations for regulated environments
• Embeds easily into CI/CD, license dashboards, or healing orchestration flows
• Serves as a governance anchor for audit-based agentic infrastructure

Use Cases

• Prove compliance with fallback governance policies at runtime
• Display clause visibility in developer tools, dashboards, or agent workflows
• Gate fallback execution on policy acceptance or clause verification
• Enforce fallback IP boundaries through licensed software integration
• Lock healing access behind audit capability in sensitive environments

📜 Runtime Transparency Clause

Public clause for AI fallback infrastructure used in regulated domains

This clause defines transparency and governance expectations for any system leveraging the Healing SDK or derivative logic. It is a mandatory precondition for commercial license eligibility and applies to all agentic recovery systems deployed in production, pilot, or evaluation settings.

Clause Requirements

1. Runtime Fallback Disclosure

   • All fallback behaviors (e.g., retries, arbitration, inference-driven logic) must be disclosed during pilot and production phases.

2. Auditability Requirements

   • Healing or recovery actions must be logged, context-attributed, and auditable by internal or external parties.

3. Governance Ownership

   • A designated internal stakeholder must be responsible for:
     • Approval of fallback behavior
     • Clause and license compliance
     • Governance of any AI-infrastructure recovery logic

4. No Silent Experimentation

   • Internal proofs of concept, experiments, or orchestration patterns derived from this SDK — even without source reuse — are restricted without license.

🧱 Enforcement Boundary

Any fallback, arbitration, or healing system released after June 12, 2025 that materially reflects this clause — including telemetry expectations or audit-based fallback enforcement — is presumed derivative unless proven otherwise.

• Cleanroom mimicry, shell-vendor repackaging, or brand obfuscation do not exempt compliance.
• Use of similar patterns in production without license is a direct infringement.

This clause exists to protect strategic fallback infrastructure from being laundered through rebranding, redocumentation, or silent internal use.

🧠 Agentic Governance Backbone

Modern agentic systems require accountable, traceable recovery.
This SDK embeds the policy and enforcement model that enables it.

It forms the licensing and governance backbone for runtime-safe fallback systems.

🛡️ License

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

Use in production, hosted systems, or commercial deployments must follow one of these paths:

✅ Comply with AGPL:

• You must open source your modifications and provide them to users of your hosted service.
• Your entire stack (including orchestration logic) must be AGPL-compatible.

OR

✅ Obtain a commercial license:

• Keep your fallback and recovery logic proprietary
• Avoid open-sourcing sensitive infrastructure or agent behavior

📩 Contact: curtnpuckett@gmail.com

🚫 Prohibited Use (Without License or AGPL Compliance)

You may not use this package in systems that:

• Execute fallback, arbitration, or healing logic without AGPL compliance
• Embed clause logic or patterns into closed-source SDKs, agents, or platforms
• Replicate fallback governance behavior under alternate branding
• Rebuild this architecture via reverse engineering, shell vendors, or renamed interfaces
• Use fallback orchestration commercially without honoring AGPL terms or license agreement

Any commercial, closed-source, or obscured use is prohibited without license.

📎 Attribution & Anti-Containment Clause

The following actions require explicit attribution and licensed approval:

• Reuse of fallback trees, replay automation, arbitration logic, or signal routing
• Embedding clause logic into assistants, SDKs, runtime agents, or internal tools
• Silent internal replication under renamed wrappers or shell vendors
• Framing derivative work as original or non-associated when built atop this infrastructure

Attribution is required.
Laundering architectural IP through redocumentation or cleanroom mimicry is not permitted.

© 2025 Curt Puckett / DevExcelsior Inc.
All rights reserved across fallback infrastructure, runtime governance, agentic healing orchestration, and derivative containment enforcement.