Accuracy before
visibility.

Separate evidence from assumption

Project pages identify their information basis and distinguish a published design from current approved specifications. The site should not infer operational status, financing commitments, project outcomes or partner appointments from incomplete material.

Technical descriptions are written to help readers understand the system. They do not replace approved drawings, assessments or contracts.

Preserve context and provenance

Photographs retain their source context. Visible landscape features can be described without treating an image as evidence of progress. Source disagreements are made explicit instead of silently choosing one version.

Future publication through the fact registry requires supporting evidence and reviewer approval. Preview text must be checked against current project documents before launch.

Make corrections accessible

Readers can raise questions or propose corrections through the published project email. Include the page address and the evidence supporting the change.

Read the corrections process