From bc80753be4ed63b648fee1230110bcab2ccceed2 Mon Sep 17 00:00:00 2001
From: BREW <81044362+b-re-w@users.noreply.github.com>
Date: Sat, 3 Oct 2026 19:41:42 +0900
Subject: [PATCH] Docs: No new top-level folders without the maintainer's
 approval (#115)

---
 AGENTS.md | 10 ++++++++++
 1 file changed, 10 insertions(+)

diff --git a/AGENTS.md b/AGENTS.md
index 5bee0827..324a1bce 100644
--- a/AGENTS.md
+++ b/AGENTS.md
@@ -31,6 +31,16 @@ ask first.**
 
 Writing to *another* repository is not an exception either. Do it only when told to work there.
 
+### Do not add top-level folders
+
+**Never add a new directory (or a new file) at the repository root on your own.** The root layout is
+the maintainer's: source modules, `docs/`, `gradle/`, `.github/` and the files that tools require
+there. Work belongs inside an existing module or directory — sources under `src/<sourceSet>/`,
+CI-only scripts under `.github/scripts/`, temporary files under the git-ignored `.tmp/`. If you think
+a new top-level entry is needed, propose it (what, why, which alternatives inside existing
+directories you ruled out) and wait for approval. This was added after unapproved root folders
+(`ksp-fixtures/`, `tools/`, `kotlin-js-store/`, `iosApp/`, `sample/python`) had to be dismantled.
+
 ## 3. Worktrees link large artefacts instead of copying them
 
 A worktree is a full checkout. Copying large untracked artefacts (prebuilt runtimes, vendored trees,