V4.3 revision to Document Types

docs/ver4/architecture_v4.md

@@ -21,7 +21,7 @@ This document describes the production architecture of the document transcriptio
 - Freeze prompt text, prompt hash, model, and explicitly configured sampling parameters on each `Job`.
 - Preserve page-level machine output, normalized metadata, and an SDK-serialized OpenRouter response snapshot on `JobSource`.
 - Organize historical `Person` records through many-to-many Document relationships and extensible roles.
-- Classify Documents through a registry with stable type codes.
+- Classify Documents through a UUID-identified registry with unique labels.
 - Maintain human revision separately from machine-generated text.
 - Isolate page failures so multi-page jobs can complete with partial success.
 - Operate across supported platforms through Python-based application and maintenance tooling.
@@ -111,7 +111,7 @@ Responsibilities:
 - People own person records, relationship roles, document-person links, and portrait media.
 - Apply deterministic conflict handling for relationship-role writes.
 - Use set-based synchronization for many-to-many relationship updates.
-- Resolve and validate registry-backed document types.
+- Resolve and validate registry-backed document types by UUID.
 
 ### Source Media Policy
 
@@ -155,7 +155,7 @@ Responsibilities:
 ### 3. Document Type Management
 
 1. User selects a registry-backed document type for a document.
-2. Service resolves the stable type code or id.
+2. Service resolves the Document Type UUID.
 3. Persistence stores the `document_type_id` reference.
 4. Inactive types remain valid for historical rows but are excluded from default selectors.
 
@@ -171,7 +171,7 @@ Responsibilities:
 - Generic `ProcessingArtifact` records use versioned schemas, digests, and one inline or external content location.
 - `DocumentPerson` links are unique for `(document_id, person_id, role_id)`.
 - Relationship mutations are deterministic and set-based.
-- `DocumentType.code` is stable; `DocumentType.label` may evolve.
+- `DocumentType.id` is canonical identity; its unique label may evolve.
 
 ## Data Model Summary