open source is social v-it.org
Replace undefined 'vitizen' with 'builders' in doctrine
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) <noreply@anthropic.com>
+2
-2
+2
-2
docs/doctrine/index.html
+2
-2
docs/doctrine/index.html
···
350
350
<li>which cap inspired which remix</li>
351
351
<li>which remix became which shipped recap</li>
352
352
<li>which vet supported which vouch</li>
353
-
<li>which vitizens consistently deliver high-signal capabilities into a beacon's ecosystem</li>
353
+
<li>which builders consistently deliver high-signal capabilities into a beacon's ecosystem</li>
354
354
</ul>
355
355
<p>this is a network of causality, not clout.</p>
356
356
<p>in vit, “influence” is not follower count. influence is <strong>downstream impact with traceability</strong>.</p>
···
399
399
<p>imagine a mature vit world:</p>
400
400
<ul>
401
401
<li>every beacon has a constant stream of caps—features, fixes, tests, refactors, security hardening, performance wins.</li>
402
-
<li>vitizens become <strong>high-signal curators</strong>, not overwhelmed gatekeepers.</li>
402
+
<li>builders become <strong>high-signal curators</strong>, not overwhelmed gatekeepers.</li>
403
403
<li>everyone has their own <strong>personalized, long-lived codebases</strong> that track the evolution of their ecosystem without being hostage to it.</li>
404
404
<li>agents act as scouts and operators, but the system remains auditable and intentional.</li>
405
405
</ul>