V4 final docs

docs/ver4/scope_boundary_v4.md

@@ -12,7 +12,6 @@ Define what this revision includes, what it intentionally excludes, and what mig
 
 - Extensible role taxonomy for document-person relationships.
 - Many-to-many document-person links with many people per role.
-- Deterministic exclusivity policy for configured role pairs.
 - Set-based add/remove synchronization for document-person updates.
 
 ### 2. Document Type Governance
@@ -30,7 +29,6 @@ Define what this revision includes, what it intentionally excludes, and what mig
 ### 4. Verification
 
 - Tests for many-per-role behavior.
-- Tests for exclusivity enforcement.
 - Tests for set-based relationship mutation behavior.
 - Tests for document and person delete/link cleanup regressions.
 
@@ -49,23 +47,18 @@ Define what this revision includes, what it intentionally excludes, and what mig
 
 - Use registry tables for relationship roles.
 
-### B. Exclusivity Matrix Baseline
-
-- `author` and `recipient` are mutually exclusive for the same `(document, person)` pair.
-- `mentioned` remains non-exclusive.
-
-### C. API Compatibility Strategy
+### B. API Compatibility Strategy
 
 - Use additive API evolution.
 - In development mode, the current revision is authoritative.
 - Deprecations should be explicit and short-lived.
 
-### D. Document Type Rollout Strategy
+### C. Document Type Rollout Strategy
 
 - Use a minimal registry rollout for the current corpus.
 - Do not introduce a `document_type_alias` helper table.
 
-### E. Database Change Policy
+### D. Database Change Policy
 
 - Future schema changes are non-destructive by default.
 - Exception: `document_type` text may be replaced by `document_type_id` without migrating the legacy text values.
@@ -81,7 +74,8 @@ Define what this revision includes, what it intentionally excludes, and what mig
 
 V4 scope is considered frozen when:
 
-- Relationship model, exclusivity rules, and document-type governance are approved.
+- Relationship model and document-type governance are approved.
+- Relationship model and document-type governance are approved.
 - Additive API change list and deprecation schedule are approved.
 - Migration exceptions are explicitly acknowledged.