Booking Sources and Change Control¶
Where The Basis Lives¶
| Class | Basis in the repository |
|---|---|
| C1 Legacy (external coexisting checkout) | app/systems/TMS/booking/api_routes.php, post_helper.php, profile_extension.php |
| C2 reference (external comparison material) | reference/mkmetal/public/js/kjtable.js, controller/Ajax.php, DDL in mk.sql, view/packingList.php, view/bookingConfirmation.php |
| C2 migration plan (owned by Product) | buildImportPlan in packages/db-mysql/src/legacy-operational-import.mjs; owner NS3-115 |
| native input and read | packages/modules/transportation/src/booking-data.ts |
| native write and copy | packages/db-mysql/src/company-booking.ts and company-booking/ |
| Packing | packages/modules/transportation/src/packing.ts, packages/db-mysql/src/packing.ts |
| Packing historical actual basis | NS3-112 REC03C inline form / commit525d0d15c; .generated/acceptance/NS3-112/recovery-2026-09-08/packing-inline-assertions.mjs and the original JSON. Current reuse scope is distinguished in ACCEPTANCE |
| Screen and recovery | apps/web/src/composition/pages/booking/ and transport/semanticBookingRoutes.ts |
| Shared multi-edit recovery | packages/ui/src/operations/MultiEditDialog.tsx; onReload consumers in Booking/Fulfillment and apps/web/tests/multi-edit-recovery.test.ts |
| Source reconciliation and implementation notes | OCEAN_BOOKING_SOURCE_RECONCILED.md, packages/modules/transportation/README.md |
| Test and execution evidence | Booking TEST_MATRIX.md, docs/tasks/NS4-017.md |
| C2 actual manual | mk-booking / mk-booking-confirmation overrides in the local T_WIKI_PAGE; catalogue precedence in apps/web/app/api/platform/wiki/[[...path]]/route.ts. Distinguished from the generic booking source |
Update Rules¶
When a requirement, source or implementation changes, review the matching specification and test traceability items together. A code change does not automatically approve a requirement. HTML is regenerated from the source and carries a source fingerprint when generated. That fingerprint exists to check whether the HTML is current; it does not mean automated impact analysis across all work sources is complete.
After reviewing a specification, derive the development guide, the operations runbook and the C2 user manual. Do not overwrite the date and result of historical evidence with a new execution.
Additional basis added 2026-09-12: running the synthetic import plan proves only status and company mapping, and running the isolated Legacy source callback proves only that refreshing the list is refused for an empty copy result. Both are reflected in the data specification, the interfaces and ACCEPTANCE respectively, and neither is promoted to DB or browser acceptance. External Legacy/reference paths are not folders inside the future Product repository.
On the same day, in a separate local C2 UI/DB test, a vessel-name length defect was reproduced and
fixed, and creation, single edit, copy, Confirmation lookup and test-data cleanup were confirmed.
The current seven input widths and the actually accepted range are reflected in the data
specification and ACCEPTANCE, and only the basic usage that was verified is derived as the
pre-publication draft of the same ACCEPTANCE. The real errors, header backup, copy response and
cleanup basis are in .generated/acceptance/NS4-017/booking-*.json; they are not evidence for other
roles, for Packing editing, for printing, or for Wiki publication.
Source:
new-system/docs/knowledge/BOOKING_SPECIFICATION_SOURCES.md— ctc repository · This page is an English translation of the source document. Identifiers, file paths and code symbols are unchanged.