From e3bcefdfcb22fe50f89b6b01595ea7eaffaae134 Mon Sep 17 00:00:00 2001
From: Manfred Riem <15701806+mnriem@users.noreply.github.com>
Date: Mon, 11 May 2026 09:40:24 -0500
Subject: [PATCH] docs: remove git branch implementation detail from Article VI

Spec versioning is now tool-agnostic: 'versioned and reviewable
before acceptance' rather than prescribing branch-based workflows.
---
 spec-driven.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/spec-driven.md b/spec-driven.md
index c97439a1a..42427d81c 100644
--- a/spec-driven.md
+++ b/spec-driven.md
@@ -358,7 +358,7 @@ Governance MUST ensure:
 
 This article ensures that governance is not static and that specifications remain the authoritative source. When a gap or requirement emerges during implementation, teams may create a new specification, update an existing one, or regenerate derived artifacts—whichever approach fits their workflow—as long as the specification continues to drive implementation rather than the reverse.
 
-The constitution follows semantic versioning—major for removed or redefined principles, minor for additions, patch for clarifications. Specifications are versioned through branch-based workflows—each feature specification lives in its own branch and is reviewed and merged like code. Together, these models create an auditable trail of architectural and product decisions.
+The constitution follows semantic versioning—major for removed or redefined principles, minor for additions, patch for clarifications. Specifications must be versioned and reviewable before acceptance. Together, these practices create an auditable trail of architectural and product decisions.
 
 #### Articles VII & VIII: Simplicity and Anti-Abstraction