Make it. Check it. Say what happened.

Start with something worth making or a question small enough to answer. Build a narrow version, inspect what it actually does, and keep the evidence close to the claim.

A plan is not a result

Separate intended capabilities from implemented ones. Roadmap features stay on the roadmap. A local prototype is not a public release; public source is not a supported service.

A repository is not a benchmark

Source can show how a tool is built. A test can establish a specific behavior. A performance claim needs the task, model, configuration, measurement method, and result. None of these automatically proves the others.

Where a project has public source, the work index links it directly. Where evidence is private or unavailable, we say so rather than inventing a public artifact. Small trials do not establish general reliability.

Failure belongs in the record

Keep constraints, manual interventions, and negative results attached to the work. If an earlier claim is unsupported, correct the original address instead of quietly leaving it in circulation. The lab corrections follow that rule.

Publication is a separate decision

A passing build is not permission to publish. Human review determines what is appropriate to share. Secrets, private endpoints, personal information, and third-party material without permission stay out.

Creative work follows the same standard: identify generated or illustrative material honestly. A graphic study is not a screenshot; a proposed production pipeline is not a finished film.