error_handling.md added

docs/mvp.md

@@ -24,7 +24,7 @@ The MVP deliberately defers full-text search, export, revision history, MongoDB,
 | UI views for status and transcript reading | REQ-5 | The user needs to see what happened. |
 | Background processing to keep UI responsive | REQ-6 | Essential for usability during long AI calls. |
 | Centralized config and logging at startup | REQ-8 | Small effort, high payoff for debugging. |
-| Store transcription prompts as Markdown files | REQ-12 | Core to the Prompt Curation Policy in Intent.md. Start with a single prompt file. |
+| Store transcription prompts as Markdown files | REQ-12 | Core to the Prompt Curation Policy in intent.md. Start with a single prompt file. |
 
 
 ### Deferred to Post-MVP
@@ -52,7 +52,7 @@ The MVP deliberately defers full-text search, export, revision history, MongoDB,
     5. On failure: saves the error detail, transitions to failed.
 
 #### Feature 3: Transcription Prompt (Markdown Asset)
-* A single Markdown file (prompts/transcribe_document.md) encoding the verbatim transcription rules from Intent.md (the Document Issues table, scholarly guidelines, etc.).
+* A single Markdown file (prompts/transcribe_document.md) encoding the verbatim transcription rules from intent.md (the Document Issues table, scholarly guidelines, etc.).
 * The worker reads this file at invocation time and injects it as the system/user prompt.
 
 #### Feature 4: Job Status & Transcript Viewer (UI)
@@ -163,7 +163,7 @@ The MVP is considered validated when:
 1. ✅ A user can upload an image of a document through the browser.
 2. ✅ The system asynchronously sends the image to the configured AI vision model with the curated prompt.
 3. ✅ The transcript (or failure reason) is persisted and visible in the UI.
-4. ✅ The transcription follows verbatim scholarly rules defined in Intent.md (spot-checked by the user on real family documents).
+4. ✅ The transcription follows verbatim scholarly rules defined in intent.md (spot-checked by the user on real family documents).
 5. ✅ The transcription prompt is stored as a standalone Markdown file and can be edited without code changes.
 6. ✅ Job status transitions are visible: queued → processing → transcribed/failed.
 
@@ -175,7 +175,7 @@ These are the real unknowns this MVP exists to resolve:
 | #	| Question | How We Learn |
 | --- | --- | --- |
 | 1	| Is AI transcription quality good enough for this document corpus?	| User reviews 20–50 real transcriptions against originals. |
-| 2	| Does the verbatim prompt produce scholarly-quality output, or does it need major rework?	| Compare output to the Document Issues table rules in Intent.md. |
+| 2	| Does the verbatim prompt produce scholarly-quality output, or does it need major rework?	| Compare output to the Document Issues table rules in intent.md. |
 | 3	| What document types are hardest (old cursive, faded ink, pencil, postcards)?	| Track which uploads produce failed or low-quality results. |
 | 4	| Is single-image upload sufficient, or is batch upload needed early?	| User friction during real scanning sessions. |
 | 5	| What metadata is missing that the user wishes they could capture at upload time?	| User feedback after processing real batches. |
@@ -200,7 +200,7 @@ Recommended build order for the MVP (each step produces a testable increment):
 | Step | Deliverable | Validates |
 | --- | --- | --- |
 | 1 | config.py + models.py + db.py — data layer with SQLite | Schema and config foundation |
-| 2 | prompts/transcribe_document.md — curated prompt from Intent.md | Prompt asset pattern |
+| 2 | prompts/transcribe_document.md — curated prompt from intent.md | Prompt asset pattern |
 | 3 | services/transcription.py + providers/ — call AI vision provider with prompt + image | Core AI integration |
 | 4 | services/upload.py + worker.py — upload handling + background job loop | End-to-end pipeline (CLI-testable) |
 | 5 | ui/upload_page.py + ui/jobs_page.py — NiceGUI pages | User-facing interface |