48 lines
2.3 KiB
Plaintext
48 lines
2.3 KiB
Plaintext
🧾 SOFTWARE PROVIDED “AS IS” CLAUSE
|
|
📄 Disclaimer of Warranty and Liability
|
|
|
|
This software is provided “as is”, without warranty of any kind, express or implied. This includes, but is not limited to, warranties of merchantability, fitness for a particular purpose, non-infringement, and any warranties arising from course of dealing or usage of trade.
|
|
|
|
The authors and contributors make no representation or guarantee that:
|
|
|
|
the software will function uninterrupted or error-free,
|
|
builds, scheduling decisions, or execution results will be correct or deterministic,
|
|
distributed execution across heterogeneous nodes will be stable or safe in all environments,
|
|
caching, snapshotting, or replay features will not result in data loss or corruption,
|
|
integrations (including but not limited to libvirt, LXC, tmux, mosh, distcc, MinIO, Prometheus, Grafana, Forgejo, or any external toolchain) will behave as expected in all configurations.
|
|
⚙️ Operational Risk Acknowledgement
|
|
|
|
This system is capable of:
|
|
|
|
executing distributed code compilation,
|
|
scheduling workloads across physical and virtual nodes,
|
|
modifying system-level environments and build artifacts,
|
|
managing cache layers, snapshots, and execution state.
|
|
|
|
You acknowledge that:
|
|
|
|
misconfiguration may result in system instability, data loss, or resource exhaustion,
|
|
execution across remote nodes may cause unpredictable behavior under load,
|
|
performance optimization logic may prioritize throughput over safety unless explicitly configured otherwise.
|
|
🔒 No Liability
|
|
|
|
In no event shall the authors, maintainers, or contributors be liable for any:
|
|
|
|
direct, indirect, incidental, or consequential damages,
|
|
loss of data, revenue, or system availability,
|
|
hardware degradation or thermal damage,
|
|
build failures or deployment issues,
|
|
security vulnerabilities arising from system configuration or integration.
|
|
🧠 Responsibility of Use
|
|
|
|
You are solely responsible for:
|
|
|
|
validating build targets and toolchains,
|
|
verifying scheduling and execution policies,
|
|
ensuring safe node configuration and thermal limits,
|
|
reviewing cache and snapshot behavior before production use,
|
|
controlling access to the system and its APIs.
|
|
⚡ High-Risk System Notice
|
|
|
|
This software operates in a high-concurrency, distributed execution domain. It is not intended for safety-critical systems unless independently audited and hardened for such use cases.
|