Case study · fixture

A traceable path from requirement to handoff.

This representative narrative demonstrates where approved evidence will sit. It does not describe a real network or claim completed engineering work.

01 · Requirements

The fictional brief asks for a small service corridor, explicit coordinate assumptions, safe identifiers, and a review package.

02 · Data provenance and CRS

Every feature is generated in-repository. The fixture declares a local training grid and avoids implying survey accuracy.

03 · Processing and model

Allowed public attributes are reduced to asset identifier, type, status, and display coordinates. Configuration rules then map types to schematic materials.

04 · Configuration and CAD

The configuration lab demonstrates a QGIS expression and XML fragment. The CAD page checks layer naming and millimetre units before exchange.

05 · QA and reflection

A fictional defect moves from open to verified. Reflection remains neutral placeholder copy until Kimberly explicitly approves words presented as hers.