Phase 1 — Never hard-reject intake (best-effort ingest for any file)#11
Closed
xt0n1-t3ch wants to merge 1 commit into
Closed
Phase 1 — Never hard-reject intake (best-effort ingest for any file)#11xt0n1-t3ch wants to merge 1 commit into
xt0n1-t3ch wants to merge 1 commit into
Conversation
Phase 1 of the Reve Intelligence overhaul (#2). - Remove the extension whitelist from intake validation; only operational limits remain (empty + oversize). Any file type is accepted. - The parser routes unknown extensions through best-effort visible-text extraction instead of throwing an unsupported-extension error. - Drop the terminal "Unsupported" path: unknown / low-confidence documents are still ingested as reviewable records that surface why they are uncertain, rather than being quarantined. Delete DocumentSupportPolicy and the NormalizeUnsupportedDocuments startup pass. - Raw export now works for any record (removed the export Conflict guard). - Update the integration test to pin the new contract. Build 0 warnings; unit 2/2 and integration 5/5 green; format clean. Refs #2
Owner
Author
|
Superseded: Phase 1 (never-reject) and Phase 2 (parser router) are coupled and ship together in the combined PR. The standalone Phase 1 commit was incomplete; folded into the clean combined branch. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Phase 1 of the Reve Intelligence overhaul. Closes #2. Stacked on #10 (base = feat/reve-overhaul).
What changed
The app no longer hard-rejects anything. Every upload becomes a reviewable record.
DocumentSupportPolicy, theMarkUnsupportedbranch, and theNormalizeUnsupportedDocumentsstartup pass. Unknown / low-confidence documents are ingested as reviewable records that surface why they're uncertain (classification + missing-field warnings).Conflictguard.Unknown) and stays exportable.Proof
dotnet build0 warnings;dotnet testunit 2/2 + integration 5/5;dotnet format --verify-no-changesclean..xyzfile becomes a reviewable record — statusExtracted, typeUnknown, confidence 26% (honest, not inflated), JSON/CSV export enabled, exceptions explain the uncertainty.Notes
Flat per-field confidence and the truthful preview/branding still land in #4 and #6. Real typed parsers (Office/Excel/email) land in #3.