Border Customs & Migration

Findings

Catalogue-native findings must describe the information grouped by each layer. This legacy version does not declare them separately.

Questions & artifacts

Questions, artifact requirements and serial naming rules are required by Vercy vNext; they remain unassigned in this reference version.

Dimension & namespace

• REFERENCE `world.person` (P1): travelers, holders and applicants resolve to persons
• EXTEND `world.authorization` (A14): statusApplication and visa issuance specialize the generic application-to-grant process
• REFERENCE `world.grantedRight` (R5): issued visas and residency statuses are recorded as granted rights
• REFERENCE `world.interstateRelations` (A15): visa-waiver and customs regimes derive from treaties in force
• REFERENCE `world.offenseEnforcement` (A18): refusals, seizures and violations hand over to enforcement
• MIX-IN `world.auditTrail` (S4): crossings, checks and assessments are append-only
• imports: wco-data-model (ALIGN): customs declaration and goods-item semantics
• imports: icao-doc-9303 (REFERENCE): machine-readable travel document structure
• imports: iso-3166 (REFERENCE): country and territory code scheme

Canon, patches & standards

• REFERENCE `world.person` (P1): travelers, holders and applicants resolve to persons
• EXTEND `world.authorization` (A14): statusApplication and visa issuance specialize the generic application-to-grant process
• REFERENCE `world.grantedRight` (R5): issued visas and residency statuses are recorded as granted rights
• REFERENCE `world.interstateRelations` (A15): visa-waiver and customs regimes derive from treaties in force
• REFERENCE `world.offenseEnforcement` (A18): refusals, seizures and violations hand over to enforcement
• MIX-IN `world.auditTrail` (S4): crossings, checks and assessments are append-only
• imports: wco-data-model (ALIGN): customs declaration and goods-item semantics
• imports: icao-doc-9303 (REFERENCE): machine-readable travel document structure
• imports: iso-3166 (REFERENCE): country and territory code scheme

Artifact formats & serial data

Format-independent core. Concrete artifact formats and naming prefixes are not declared in this legacy version.

Policies & accepted processes

• `selfStatusAccess`: each person's guaranteed view of their own crossings, visas and residency records
• `carrierVerification`: yes-or-no validity checks on documents and visas for transport operators, without record disclosure
• `traderDeclarationAccount`: a declarant's standing access to its own declarations and assessments
• `interAuthorityExchange`: scoped exchange with other authorities of this catalogue under explicit grant

Read / add / edit / delete

CRUD procedures and interface bindings are not declared in this legacy version.

Ownership, roles & access

The border authority (a mandated operator under A12) stewards crossings, customs and status records. Every person is guaranteed sight of their own status; all other access, including carrier and inter-authority flows, is granted by the owner via S1 and S2.

Objects

• `borderCrossing`: one recorded entry or exit of a person; key attributes: personRef, borderPoint, direction, timestamp, outcome
• `travelDocumentCheck`: the verification of a presented document; key attributes: documentIdentifier, issuingCountryCode, validityResult, checkedOn
• `customsDeclaration`: declared goods for import, export or transit; key attributes: declarantRef, goodsItems, declaredValue, procedureCode
• `dutyAssessment`: the duties and taxes computed on a declaration; key attributes: declarationRef, amounts, reliefsApplied, dueOn
• `inspection`: a control act on goods or documents; key attributes: targetRef, inspectionType, finding, completedOn
• `visa`: a permission to enter for a purpose and period; key attributes: holderRef, category, validity, entriesAllowed, conditions
• `residencyStatus`: a status permitting residence; key attributes: holderRef, statusClass, validity, renewalRule
• `statusApplication`: a pending request for a visa or residency status; key attributes: applicantRef, requestedStatus, filedOn, state

Relationships

• `borderCrossing` -> crossedBy -> `personRef` (N:1): the traveler resolves to a person in P1
• `travelDocumentCheck` -> verifies -> `borderCrossing` (N:1): document checks attach to a crossing record
• `customsDeclaration` -> lodgedFor -> `borderCrossing` (N:0..1): a declaration may accompany a crossing or stand alone for a consignment
• `dutyAssessment` -> assesses -> `customsDeclaration` (1:1): each declaration receives one current assessment
• `inspection` -> examines -> `customsDeclaration` (N:1): controls accumulate on a declaration
• `visa` -> issuedTo -> `personRef` (N:1): the holder resolves to a person
• `residencyStatus` -> heldBy -> `personRef` (N:1): the resident resolves to a person
• `statusApplication` -> requests -> `residencyStatus` (N:1): an application targets one status class, visa applications analogously

Events

• `crossingRecorded`: a person's entry or exit was recorded at a border point
• `entryRefused`: a crossing was denied and the ground recorded
• `declarationLodged`: a customs declaration was filed
• `dutyAssessed`: duties and taxes on a declaration were computed and became payable
• `inspectionCompleted`: a control act on goods or documents concluded with a finding
• `visaIssued`: an entry permission was granted with its conditions
• `visaRevoked`: an entry permission was withdrawn before expiry
• `residencyGranted`: a residence status became effective for a person

Projections

• `myStatus`: a person's own statuses, applications and crossings; omits enforcement annotations
• `borderFlowStatistics`: aggregate flows of persons and goods by point and period; omits all identities
• `traderLedger`: declarations, assessments and inspection outcomes for one declarant; omits other parties