ID 147 Initial User Feedback

OQ Responses

1. See below for more information.
2. As noted in later findings, ID-147 owns the first registry install, as ID-117 eventually used a different approach.
3. Unlock Extend Bounding Box Citations - see below for more information.
4. Fold in migrating components/item-detail/content-renderer.tsx to streamdown.
5. Spike, plus ensure commonforms approach is integrated here too, assuming it should be.
6. As per item 1, see below for more information.

More information for the OQs

• PDF - Adopt for consistency across document viewers.
• Adopt DOCX, XLSX, and CSV viewers.
• Adopt Document Viewer Sidebar, File Thumbnail, and Document Splits for Multi-document item page.
• Adopt File Upload, PDF Dropzone - does Extend have an equivalent backend, given that theirs is “battle-tested”, and our platform isn’t live yet.
• Adopt File System for browse/finder, but presumably this also needs to work correctly with the multi-document item page approach.
• Spike the schema builder - we have example forms that we can use.
• Why wouldn’t we use the DOCX & Excel Editor to enable users to make changes or manually any missing answers? E-signature would be valuable to adopt here too, given some forms require this.
• Similar to the above, it would make sense to utilise layout blocks for composing state/deadline/questions/coverage/documents panels to ensure consistency of the surface, again, keeping in mind that anything we have currently, isn’t yet battle-tested, and these may also help where we need to create “custom” layouts which Extend doesn’t cover by default.
  • NB. There are components which may also be relevant for the work required for custom components. I’ve listed some of these below, in case they haven’t been identified in the RESEARCH work so far and are vaulable/relevant to what is needed here for the Procurement UI rework:
  • components/qa/.
  • components/procurement (question-* and response-* components, amongst many others).
  • components/source-document-detail - has derived-pairs-list.tsx and document-citations-panel.tsx.
  • There are template coverage components in both procurement and coverage.
  • components/admin/q-a-pairs/dedup-proposals/
  • Pre-existing editor surfaces under item-detail/
• What is the impact of adopting wholesale, versus cherry-picking + re-wire? E.g., could we not just use Hugeicons where the extend components require these?
• Regarding warm meridian token usage, we wouldn’t necessarily apply this wholesale - first step would be added the components as-is (people prefer white backgrounds for documents), and then we’ll tweak once the components are in place.
• For pixel/region bounding-box coordinates, would we be using commonforms functionality for this - form_creator.py uses this functionality, for example.
• Are we already using Anthropic’s Files API, Converse API, InvokeModel API and Prompt Caching for document/form processing, either in the app, pipeline, or MCP tooling?
• Would the following be a feasible option for the Workflow-state stepper UI requirement: https://elements.ai-sdk.dev/examples/workflow