# Implementation boundaries

All output quantities describe seed-77 fictional staging data, including deliberately invalid records. The hosted operational view displays staging QA, not a production-quality inventory. Rejected records and canonical database counts are separate. No employer outcomes or authorised production metrics have been supplied.

The hosted map is static snapshot delivery. The read-only Python FastAPI service uses the same deterministic staging graph locally; it does not claim a live PostgreSQL-backed serving architecture. The PostGIS loader and analytical queries form a separate canonical validation path. Database runtime tests require a working isolated PostGIS engine; their actual status is recorded, not assumed from SQL files. Docker configuration is provided, but a Dockerfile is not evidence that containers or database queries have executed successfully.

Topology is a simplified directed hierarchy. It omits real fibre core/port allocation, splicing, optical budgets, redundancy, failure restoration and enterprise authentication. Capacity for non-terminals counts direct child devices; downstream active premises are separately reported. There are no real addresses, customer identities, commercial products or billing data.

Analytical coordinates are authored SRID-0 planar metres; geography.py independently transforms them into WGS84 for a Lagos display. This is not surveyed or street-aligned infrastructure. The 160 m radius and 2 m endpoint tolerance are demonstration rules. Distances are not geographic survey measurements. A dashed premise-to-terminal line is proximity only, not an installed cable. Invalid/ambiguous physical links prevent a valid path. Historical fault timestamps are fixed synthetic metadata, not operational event dates.

Future work: complete runtime PostGIS checks where unavailable; connect the read-only API to explicitly separated canonical and staging views; add typed entity/trace response models; implement versioned migrations and connection-occupancy concurrency guarantees; extend the current desktop/mobile browser checks with a full accessibility audit; publish source to a confirmed GitHub repository. No GitHub link or hosted backend is invented.