VCDesign

(Value Continuity Design)

VCDesign (Value Continuity Design).
Defining design principles not for "how to build", but for how to protect the value after creation over time.

VCDesign Constitution

Article 1: Continuity of Value

The purpose of a system is not the preservation of function, but the continuity of value.

When value is impaired, the system is obligated to transform itself starting from Delta.

Article 2: Locality of Responsibility

Every behavior must belong to a Chapter that takes responsibility for it.

Leaving a state of unclear responsibility (`owner_missing`) unresolved means the death of the system.

Article 3: Human Sovereignty

AI and automation may assist judgment, but they do not bear responsibility.

Final determination of meaning and structural changes (Reframe / Retire) must always be led by humans and remain explainable.

VCDesign Manifesto

1. Embrace Finite Chapters

A Chapter is not an immutable truth.

Through divergence from reality and accumulation of Delta, every Chapter will eventually drift.

Change is not failure. It is the precondition for Reframe in order to sustain value.

2. Do Not Hide Delta, Celebrate the Signal

Delta is the entry point to evolution.

Use responsibility metrics to observe unease and declare drifting.

Observed abnormality must take priority over silent normality.

3. Prefer Consistency for the Future over Loyalty to the Past

A Decision Log is not a replay of the past, but a record of Purpose Linkage.

Every judgment carries accountability to the future.

4. Close Responsibility, or Send It Upward

Ambiguous responsibility degrades the system.

If it can be resolved, Fix it. If it cannot, Defer it.

Holding responsibility indefinitely without action is prohibited.

5. Retire Meaningless Automation

Chapters, code, and data that no longer create value must not be maintained.

Through Value Review, give Retire to structures whose role has ended.

Not continuing is also a form of design.

VCDesign Overview

VCDesign is a set of specifications not for "how to build" a finished system, but for
how to design so that a system's value does not get lost over time during operation.

VCDesign Core is a development OS for value continuity. It structures systems through transitions of Chapters and Responsibilities.

"Sustaining value" means embedding this obvious cycle into design:

Clarify the expected value at design time
Check whether the current state still preserves that expectation
If it doesn't, improve it. If you can't, let it go.

Primitives

Chapter: The unit of responsibility allocation for sustaining value
Responsibility: The actor and placement that make a Chapter viable
Delta: A sign that the conditions of a Chapter or its responsibility allocation are no longer holding
Action: Four action types: Fix, Reframe, Defer, Retire

PDΔA Flow

Systems protect value continuously through the cycle of Precondition → Do → Delta → Action.

Responsibility Model

Every Chapter requires an Owner, Supporters, and a Final Decider. The Final Decider must always be human.

Core Metrics and Policies

Core Metrics are indicators for detecting misalignment in responsibility, such as Owner Missing and AI Overreach.

Policies define AI judgment constraints and the control of Reframe. AI cannot hold final authority; humans carry responsibility.

Refer to Specs

Specs are not for reading, but "tools" for design and implementation support.
When passing them to generative AI, the YAML Index links are the shortest path.

2026 Implementation (value-review, VC-AD, TDDD)

Research & Analysis

Third-party research, analytical reviews, and independent evaluation materials regarding VCDesign.

* These metrics and research materials are propositional and exploratory, and do not indicate formal definitions or pass/fail judgments.