solpbc.org / vit
open source is social v-it.org
0
fork

Configure Feed

Select the types of activity you want to include in your feed.

Reformat VOCAB.md as clean markdown

Jer Miller 0e4cd384 51f9e9da

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