Architecture

The widgets run inside your application. Its browser and server initiate requests to Sea. Sea calls your application when a pipeline has an integration step configured to do so.

Responsibilities

Component	Responsibility
Your application	Case identity, sign-in, pipeline creation and screen layout
Sea context	Required API connection, credentials, shared metadata, citation handling and interaction tracking
Process	Load one existing run, its steps, definition, progress and output submissions
Form	Display a bound output's existing form UI and save corrections
Upload and manual input	Satisfy existing run dependencies through the API
Source and document list	Show and select the sources supplied by shared context
Sea API and workers	Persist submissions and execute the configured pipeline
Document storage	Supply original files through signed URLs

Document intake is an example composition of these components. The host owns its arrangement and panel choices.

A deal groups submissions. A form defines typed fields. Each submission holds the form's current values. A pipeline run executes configured steps and links its output submissions. A step's role denotes its execution kind; its unique label identifies it for widget binding.

Document processing

1. Your application creates a deal and starts its configured pipeline.
2. The host mounts Sea context and a process with the returned run ID.
3. Uploads and completed manual inputs satisfy the run's existing dependencies.
4. The process reads progress and output submissions.
5. Child forms and source viewers receive the selected output through the shared context.
6. A reviewer saves a correction. The form uses the context's client and emits an event.
7. Your application reads the run's structured outputs for its own application data.

Run a pipeline gives the API sequence. Application integration shows the widget mounts.

State ownership

State	Location
Documents, values, correction history and run progress	Sea services
Case-to-run mapping, authentication and screen layout	Your application
Run identity, steps and loaded outputs	Process
Selected output, document, citation and shared widget metadata	Sea context
Unsaved field edits	Form instance in browser memory
Language, zoom and group preferences	Browser local storage

Each process scopes its run so sibling compositions retain independent selections through their context. Changing its run or connection retires old facts and late responses. Labelled check forms are ordinary output submissions.