Around VCDesign
Related projects
Practices and tools around VCDesign. Each has its own norms in its own repository; they are not VCDesign specifications.
Status labels: consistent with v2 means no conflict with v2 vocabulary; v1 vocabulary means the material is still written in v1 terms. See the migration table to read v1 terms.
-
VC-AD
Evolving in its own repository
A development protocol for AI-driven coding in which decisions, contracts, connections and scope are handed to AI as YAML, so that humans keep the core of design and responsibility.
"VCDesign is law; VC-AD is its implementation at the current technical level." (VCDesign README)
-
TDDD
Independent practice record
TODO Driven Development: an operating record of development in the generative-AI era that preserves decisions rather than code.
-
Value Review
v1 vocabulary
A review sheet (L1–L4) for deciding, before implementation, which value is protected inside which boundary. In v2 the judgment gate and the canonical Review Output play this role.
-
VMS / VMS Marketing
v1 vocabulary
An operating protocol that translates management and marketing concerns into loops, boundaries and decisions to design responsibility and value continuity.
-
Re-derivation Layer
Consistent with v2
A layer that makes a robot's or machine's action explainable afterwards as responsibility and business meaning (physical AI and OT). The v2 glossary places it under "pass on".
-
Continuity Claim Protocol
Consistent with v2
A protocol for declaring identity, boundary, authority and signature before crossing into another organization or agent. Referenced by the boundary pattern's
external_crossing. -
idk-lamp.org
Consistent with v2
An everyday entry point: giving AI an "I don't know" lamp. It explains, with familiar stories, the idea that a guard which cannot decide stops and escalates as unknown.