This view contains identified evidence gaps.

Capability hierarchy

Which business abilities exist, and which are parts of others?

This view identifies business abilities for administering waste-shipment notifications, processing movements, and finding or reporting information. The capability chapter describes both import and export notifications, while noting that the complete deployed business scope is not established. C02

Read contains as “this business ability includes the narrower ability,” not as workflow order, software ownership, or a runtime dependency. The decomposition below is inferred from the documented functional groupings; it is not a published organisational capability taxonomy. Notification management and movement management remain separate branches, with search and reporting left standalone rather than assigned an unsupported parent. C02

The evidence has different strengths: controller analyses describe selected orchestration, tests describe expected outcomes under mocks, and request contracts describe intended operations. None establishes successful end-to-end production execution. Technical frameworks, repositories, scanning services, and deployment tooling are therefore not capability labels here. E0017 E0494 E0054 C02

Diagram

flowchart TD
  n68a0a17b718b64ee403f["Notification management"]
  n566bd406f6d9d68bb274["Notification preparation and submission"]
  n94a20aacb5acfb017d00["Notification assessment and decisions"]
  nd70b1fce5b4554c28258["Financial guarantee management"]
  nf66a76cf5048b7031cc8["Notification access sharing"]
  n6a891632dd7cd7adf54b["Movement management"]
  n138930fe1bf325b64904["Movement outcome recording"]
  n5a2498ba6736c6658eae["Movement document production"]
  n12f4c907552b8710063e["Notification search and reporting"]
  n68a0a17b718b64ee403f -.->|"Preparation within notification management #40;inferred#41;"| n566bd406f6d9d68bb274
  n68a0a17b718b64ee403f -.->|"Assessment within notification management #40;inferred#41;"| n94a20aacb5acfb017d00
  n94a20aacb5acfb017d00 -.->|"Guarantees within assessment #40;inferred#41;"| nd70b1fce5b4554c28258
  n68a0a17b718b64ee403f -.->|"Sharing within notification management #40;inferred#41;"| nf66a76cf5048b7031cc8
  n6a891632dd7cd7adf54b -.->|"Outcomes within movement management #40;inferred#41;"| n138930fe1bf325b64904
  n6a891632dd7cd7adf54b -.->|"Documents within movement management #40;inferred#41;"| n5a2498ba6736c6658eae

Elements

Notification management

Kind: capability Basis: reported Description: Manage import or export notifications across preparation, submission, assessment, decision, and closure-related work, as described by the capability chapter. This is a broad business grouping, not proof of one uniform lifecycle. C02 Evidence: C02

Notification preparation and submission

Kind: capability Basis: reported Description: Assemble notification information about parties, facilities, waste, routes, and intended shipments, then submit it. Controller evidence describes preparation and submission orchestration; domain tests assert completeness checks and duplicate-submission rejection. E0017 E0494 E0279 Evidence: E0017 E0494 E0279

Notification assessment and decisions

Kind: capability Basis: reported Description: Process assessment milestones and decision-related changes, including consent withdrawal, reassessment, prohibition, and closure in the tested notification-assessment contract. These tests do not establish the complete production decision policy. E0279 Evidence: E0279

Financial guarantee management

Kind: capability Basis: reported Description: The capability chapter reports creation, approval, refusal, and release of financial guarantees as part of assessment processing. The supplied guarantee reporting model also represents cover amounts, permitted loads, active loads, and blanket-bond information, but does not establish their calculation or decision sequencing. C02 E0459 Evidence: C02 E0459

Notification access sharing

Kind: capability Basis: reported Description: Add and remove shared users for notifications. Controller analysis describes external-user eligibility and duplicate checks, while leaving final persistence, authorization, and duplicate handling dependent on unseen processing. E0017 E0494 Evidence: E0017 E0494

Movement management

Kind: capability Basis: reported Description: The capability chapter describes processing shipment movements, including receipt, completion, rejection, cancellation, and partial rejection. Supplied repository evidence confirms selected retrieval, update, and deletion operations, but not the full movement lifecycle. C02 E0414 Evidence: C02 E0414

Movement outcome recording

Kind: capability Basis: reported Description: Record receipt, recovery or disposal completion, and exceptional shipment outcomes. The chapters report these operations; supplied controller tests cover cancellation selection and receipt-recovery bulk-upload flows, without proving their production persistence outcomes. C02 C04 E0401 Evidence: C02 C04 E0401

Movement document production

Kind: capability Basis: reported Description: Produce movement documents with conditional annexes containing carrier, facility, and customs-office information. Retained analysis describes ordered merging and annex generation, but does not establish final storage, transmission, or successful production rendering. E0457 Evidence: E0457

Notification search and reporting

Kind: capability Basis: reported Description: Find notifications and obtain reporting information about finance, freedom of information, producers, shipments, and import/export statistics. Criteria and result models define the information surface, while repository analyses describe selected reporting and search queries. E0459 E0182 E0414 Evidence: E0459 E0182 E0414

Relationships

Preparation within notification management

From: Notification management To: Notification preparation and submission Relation: contains Basis: inferred Description: Preparation and submission are narrower abilities within the chapter’s notification-management scope. This decomposition does not imply that import and export submission follow identical steps. C02 Evidence: C02

Assessment within notification management

From: Notification management To: Notification assessment and decisions Relation: contains Basis: inferred Description: Assessment and decision processing form a narrower part of the documented notification-management ability, including correction and closure-related paths rather than only a linear approval sequence. C02 E0279 Evidence: C02 E0279

Guarantees within assessment

From: Notification assessment and decisions To: Financial guarantee management Relation: contains Basis: inferred Description: Financial-guarantee management is placed beneath assessment because the capability chapter explicitly groups guarantee operations with assessment processing. This is functional containment, not a claim that guarantee approval must follow consent. C02 Evidence: C02

Sharing within notification management

From: Notification management To: Notification access sharing Relation: contains Basis: inferred Description: Sharing is notification-specific management of access to the business record, supporting its placement beneath notification management rather than beneath a general technical security capability. E0017 E0494 Evidence: E0017 E0494

Outcomes within movement management

From: Movement management To: Movement outcome recording Relation: contains Basis: inferred Description: Receipt, completion, rejection, partial rejection, and cancellation are documented parts of movement processing, supporting their grouping as movement outcome recording. Their legal ordering is not encoded by this relationship. C02 C04 Evidence: C02 C04

Documents within movement management

From: Movement management To: Movement document production Relation: contains Basis: inferred Description: Movement-document production is a narrower ability within the movement and shipment capability described by the chapter. The retained document analysis supports the particular document and annex production behavior. C02 E0457 Evidence: C02 E0457

Gaps

• Hierarchy authority: The chapters provide functional groupings, not an approved parent/child capability taxonomy. Business review is needed to confirm these inferred decompositions and whether search and reporting has a broader business parent. C02
• Import/export scope differences: The notification chapter describes tested submission to Submitted, whereas the conceptual and component chapters report an import-assessment transition to AwaitingPayment beneath Submitted. These accounts must remain scope-qualified rather than merged into one workflow. C02 C06 C07 E0279
• Movement and guarantee evidence: Detailed movement-domain and financial-guarantee implementation artifacts cited by the chapters are not included in this evidence packet. Their operational scope and rules are consequently retained as chapter reports, not independently recovered implementation findings. C02 C04
• Outcome terminology: Recovery/disposal completion and partial rejection are documented, but the supplied evidence does not establish every valid combination or consistent enforcement across application and persistence paths. Complete domain methods, callers, and integration tests would resolve this. C04 E0414
• Supporting abilities: Address-book and account administration are described elsewhere in the chapters, but their authoritative placement relative to this hierarchy is unresolved. They have not been attached merely to make the hierarchy connected. C07
• Operational reliability: Reporting completeness and refresh behavior, document rendering and transmission, and sharing authorization remain unestablished. Database definitions, deployed templates, relevant handlers, and representative integration results are required follow-up evidence. E0182 E0457 E0017

Recovery limitations

• Some identified concepts have no supported connection.
• The view includes explicitly marked inference.

Sources

• C02 — SHA256 5f0242dead31d39b1254a75032bb6e91eb76df06330b351c7542819e8ed170b4
• C04 — SHA256 25efa24f3fbed7405ef5cbf62f9e0943ba662714ffbcdfd852f04e54bdfe909b
• C06 — SHA256 8bceb3aecb3cf6c886c0465d9182417aaff5f99715f640e319cf4d0126f75a10
• C07 — SHA256 bdf9a0f39146dc7515eabe57974e583bf80f25a32ee16fc7327d96597b6a08ee
• E0017 — SHA256 d085853b1955cb12eb4ab9e6d7193b1ecca10fb74c074a1b98277f70d3bc8e36
• E0054 — SHA256 cf3ccd21dd34a999412e6942b02fe8627a71799c492186cbd7aea21eb1473159
• E0182 — SHA256 5d746af7496c1107dec94eb72c47a233f1d333b22050afdaad2914ec6212d427
• E0279 — SHA256 50c25a25ef0bf7c0c7cb77e8f6667f868754ece4a34ac1f6e7083a220f3e7f5a
• E0401 — SHA256 b29d8804f8fe1ee8cbda0b45c953fc674f5cf43c926f0b031837f7c3fc61aca1
• E0414 — SHA256 00927b3bbafc68cc55e037523314623851b0cc0f73e622cc0842f0adff390ab0
• E0457 — SHA256 98f2f7867c866205f57b8712e268ff3ff5704e1533ff236617e4e4717c0a52aa
• E0459 — SHA256 74513b186450f1e0f23fa4f4aa555e8ca40940b76d6443502e2272f093824071
• E0494 — SHA256 5e75da157a930a3d220d22f0d49571bd5b87314257bd7e7cac060583b4a511d2