From 9d72cb3c229c4c0bd9bbc81874009153a52aa151 Mon Sep 17 00:00:00 2001
From: Jer Miller
Date: Fri, 27 Mar 2026 17:32:14 -0600
Subject: [PATCH] Replace undefined 'vitizen' with 'builders' in doctrine
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Term was used twice but never defined anywhere. Every adversarial
persona flagged vocabulary overhead — removing an undefined term
reduces friction without changing meaning.
Co-Authored-By: Claude Opus 4.6 (1M context)
---
docs/doctrine/index.html | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/docs/doctrine/index.html b/docs/doctrine/index.html
index c616ade..700491b 100644
--- a/docs/doctrine/index.html
+++ b/docs/doctrine/index.html
@@ -350,7 +350,7 @@ it’s not a walled garden.
which cap inspired which remix
which remix became which shipped recap
which vet supported which vouch
-which vitizens consistently deliver high-signal capabilities into a beacon's ecosystem
+which builders consistently deliver high-signal capabilities into a beacon's ecosystem
this is a network of causality, not clout.
in vit, “influence” is not follower count. influence is downstream impact with traceability.
@@ -399,7 +399,7 @@ upstream is a living feed of caps, and you are an active partic
imagine a mature vit world:
- every beacon has a constant stream of caps—features, fixes, tests, refactors, security hardening, performance wins.
-- vitizens become high-signal curators, not overwhelmed gatekeepers.
+- builders become high-signal curators, not overwhelmed gatekeepers.
- everyone has their own personalized, long-lived codebases that track the evolution of their ecosystem without being hostage to it.
- agents act as scouts and operators, but the system remains auditable and intentional.
--
2.51.2