Skip to content

Commit 6cc32d0

Browse files
committed
content: Rework LLM policy
Signed-off-by: James Calligeros <jcalligeros99@gmail.com>
1 parent babf005 commit 6cc32d0

2 files changed

Lines changed: 37 additions & 85 deletions

File tree

‎content/llm-policy.md‎

Lines changed: 37 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,37 @@
1+
---
2+
title: Generative AI Policy
3+
date: "2026-09-08T09:00:00+10:00"
4+
draft: false
5+
aliases:
6+
/slop
7+
---
8+
9+
Generative AI tools using large language models (LLMs) are widespread
10+
in software development today. While we acknowledge that these tools
11+
do have uses cases, LLMs engender harms to the pillars of Asahi Linux:
12+
software freedom, the open-source community, the open Internet, the
13+
environment, digital privacy, user consent, and software developers
14+
themselves. For more information on the ethical issues of LLM use
15+
in open source, we recommend reading [SourceHut's policy](https://sourcehut.org/blog/2026-08-27-tos-changes-and-llms/)
16+
17+
Furthermore, Asahi Linux relies on [clean room reverse engineering](https://asahilinux.org/copyright)
18+
to ensure our work is legal. We have strict guardrails around
19+
binary disassembly and decompilation, and we absolutely forbid
20+
the use of leaked materials. While general questions around
21+
LLMs and copyright remain unsettled, LLMs pose unique legal risks to
22+
reverse engineering projects, as these systems are likely to violate
23+
the clean room requirements and taint the resulting code. This risk
24+
is amplified with "agentic" approaches, where the human may
25+
be unaware of the reverse engineering process. In reverse engineering
26+
and science _how_ knowledge is obtained is just as important as the
27+
knowledge itself.
28+
29+
Due to these legal and ethical issues, we broadly forbid the use of
30+
generative AI tooling for material contributions to Asahi Linux.
31+
Enforcement may vary depending on the seriousness of the infraction.
32+
A GitHub issue drafted by an LLM may simply be closed with reference
33+
to this policy. A contributor using an LLM to interpret a trace
34+
made using the m1n1 hypervisor may be issued with a first and final
35+
warning. A contributor found to have concealed extensive LLM use will
36+
be banned immediately, particularly if they may have accessed unreleased
37+
Apple material.

‎content/slop.md‎

Lines changed: 0 additions & 85 deletions
This file was deleted.

0 commit comments

Comments
 (0)