VMS
VCDesign Management Strategy
VMS is an operating protocol for translating management concerns into VCDesign Loops, Boundaries, and Decisions, so responsibility and value continuity can be designed explicitly.
Contents
Purpose
VMS exists to clarify where responsibility lives in management decisions and to maximize the continuity of business value.
AI may present alternatives, but final closure always remains with the manager. VMS preserves that premise and closes each consultation as Boundary, Metrics, and Decision.
Monetary
Capital circulation and business continuity. Whether money remains and the business can continue.
Cultural
The history, aesthetics, and cultural value of the domain that must be protected.
Generative
Whether skills, spirit, and decision logic can be handed to the next generation.
Symptom Mapping
The first step is to classify a concern by Loop. This classification is not the answer; it is the entry point for deciding which responsibility boundary to inspect.
Physical Loop
Symptoms: no money left / cash flow is tight
Connects to Unit Economics, Throughput Accounting, and related frames.
Semantic Loop
Symptoms: products do not sell / competitors are winning
Connects to JTBD, Value Proposition Canvas, and related frames.
Value Loop
Symptoms: no passion / unclear reason for continuing
Connects to Ikigai, Purpose-Driven Management, and related frames.
Responsibility Loop
Symptoms: nothing runs without me / successors are not growing
Connects to Generativity, DACI, and related frames.
The first three questions
- current_pain: What is the hardest thing right now?
- desire: What would count as success?
- constraints: Where are the limits of time, money, and mental energy?
Operation
Mode Selection
Maintain
Closure Mode. Protect boundaries and close responsibility.
Expand
Exploration Mode. Rediscover structure and test new hypotheses.
Ambiguous
Diagnostic Exploration. Structure discomfort and bridge it toward Closure.
First Session
- Enter the current symptom and identify the closest Loop
- Set survival boundaries for cash, mind, and aesthetics
- Generate the first Decision for the immediate concern
- Select one Metric to monitor at the next review
Minimum Output
Do: - Concrete actions to take Don't: - Things to stop immediately Outcome: - The drift expected to improve boundary_definition: - Boundaries created or updated in this decision metrics_to_watch: - Value Drift / Boundary Invasion / Responsibility Deadlock decision_log: owner: final decision owner status: Instant / Pending / Discard closure_check: which Loop this decision closes
Domain Extensions
VMS is the entry point for management judgment. Domain-specific consultations are handled as knowledge extensions while preserving VMS responsibility principles.
Resources
VMS is not just reading material. It is a specification to pass to AI. Provide the minimum reading set, then enter the management concern as a symptom.
Minimum Reading Set for AI
specs/VMS.yamldecision principles, value definitions, responsibility placementspecs/prompt.txtbase instruction for AIspecs/Input_Interface.yamlsymptom classification and missing contextspecs/Mode_Switcher.yamlmode selectionspecs/Output_Structure.yamloutput formatspecs/User_Role_Definition.yamloutput granularity by user level