Port & Terminal 01 — Port Infrastructure & Engineering Restrictions (prt_01_infra)

Know what the fixed infrastructure is, how it is inspected, and which engineering restrictions apply — port, terminal, area, fixed assets (berths, wharf structures, fenders, conveyor supports, pavements), inspection plans and inspections, defects, engineering assessments, restrictions, remedial work and independent verification.

Its central question:

Is this piece of fixed infrastructure fit for the operation that depends on it, and if a restriction applies, who assessed it, who approved it and who verified its release?

prt_01_infra is application PRT-01 of the Port & Terminal Operations series (prt_NN_<name>, numbered by the Stage 1 pack catalogue; each able to run stand-alone or as a member of the port_terminal_operations network). It shares no tables and no foreign keys with its five siblings (prt_02_maint, prt_03_ops, prt_04_berth, prt_05_safety, prt_06_assurance) — they link by canonical (cid) strings and by events only. This is a demonstration prototype; all data is fictional (the terminal, the assets, the people and every number — no engineering standard or statutory time is claimed).

The spine

InfraPort → InfraTerminal → InfraArea → InfraAsset → (InfraInspectionPlan → InfraInspection) / InfraDefect → InfraAssessment → InfraRestriction ← InfraVerification ← InfraRemedialWork, with InfraDependency recording which other applications' records depend on an asset.

The documents

Page What's in it
00 — Overview What the app is, the rules it is built around, the 15 models by area, the demo story
01 — Quick Reference Menu map, every model, status vocabularies, workflow actions, how to run, seed and regenerate
02 — System Diagram The data model as diagrams (+ interactive viewer) and how the app links to its siblings

Status

Built: the data model (12 pack models plus 3 overlay models, 15 in all), the generated list / detail / edit screens, the menu and dashboard, and the demo data for Example Bulk Terminal (T01).

Phase 2 (not built yet): the workflow guards of the pack's workflows.yaml (approve assessment, activate restriction, complete remedial work, release restriction with an independent verification) and the business rules are not enforced — a status can be edited directly in this prototype. The integration handlers are scaffolds: the published event infrastructure.restriction_changed and the three consumed events are declared and wired, but the handlers do not yet change state. The overlay models (InfraObligationTask, InfraCaseLink, InfraSafetyHold) are additions to the pack's models, put in so the event handlers have somewhere typed to keep what they receive.

Prototype system; draft. All names and figures in the demo data are fictional; no engineering or statutory claim is made.