This view contains identified evidence gaps.

Integration data flow

Who sends which information to whom, in which direction, and through what mechanism?

This bounded view recovers three internal exchanges: notification-progress retrieval, authority-specific notification-number allocation, and import-movement updates. The supplied analyses report concrete database calls for these exchanges; they do not establish a complete deployed integration topology. E0008 E0262

Read each relationship as information travelling from the named From participant to the named To participant. Requests and returned information are separate directional flows. The model distinguishes the progress service’s expected result sets from the database procedure’s published definition, rather than treating either as live verification. E0008 E0081

SQL Server is the shared database participant in this model, not a claim that every application component uses one physical database instance. SQL Server-oriented scripts and queries are supplied, but deployed connectivity and topology remain unresolved. E0156 C10

Diagram

flowchart LR
  n6001f2645fbaf4c2dd5d["Notification progress service"]
  nc6cafd930e4948f80dfd["Notification number generator"]
  n1df1b49c4825fd9f086f["Import movement repository"]
  nfa3b88fadcf90d78db13["SQL Server"]
  n6001f2645fbaf4c2dd5d -->|"Notification identifier selecting the notification whose progress is requested. #91;E0008#93;"| nfa3b88fadcf90d78db13
  nfa3b88fadcf90d78db13 -->|"Notification and related progress fields#59; producer identifiers and site-of-export flags#59; facility identifiers and actual-treatment-site flags#59; waste-code categories#59; and route EU-membership flags, customs-office identifiers, and selection flags. #91;E0081#93;"| n6001f2645fbaf4c2dd5d
  nc6cafd930e4948f80dfd -->|"A sequence-selection query identifying the authority-specific number sequence. #91;E0008#93;"| nfa3b88fadcf90d78db13
  nfa3b88fadcf90d78db13 -.->|"Next value allocated from the selected notification-number sequence. #91;E0008#93; #40;inferred#41;"| nc6cafd930e4948f80dfd
  n1df1b49c4825fd9f086f -->|"Movement and notification identifiers, with movement-update information covering shipment and prenotification dates, comments, statistics marking, outcome flags, receipt quantities and units, rejection details, and recovery or disposal date. #91;E0262#93; #91;E0218#93;"| nfa3b88fadcf90d78db13

Elements

Notification progress service

Kind: component Basis: reported Description: Retrieves progress information through a database procedure and translates five result sets covering notification data, producers, facilities, waste codes, and customs offices. It also applies completion logic to the returned information. E0008 Evidence: E0008

Notification number generator

Kind: component Basis: reported Description: Requests the next sequence value using a sequence name derived from the competent authority. The supplied database analysis separately reports authority-specific notification-number sequence definitions. E0008 E0156 Evidence: E0008 E0156

Import movement repository

Kind: component Basis: reported Description: Provides import-movement data access using Entity Framework and raw SQL, including a receipt-and-recovery update operation. Supplied identifiers are passed through SQL parameters in the reported update paths. E0262 Evidence: E0262

SQL Server

Kind: store Basis: reported Description: Holds notification-related data and SQL objects supporting progress retrieval, number allocation, and movement updates. The supplied scripts define notification-number sequences, a progress procedure, and an import-movement update procedure; they do not demonstrate the deployed database state. E0156 E0081 E0218 Evidence: E0156 E0081 E0218

Relationships

Request notification progress

From: Notification progress service To: SQL Server Relation: sends Basis: reported Description: The service executes the notification-progress procedure with a notification identifier to obtain the information used in progress calculation. E0008 Information: Notification identifier selecting the notification whose progress is requested. E0008 Mechanism: Raw SQL procedure execution through the Entity Framework database connection. The service opens the connection and closes it in a finally block. E0008 Evidence: E0008

Return progress data

From: SQL Server To: Notification progress service Relation: sends Basis: reported Description: The service expects five result sets, and the supplied procedure analysis reports five corresponding outputs filtered by the supplied notification identifier. This supports the documented exchange shape, not deployed schema compatibility. E0008 E0081 Information: Notification and related progress fields; producer identifiers and site-of-export flags; facility identifiers and actual-treatment-site flags; waste-code categories; and route EU-membership flags, customs-office identifiers, and selection flags. E0081 Mechanism: SQL result sets read and translated through Entity Framework ObjectContext translation APIs. E0008 Evidence: E0008 E0081

Request next notification number

From: Notification number generator To: SQL Server Relation: sends Basis: reported Description: The generator executes a next-sequence-value query whose sequence name is derived from the competent authority. The database scripts report separate sequences for the four UK competent authorities. E0008 E0156 Information: A sequence-selection query identifying the authority-specific number sequence. E0008 Mechanism: SQL Server sequence allocation through a NEXT VALUE FOR query. E0008 Evidence: E0008 E0156

Return allocated sequence value

From: SQL Server To: Notification number generator Relation: sends Basis: inferred Description: Returning the allocated sequence value to the generator is inferred from its reported execution of the next-value query. The supplied analysis does not describe the exact response mapping or subsequent formatting into a complete notification number. E0008 Information: Next value allocated from the selected notification-number sequence. E0008 Mechanism: SQL query result; exact materialization and conversion are unknown in the supplied analysis. E0008 Evidence: E0008

Send import movement update

From: Import movement repository To: SQL Server Relation: sends Basis: reported Description: The repository reports a raw-SQL receipt-and-recovery update path. The database-side import-movement procedure reports updates to movement fields and receipt, rejection, partial-rejection, and operation-receipt records. Exact correspondence between every repository argument and procedure parameter remains unestablished. E0262 E0218 Information: Movement and notification identifiers, with movement-update information covering shipment and prenotification dates, comments, statistics marking, outcome flags, receipt quantities and units, rejection details, and recovery or disposal date. E0262 E0218 Mechanism: Repository raw-SQL execution, with supplied identifiers represented by SQL parameters. The published import-update procedure uses a transaction and rolls back and re-raises caught errors. E0262 E0218 Evidence: E0262 E0218

Gaps

• Progress contract compatibility: The service analysis says the procedure definition was unavailable within its own source range, while the separately supplied database analysis reports that definition. This narrows the gap to deployed compatibility and execution behavior; it does not establish that the published consumer and procedure work together successfully. Command and reader disposal are also not established by connection closure alone. E0008 E0081
• Number allocation guarantees: Sequence definitions and a next-value query are reported, but full-number formatting, uniqueness enforcement, and end-to-end concurrency guarantees remain unresolved. Follow-up should inspect the generator implementation, database constraints, and concurrent-creation tests. E0008 E0156
• Movement update boundary: The exact repository-to-procedure parameter mapping, caller authorization, and coordination with other ORM writes require confirmation. No return flow is modelled because the repository’s update response contract is not established in the supplied analysis. E0262 E0218
• External integrations omitted: Chapters report identity, scanning, email, and Companies House-related components, but the underlying artifacts cited for those exchanges are not supplied here. Those chapter statements do not justify inventing a complete sender, receiver, payload, or transport path. Deployed routes, client implementations, and environment configuration are required to extend this view. C07 C09 C10
• Reporting refresh omitted: A cache-refresh procedure is reported, but its initiating job or application caller and schedule are unknown. It therefore cannot be attached to an operational sender in this recovered flow. E0218 C08

Recovery limitations

• Ownership, mechanism or boundary controls remain explicitly unverified.
• The view includes explicitly marked inference.

Sources

• C07 — SHA256 bdf9a0f39146dc7515eabe57974e583bf80f25a32ee16fc7327d96597b6a08ee
• C08 — SHA256 48d1a99f108e6181d2ad40d5538216b59cdb5fa3fc5131464794b98856c3b850
• C09 — SHA256 96150714a9093ad3b81682e3262b0aaf88c8f04b6664a52273b79f29d0a6acd2
• C10 — SHA256 6ca1acb64b4f356fc274bdf340f0ce48a5f37133e0b9d2da632a9ba794dc90c0
• E0008 — SHA256 090f3006325dff37b2efc4e57bd7f71899a754f0f12a367d7231326c45846ad2
• E0081 — SHA256 880c1283f6cfd7d6f8407a0f46f77c0e778837966f8bde5b3c4c23e8c6b4ff13
• E0156 — SHA256 5e890d03921ed9b2b61c72356c808100f2fd9b69d45546bb9cbda21a932fe2c5
• E0218 — SHA256 51dd7c8b8b56b62dc1b1593551915269a6e29fdf5e835ce32a37d472c324b316
• E0262 — SHA256 6284ea5fe1ee7f4bdb6d76ae0d65fe5992ee19c0f0339a1e443328986fd8a89e