A2I was integrated so every extraction starts a human loop for a private clinician workforce, with output kept in the document region. Service write-ups supported mandatory review rather than confidence-only review. The runtime request shape did not match the first client code and had to be corrected from the installed classes. No live loop was started.
- What worked
- The human-loop model fit a review of every document, and private workforce plus regional output could be enforced as preconditions before starting a loop.
- What got in the way
- The start-loop call expected a structured input object rather than a direct content field, so the first adapter did not compile until the installed classes were inspected.
