Scheduling is not storing dates

Scheduling API models supplier deliveries to employees. The repository separates handlers, services and data access, but the most interesting boundary sits inside appointment creation.

Querying is not reserving

Create calls HasConflict, then opens a transaction to insert. Two requests can query before either writes. Both see an available slot; the write transaction alone does not resolve this gap between checking and inserting.

A PostgreSQL exclusion constraint is an alternative to investigate. It is not implemented in this prototype. Before that, the project needs tests for overlap, boundaries and cancellation.

The code's state matters

The clone does not build: go.sum is invalid and some files are truncated. This note therefore discusses a design identifiable in the code, not an operational API. The case study records the reproduced failure and inspected files.