Skip to content

Processing Hub

Processing Hub

What this area does

Processing Hub is the operational workspace for queued or in-flight documents. It is where users inspect documents, configure prompts, verify outputs, and work through processing status.

The route is mounted from App.jsx as a protected workspace page and uses the shared workspace chrome.

Primary implementation

The main implementation lives in src/pages/processinghub/:

  • ProcessingHub.jsx
  • DocumentTable.jsx
  • MobileCard.jsx
  • PromptConfigModal.jsx
  • VerificationModal.jsx
  • verificationUtils.js

Service and context coupling

Processing Hub depends on the same shared state and service layers as the rest of the workspace:

  • processing documents are loaded and updated through the document service and shared context,
  • prompt/schema state is shared with the generator contexts,
  • verification logic is split into modal and utility layers so the page shell stays thin.

Important responsibilities

  • show processing documents in a dense table/card layout,
  • present prompt configuration before or during processing,
  • let the user verify document outputs,
  • keep document status synchronized with backend state,
  • support mobile and desktop display modes.

Invariants

  • The hub must remain consistent with the shared processing-document state; stale table state is not acceptable because it drives operational decisions.
  • Verification actions should be gated by the current document and prompt configuration.
  • Page-local UI should not duplicate the parsing/verification rules that belong in verificationUtils.js.

Validation

This area is exercised through the processing/document contract tests and the browser workflow specs that cover portal/preflight and batch-processing journeys.