Booking Context and System Boundaries

Overall Boundary

The shared system separates work modules, the screen/HTTP layer, and the repository and external processing layers. What follows is the composition inside the Booking scope; it is not a diagram of every module and deployment node in the whole system.

flowchart TB
    U[Operator] --> UI[Booking screen]
    UI --> API[HTTP · session · authority]
    API --> B[Transportation / Booking contract]
    B --> DB[MySQL repository adapter]
    API --> P[Packing · document preview]
    P --> F[Fulfillment execution pricing]
    P --> DB
    F --> DB
    UI --> A[Attachments · AI analysis]
    A --> E[File store · external analysis service]

Separation Of Responsibility

Component	Responsible for	Not responsible for
Booking screen	Drafting input, screen navigation, showing save results and recovery	Direct DB writes, authority decisions
HTTP / session layer	Login, tenant and access decisions, input interpretation, error responses	Ownership of SQL and work data
Transportation	Booking input and read contracts, booking semantics	Direct ownership of another module's execution orders or financial records
MySQL adapter	Identifier conversion, SQL, transactions, version comparison and re-read	Approving new business policy
Fulfillment	Linking execution orders to Booking, execution item pricing	Hidden side effects of saving the Booking header
Documents, attachments, AI	Output preview, file relations, verified analysis proposals	Substituting for a successful booking save or for actual dispatch completion

Source Locations For Client 1 And Client 2

C1 is described on the basis of the Legacy screen → PHP API/helper → MySQL path. The C2 reference uses the kjtable screen → Ajax handler → reference DB path. New-System uses the module, HTTP and adapter path above. The three paths are subjects for comparison, not different names for the same API.

Design Decisions

A shared contract is defined once, with per-Client application and the differences marked. We do not create per-customer packages. HTML and Wiki are ways to read the technical specification; they are not a new work system and not a separate data authority.

The full SAD, including deployment nodes, operations configuration and every external system, must be completed later in the system-scope specification. The Booking composition alone does not declare the full SAD complete.

---

Source: new-system/docs/architecture/BOOKING_CONTEXT.md — ctc repository · This page is an English translation of the source document. Identifiers, file paths and code symbols are unchanged.