AI Transparency
Dubby uses AI coding assistants as part of its development workflow. We believe you should know that, so this page explains what it means in practice.
How we use AI
Section titled “How we use AI”AI assists with routine software engineering tasks under human direction:
- Writing and editing code — implementing features, fixing bugs, refactoring
- Running verification — executing tests and checks to catch problems early
- Drafting documentation — writing and updating pages like this one
Every task is initiated, directed, and reviewed by a human developer. AI does not decide what to build or how the product should work.
What AI does not do
Section titled “What AI does not do”- Make product decisions. Feature direction, architecture, and design tradeoffs are human decisions. AI may surface options, but a person chooses.
- Ship code unsupervised. No AI-written code reaches production without human review. All changes go through the same automated testing and manual review process regardless of who — or what — wrote them.
- Access production systems. AI has no access to servers, databases, user data, or infrastructure.
Quality assurance
Section titled “Quality assurance”AI-assisted code is held to the same standard as any other code. Every change must pass automated testing, static analysis, and human review before it ships. We don’t lower the bar because a tool helped write it.
Why we’re open about this
Section titled “Why we’re open about this”AI-assisted development is becoming common, but not everyone talks about it. We’d rather be straightforward. You’re trusting Dubby with your media library and your home network — you deserve to know how the software is built.
Using AI doesn’t mean cutting corners. It means a small team can cover more ground — streaming pipelines, client apps across multiple platforms, metadata systems — without sacrificing the quality and attention to detail that makes self-hosted software worth running.
Questions
Section titled “Questions”If you have questions about how AI is used in Dubby’s development, open an issue on GitHub or reach out through our contact page.