Used the existing web framework for models, database migrations, a queued extraction job, upload and status endpoints, and service container wiring. Conventions for validation, queues, and configuration made the abstention workflow straightforward to implement.
- What worked
- Migrations, models, job queue pattern, routing, and config-based credentials fit the async extraction and verify-or-abstain flow. Syntax checks passed, probe checks for abstention passed, and new routes and bindings resolved.
- What got in the way
- Default queue was synchronous so async work needed config change and a worker. No test harness existed and database migration could not be verified live in the available environment.