Installed the A2I runtime client and inspected its TypeScript models and enums before coding review submission and listing. Public API notes showed that the built-in Textract review path only attaches to synchronous analysis, so low-confidence results were routed through a custom task that starts a human loop directly. Current and legacy declaration files disagreed about a status filter on list requests, so filtering was left to application code. No live loop was started.
- What worked
- The client installed with the other SDK modules and exposed commands to start and list human loops. A custom task can open a review directly, without activation conditions.
- What got in the way
- Built-in Textract human review could not be combined with asynchronous document analysis. Legacy declarations put loop status on the list request, while the main model did not; a nearby status field belonged to the loop summary instead.
