aether-substrate docs DISCLAIMER.md
5.3 kB · 60 lines
Markdown
at main

Disclaimer #

Aether Substrate is experimental software. This document explains what that means in practice and the terms under which the project is provided. The legally binding terms are in the LICENSE (Apache License 2.0); this document is the plain-English version.

Experimental status #

Substrate is in early development. Expect:

  • Breaking changes to APIs, environment variables, schemas, and on-disk formats between versions
  • Surfaces that work today but may be removed, renamed, or restructured tomorrow
  • Rough edges, partial documentation, and bugs that have not been found yet

If you need a stable, production-grade backend, this is not it yet.

Why it's experimental — concrete risks #

Substrate is not a passive library. It runs persistent containers, executes code on your behalf, talks to third-party APIs, and can expose services beyond your local machine. You should understand the surface area before running it.

  • LLM agents execute code. The workspace and managed sandbox containers exist so that agents can run sandboxed arbitrary commands, install packages, write files, and start long-lived processes. Agents can — and occasionally will — take destructive actions: deleting files inside the workspace, exhausting disk via runaway logs, or running unbounded loops. The docker-compose.yml resource caps reduce blast radius but do not eliminate it.
  • Container resource use. The default 4 GB memory ceiling, embedding model downloads (~150 MB), Tap firehose ingestion, and workspace state can all moderate CPU, RAM, and disk on the host. Defaults are designed for a typical development machine, but your mileage may vary.
  • Networking exposure. Substrate binds to 127.0.0.1 by default, but the optional Cloudflare Tunnel and Tailscale integrations are designed to publish services beyond localhost. A misconfigured allowlist, hostname, or auth key can expose endpoints you did not intend to expose. Review your tunnel config before enabling it.
  • LLM gateway and provider spend. The gateway holds your provider credentials server-side and proxies requests to OpenAI, Anthropic, and other paid APIs. Buggy code, runaway agents, or compromised credentials can incur real charges. You are responsible for setting provider-side spend limits.
  • AT Protocol firehose ingestion. Tap can index large volumes of records to local SQLite. Disk usage grows with the number of tracked repos and time the indexer runs.
  • Third-party tools. Substrate composes Docker/Podman, Caddy, Tap, Goat, EmbeddingGemma, and various LLM provider SDKs. Each has its own bugs, security advisories, and licensing terms.

No warranty, no liability #

The 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, and non-infringement.

The authors and contributors accept no liability for any harm arising from use of this project, including but not limited to:

  • Damage to hardware (overheating, disk wear, etc.)
  • Data loss or corruption (workspace files, Tap database, embeddings, etc.)
  • Security incidents (credential leaks, unauthorized access via misconfigured tunnels, etc.)
  • Financial loss (LLM API spend, cloud egress, etc.)
  • Any other direct, indirect, incidental, special, exemplary, or consequential damages

This is the plain-English summary of Sections 7 and 8 of the Apache License 2.0. The license text is what governs in any conflict.

Your responsibilities #

By running Substrate, you accept responsibility for:

  • Securing credentials. Treat your .env, SUBSTRATE_API_KEY, LLM provider keys, and OAuth tokens as secrets. Do not commit them. Rotate them if they leak.
  • Monitoring resource use. Watch disk, RAM, and CPU on the host. Watch your LLM provider dashboards for unexpected spend.
  • Auditing exposure. If you enable Cloudflare Tunnel or Tailscale, verify that only the services you intend to publish are reachable from outside localhost.
  • Backups. Anything you cannot afford to lose — workspace files, database snapshots, exported embeddings — should be backed up independently.
  • Compliance. You are responsible for ensuring your use of Substrate (and the third-party services it talks to) complies with applicable laws and the terms of those services.

Third-party components #

Substrate composes software from many other projects. Each has its own license, terms of service, and security posture. Aether is not responsible for the behavior, availability, or terms of any third-party tool, including but not limited to: Docker, Podman, Caddy, Tap, Goat, EmbeddingGemma, OpenAI, Anthropic, Cloudflare, and Tailscale.

Reporting issues #

If you find a bug, security issue, or surprising behavior, please open an issue on the repository. We cannot guarantee a fix or a timeline, but reports help shape priorities.

License #

This software is licensed under the Apache License 2.0. You are free to use, modify, and redistribute it — including for commercial purposes — provided you preserve attribution and the license notice. The full text in LICENSE governs in any conflict between this document and the license.