docs(parser): add rule/engine pipeline ADR and parsing reference #101
No reviewers
Labels
No labels
area:backend
area:frontend
area:infra
area:ocr
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
phase:M1
phase:M2
phase:M3
phase:M4
phase:M5
phase:M6
phase:M7
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
TJC/bill-splitter!101
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "docs/receipt-parser-pipeline"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
ReceiptParserinto a normalize/classify/rule/validate pipeline, restaurant-scoped, behaviour-preserving migration.docs/15-receipt-parsing.md: detector/regex/layout/scoring reference distilled from the design notes, each entry tagged current vs planned.docs/06parsing section.Refs #77 (does not close the epic).
Test plan