Policy cluster

Transparent publishing surfaces need visible policy cues.

This is a restrained prototype for how Mosquito Laser exposes editorial-policy surfaces while the upstream evidence-first workflow matures. It is navigation and expectation-setting, not a backend policy engine.

Editorial policy

Judgment happens upstream. The site presents reviewed editorial outputs with visible update state, source posture, and correction intake rather than pretending the shell is the editorial brain.

Methodology

Comparisons and explainer pages should make their decision frame visible: what is being measured, what is interpreted, and what remains uncertain or out of scope.

Sourcing policy

Future public pages should separate primary materials, technical references, and interpretive notes so readers can see where direct evidence stops and analysis begins.

Corrections policy

Readers should be able to report factual errors, stale guidance, and missing context. Public updates should describe conceptual changes rather than hide behind silent edits.

Image policy

Illustrations, diagrams, and product or facility imagery should be labeled by origin and treated as explanatory aids, not as substitute evidence for technical claims.

Prototype note

Delivery layer, not editorial brain.

DanSites should show provenance, review state, and correction intake clearly, while the underlying editorial judgment remains upstream. This page exists to make that future surface visible without claiming backend logic that does not exist yet.

View article prototype Corrections contact