diff --git a/README.md b/README.md
index d1441e5..c03a7fa 100644
--- a/README.md
+++ b/README.md
@@ -202,14 +202,13 @@ Below are special definitions that are used for tagging purposes.
 
 ![Permissive AI policy](./badges/permissive-ai-policy-orange.svg)
 
-A policy that permits the use of AI/LLMs in any capacity or is declared to be [vibecoded](#vibecode). Both vibecoding and opening the door for people to vibecode count as a permissive AI policy.
+A policy that permits the use of AI/LLMs in any capacity. Opening the door for people to vibecode counts as a permissive AI policy.
 
 Evidence can be:
 
 - an explicit AI policy (e.g. `AI_POLICY.md`, `CONTRIBUTING.md`, developer docs) in the repo or something in the project's contributing guidelines or in their website's documentation that says that AI/LLMs are allowed
 - an LLM friendly `AGENTS.md`, `CLAUDE.md`, or other such LLM instruction files or folders.
-- core maintainers' blog or social media post about vibecoding
-- link to readme, website, or documentation stating the project is vibecoded
+- core maintainers' blog or social media post about using AI/LLMs
 
 > [!Important]
 > If a core maintainer has noted that the code is entirely vibecoded, please use the ![Vibecoded](./badges/vibecoded.svg) instead. That tag is specifically meant for extreme cases only.
@@ -227,9 +226,12 @@ The term was coined by [Andrej Karpathy](https://en.wikipedia.org/wiki/Andrej_Ka
 > [!tip]
 > Humans reviewing vibecoded code does not disqualify said code from being considered vibecoded.
 
+Sometimes people will refer to vibecoding as "agenic engineering". We will not be using that term in this repo, but that still counts for this tag's usage.
+
 Evidence can be:
 
 - blog post stating the project was vibecoded
+- link to readme stating that the project was vibecoded.
 - contributing/developer docs *requiring* the usage of AI
 
 > [!Important]