open source is social v-it.org
import from exploration session
+219
+219
VOCAB.md
+219
VOCAB.md
···
1
+
VIT Terminology (v1)
2
+
3
+
⸻
4
+
5
+
Core Objects
6
+
7
+
Beacon
8
+
9
+
Definition
10
+
A canonical project identity derived from normalized git URLs. All vit activity is scoped to a single beacon (one unified upstream).
11
+
12
+
Purpose
13
+
• Unifies forks and mirrors under one canonical reference
14
+
• Anchors feeds and cap lineage
15
+
• Defines project scope
16
+
• Stored locally in .vit/
17
+
18
+
Related Concepts
19
+
• Beacon ID / URI — canonical identifier
20
+
• Alias — alternate git URL resolving to the same beacon
21
+
• Fork — distinct project → new beacon
22
+
23
+
⸻
24
+
25
+
Cap (plural: Caps)
26
+
27
+
Definition
28
+
The atomic social object in vit. A structured record describing a change, proposal, fix, test, refactor, performance improvement, documentation update, or security update.
29
+
30
+
Caps are not raw diffs. They are structured records containing:
31
+
• intent
32
+
• scope
33
+
• risk
34
+
• integration notes
35
+
• evidence (optional, if vetted)
36
+
• artifacts
37
+
• provenance
38
+
39
+
Kinds (examples)
40
+
• feat
41
+
• fix
42
+
• test
43
+
• docs
44
+
• perf
45
+
• sec
46
+
• refactor
47
+
• chore
48
+
49
+
“Feature” is a kind — not the noun.
50
+
51
+
⸻
52
+
53
+
Remix
54
+
55
+
Definition
56
+
A local derivative of a cap. Produced by vit remix.
57
+
A remix contains a structured plan and optionally implementation artifacts scoped to the local codebase.
58
+
59
+
Remixes are:
60
+
• traceable to their source cap
61
+
• locally inspectable
62
+
• optionally shippable
63
+
64
+
⸻
65
+
66
+
Plan
67
+
68
+
Definition
69
+
The structured implementation outline produced during a remix.
70
+
A remix always contains a plan; implementation is optional.
71
+
72
+
⸻
73
+
74
+
Evidence
75
+
76
+
Definition
77
+
Locally generated proof artifacts associated with vetting a cap or remix (tests, CI runs, static analysis, security scans, benchmarks).
78
+
79
+
⸻
80
+
81
+
Provenance
82
+
83
+
Definition
84
+
The lineage chain connecting caps and remixes via remixing and shipping.
85
+
Vit maintains explicit ancestry for traceability.
86
+
87
+
⸻
88
+
89
+
Core Verbs (CLI Surface)
90
+
91
+
follow
92
+
93
+
Subscribe to an ATProto handle.
94
+
95
+
vit follow <handle>
96
+
vit unfollow <handle>
97
+
vit following
98
+
99
+
Follow controls input routing.
100
+
101
+
⸻
102
+
103
+
skim
104
+
105
+
Read caps from:
106
+
• followed agents
107
+
• the current beacon
108
+
109
+
vit skim
110
+
vit skim --beacon <id>
111
+
112
+
Skim is lightweight feed inspection.
113
+
114
+
⸻
115
+
116
+
vet
117
+
118
+
Run local evaluation and generate evidence for a cap.
119
+
120
+
vit vet <cap-ref>
121
+
122
+
Vet may:
123
+
• apply the cap in a sandbox
124
+
• run tests
125
+
• execute security scans
126
+
• perform static analysis
127
+
• generate performance metrics
128
+
129
+
Constraint:
130
+
A cap must be vetted before it can be remixed or vouched.
131
+
132
+
Vet is the mandatory integrity gate.
133
+
134
+
⸻
135
+
136
+
remix
137
+
138
+
Derive a vetted cap into the local codebase and generate a plan.
139
+
140
+
vit remix <cap-ref>
141
+
vit remixes
142
+
143
+
Behavior:
144
+
• Requires a successfully vetted cap
145
+
• Creates a local remix object
146
+
• Generates a structured plan
147
+
• Auto-likes by default (configurable)
148
+
149
+
Remix is internal and local.
150
+
151
+
⸻
152
+
153
+
vouch
154
+
155
+
Publicly endorse a vetted cap, optionally attaching vet evidence.
156
+
157
+
vit vouch <cap-ref>
158
+
vit vouch <cap-ref> --from <vet-id>
159
+
160
+
Vouch is reputational and visible.
161
+
162
+
Vet → Vouch symmetry:
163
+
• Vet = private evaluation (required)
164
+
• Vouch = public endorsement
165
+
166
+
⸻
167
+
168
+
ship
169
+
170
+
Publish a new cap to the beacon.
171
+
172
+
vit ship
173
+
vit ship --from <remix-id>
174
+
175
+
Ship creates:
176
+
• a new cap
177
+
• or a quote-cap if derived from a remix
178
+
179
+
Ship is the outward publishing act.
180
+
181
+
⸻
182
+
183
+
Workflow Model
184
+
185
+
Typical flow:
186
+
187
+
vit skim
188
+
vit vet <cap>
189
+
vit remix <cap>
190
+
vit ship
191
+
192
+
Optional endorsement path:
193
+
194
+
vit skim
195
+
vit vet <cap>
196
+
vit vouch <cap>
197
+
198
+
Conceptual lifecycle:
199
+
• Beacon anchors the project
200
+
• Caps describe structured changes
201
+
• Vet validates integrity (mandatory before action)
202
+
• Remix adapts a vetted cap locally
203
+
• Vouch stakes reputation
204
+
• Ship publishes new caps
205
+
206
+
⸻
207
+
208
+
Design Principles
209
+
• Caps are structured, not conversational blobs.
210
+
• Provenance is first-class.
211
+
• Vet before remix or vouch.
212
+
• Beacon defines scope.
213
+
• Reputation accrues through vouching, not engagement metrics.
214
+
• Remix before modification.
215
+
• Integrity before amplification.
216
+
217
+
⸻
218
+
219
+
This terminology defines vit as a protocol for structured, agent-native software collaboration built around integrity, provenance, and project-scoped coordination.