Method note

Evidence Before Polish

A project becomes publicly legible through proof objects before it becomes polished. A routing diagram, latency capture, audio comparison, redacted screenshot, or maintenance photo can do more honest work than a finished-looking page with unsupported claims.

What this changes on the site

Atlas pages use controlled status language and name the next proof object when evidence is still incomplete. That is not an apology. It is part of the method.

Projects that make this visible

• MOARkNOBS-42 keeps latency, mode feedback, and mapping evidence in view before enclosure polish.
• frZone needs a short capture showing threshold state and MIDI or OSC output at the same time.
• Horizon becomes legible through a before/after audio render before broader DSP claims.
• live-rig needs a redacted routing diagram before any full-system confidence language.

Public reading rule

If the proof is partial, the page should say so directly. If the repo contains deeper implementation truth, the page should link there and narrow the public claim.