bbchops/transcription
1
0
Fork 0
generated from john/python-template
Code Issues 4 Pull Requests Actions Packages Projects Releases Wiki Activity

V4 final docs

Browse Source
This commit is contained in:
Jim Lancaster
2026-08-10 12:34:36 -05:00
parent 4b3baf5a3e
commit ccf2c78ff4
7 changed files with 24 additions and 43 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/ver4/implementation_plan_v4.md
+5 -5
View File
@@ -13,7 +13,7 @@ Implement the Version 4 project definition from the current repository state whi
## Current Project Impact
- `src/transcription/db/models.py` requires full schema alignment with the V4 core documents.
- `src/transcription/services/documents.py` requires set-based document-person sync, exclusivity checks, and document-type resolution.
- `src/transcription/services/documents.py` requires set-based document-person sync and document-type resolution.
- API modules require additive role-aware relationship behavior and document-type selection behavior.
- UI pages require grouped role displays, multi-role editing, and registry-backed document-type selection.
- Existing tests require updates for role enforcement, document-type selection, and regression safety.
@@ -29,7 +29,7 @@ Implement the Version 4 project definition from the current repository state whi
### 2. Align the Persistence Layer
- Update SQLModel definitions to match the final V4 schema.
- Add `person_role`, `role_exclusivity`, and `document_type` support.
- Add `person_role` and `document_type` support.
- Replace legacy document-type storage with `document_type_id`.
- Apply the accepted manual exception strategy for `document_type` and `document_person` data.
- Preserve all other data structures non-destructively.
@@ -37,7 +37,7 @@ Implement the Version 4 project definition from the current repository state whi
### 3. Update Services and Write Semantics
- Implement set-based synchronization for document-person updates.
- Implement deterministic exclusivity conflict checks.
- Implement deterministic uniqueness and relationship-write conflict checks.
- Remove suggestion-related service behavior.
- Add document-type resolution and validation by stable code or id.
@@ -57,7 +57,7 @@ Implement the Version 4 project definition from the current repository state whi
### 6. Verification and Hardening
- Add or update service tests for many-per-role behavior, exclusivity enforcement, and set-based sync correctness.
- Add or update service tests for many-per-role behavior, uniqueness conflict handling, and set-based sync correctness.
- Add API tests for relationship behavior and document-type selection.
- Add UI tests or walkthrough coverage for grouped roles and type selection.
- Add regression coverage for delete and cleanup semantics.
@@ -66,7 +66,7 @@ Implement the Version 4 project definition from the current repository state whi
- Core V4 documents and code paths agree on the final project definition.
- Relationship-role writes are deterministic and non-destructive.
- Exclusivity rules are enforced consistently.
- Relationship-write conflict rules are enforced consistently.
- Document type selection is registry-backed.
- The accepted manual exceptions for `document_type` and `document_person` are completed.
- The focused test coverage passes.