POSTGRESQL REFERENCE · WORKING SOURCE

docs/production-work.md

This file ships in the runnable source archive. Synthetic fixtures and demonstration policies are identified in the README.

# Work remaining before production use

The prototype proves a bounded workflow with synthetic data. Production readiness is a separate engineering and operational program. The following work is intentionally deferred, with the decision it would require made explicit.

| Area | Required work | Why it matters |
| --- | --- | --- |
| External warehouse reconciliation | Define the source of truth with each WMS; map pallet/location identifiers; import receipts, departures and moves; reconcile counts and custody intervals; own duplicate, late and missing events. | A consistent application database is not evidence that the warehouse floor matches it. |
| Operational exceptions | Define damaged goods, rejected loads, stock discrepancies, unsafe positions, overflow space, after-hours receipt, pallet identity corrections, retroactive movement corrections and escalation owners. | The demonstration preserves overstay and block conflicts, but a production operation needs an agreed human resolution process. |
| Authentication and sessions | Integrate the chosen identity provider, manage invitations and role changes, MFA, recovery, session expiry/revocation, secure cookies over TLS, CSRF/origin policies, brute-force protection and access reviews. Remove shared demo credentials and clock controls. | Seeded local users support a demonstrator; they do not establish safe public access. |
| Tenant isolation | Define operator/customer relationship lifecycle, scoped service identities and database roles; consider row-level security as defense in depth; test every export, audit and integration path. | Tenant protection must extend beyond the browser and the current API. |
| Contractual billing | Agree the legally operative tariff: reservation fees, minimums, rounding, taxes, currencies, grace periods, receipt variance, cancellation, liability, disputes, credits and payment terms. Version acceptance evidence. | The USD 61.00 fixture is a demonstration policy, not a market quote or customer contract. |
| Financial operations | Define invoice numbering/finality, accounting periods, credit notes, receivables and payment integrations; control who can issue adjustments and reconcile them. | An explainable preview is not an accounting ledger or payment collection system. |
| Physical capability and safety | Validate each rack position's limits, handling equipment, inspections, permitted commodities, segregation and local requirements with qualified operations staff. | Declared dimensions and weights are necessary application inputs, not certification of safe storage. |
| GS1/EPCIS integrations | Validate identifiers, preserve issuer information, choose standards versions and partner profiles, implement schema/vocabulary validation and interoperability tests. | A free-text external ID and EPCIS-informed event fields do not establish standards conformance. |
| Database operations | Use a supported managed or operated PostgreSQL deployment with least-privilege roles, TLS, controlled migrations, encrypted backups, restore drills, monitoring and tested recovery objectives. Replace the development provisioner as appropriate. | The local persistent database demonstrates transaction behavior; production durability and recovery need operational controls. |
| Performance and contention | Measure warehouse-lock contention at realistic request volumes; preserve correctness while considering finer allocation partitions or stronger database constraints. | Coarse per-warehouse serialization is intentionally easy to audit for this small scope. It must be measured before scaling. |
| Availability and delivery | Add deployment health, controlled rollout/rollback, request limits, metrics and tracing. Add an outbox only when background delivery is implemented; define its retry/idempotency and reconciliation rules. | More services and queues do not replace transactional evidence or operational ownership. |
| Privacy and retention | Agree retention, authorized exports, audit review, deletion/legal-hold requirements and incident response with the parties. | Custody and billing evidence can outlive an active booking and need a deliberate lifecycle. |
| Additional warehouse services | Introduce separate models/tariffs for floor or bulk storage, stacking, other units, cold chain, hazardous goods, picking and value-added operations. | These are not interchangeable with one ambient pallet per rack position. |
| Scheduling and networks | Add dock appointments, carrier interfaces, marketplace onboarding and optimization only after the core operational contracts are reliable. | Each creates new promises and exception paths beyond this release's acceptance gate. |

## Explicit prototype limits

The demonstration does not automatically resolve an overstay, relocate goods, certify storage capability, charge unused reserved space, collect payments, or reconcile an external warehouse. Movement adjustments retain the original evidence; the initial adjustment path does not rewrite historical receipt/release timestamps or quantities. Complex physical corrections require a future protected correction workflow.

The prototype's local demo clock and reset mechanism are presentation tools. Production must use an authoritative operational clock, handle clock skew and delayed evidence explicitly, and disable seed/reset access to real data. Final verification results belong in the verification report; this list does not turn a missing implemented invariant into acceptable deferred production work.