wtf is async-document-processing?

This is a Python backend project that provides a web API for processing documents asynchronously. It is built using FastAPI (a Python web framework) and stores data in a PostgreSQL database. The project uses async database access throughout, meaning the server can handle multiple requests at once without waiting on slow database calls. Authentication is handled via Google OAuth: users sign in with their Google account, and the server stores their session in an HTTP-only cookie secured with a JWT (a type of signed token). The README mentions rate limiting via a library called slowapi, which controls how many requests a client can send in a given time window to prevent abuse. Setting up the project requires Python 3.14 or newer, a PostgreSQL database (optionally run via Docker), and a few environment variables for database credentials, Google OAuth client details, and generated secret keys. After cloning, you install dependencies with the uv package manager, copy an example config file and fill in the secrets, start the database container, run database migrations with Alembic, and then start the API server. Interactive API documentation is automatically available at the /docs route once the server is running. The project includes a full developer toolchain: Ruff for linting and code formatting, pytest for testing with parallel test execution support, and Alembic for managing database schema changes over time. Tests run against a separate test database that is created and migrated automatically before the test suite runs. The README is minimal. It covers the tech stack, setup steps, and a table of development commands, but does not document the document processing endpoints in detail. Architecture decisions are referenced in a separate file within the repository. The project is configured for deployment on Vercel.