How chiragmalhotra070-arch/listing-readiness-engine works
Listing Readiness Engine is a FastAPI-backed workflow for turning listing documents into an auditable readiness decision. The documented target flow is upload, parse, classify, extract, normalize, resolve, reconcile, generate requirements and apply California rules, then handle exceptions and human review before a readiness verdict. Intake can be processed synchronously or queued for a worker; runs, attempts, and audit events provide execution accounting. The README describes important listing-specific stages whose implementation was not sampled, so those are represented at the supported services-directory level. Edges rely on shown calls, indexed references, or README statements.
Main entry points: pipeline.py Processing pipeline · routes.py Intake API · classification.py Classification · services Listing intelligence
Components 24
Intake and execution
- Intake API
app/api/routes.py - Queue worker
app/worker.py - Work queue
app/services/work_queue.py
Document processing
- Processing pipeline
app/services/pipeline.py - Document storage
app/services/storage.py - Document parser
app/adapters/document_parser.py - Classification
app/services/classification.py - Semantic fields
app/services/semantic_fields.py - Duplicate detection
app/services/duplicate_detection.py
Listing readiness
- Listing intelligence
app/services - Business identity
app/services/business_identity.py - Decision engine
app/services/decision_engine.py
Persistence and audit
- Domain records
app/db/models.py - Database session
app/db/session.py - Audit events
app/services/audit.py - Persistence safeguards
app/services/text_sanitization.py
External integrations
- OCR providers
app/adapters/ocr.py - LLM adapter
app/adapters/llm.py - CRM adapter
app/adapters/crm.py - Customer lookup
app/adapters/customer.py
Other components
- Intake client
- Local file system
- Readiness verdict
- Human reviewer
Connections 24
- Intake client → Intake API: submits intake
app/api/routes.py - Intake API → Processing pipeline: starts processing
app/api/routes.py - Intake API → Document storage: stores files
app/api/routes.py - Intake API → Database session: uses session
app/api/routes.py - Queue worker → Work queue: claims work
app/worker.py - Queue worker → Processing pipeline: executes runs
app/worker.py - Processing pipeline → Document parser: parses documents
app/services/pipeline.py - Processing pipeline → OCR providers: requests OCR
app/services/pipeline.py - Processing pipeline → Classification: classifies
app/services/pipeline.py - Processing pipeline → Business identity: resolves identity
app/services/pipeline.py - Processing pipeline → Duplicate detection: checks duplicates
app/services/pipeline.py - Processing pipeline → Decision engine: evaluates outcome
app/services/pipeline.py - Processing pipeline → Audit events: records events
app/services/pipeline.py - Processing pipeline → CRM adapter: invokes actions
app/services/pipeline.py - Processing pipeline → Customer lookup: looks up customers
app/services/pipeline.py - Classification → LLM adapter: analyzes content
app/services/classification.py - Classification → Semantic fields: uses field mapping
app/services/classification.py - Semantic fields → LLM adapter: maps fields
app/services/semantic_fields.py - Document storage → Local file system: writes files
app/services/storage.py - Database session → Persistence safeguards: registers flush hook
app/db/session.py - Database session → Domain records: persists records
app/db/models.py - Processing pipeline → Listing intelligence: runs listing stages
README.md - Listing intelligence → Readiness verdict: produces verdict
README.md - Listing intelligence → Human reviewer: routes exceptions
README.md