Editorial Policy

Feature claims follow the live interaction

A CountNook feature is described as available only when the corresponding page, control and result work together. Copy must distinguish browser-local saving from cloud sync, a CSV snapshot from a restorable JSON backup, a draft score from a completed round, and a user’s Clean judgment from automated assessment. Planned work and unfinished service setup are not converted into present-tense claims.

Examples explain a workflow; they do not certify an outcome. A craft example does not validate a pattern. A game example does not supply rules or settle disputes. A music example does not judge pitch, rhythm or proficiency. The product copy stays within the behavior the browser can actually perform.

Evidence has a named boundary

CountNook checks a public claim against the working tool, saved data, download or page a visitor can use. Google Analytics, Brevo, Turnstile and hosting protections are described as active only after they are configured and checked. The Methodology explains how those checks fit together without treating them as an endorsement.

Volatile external facts are either rechecked, qualified or omitted. CountNook does not fill an evidence gap with a likely answer. When the available source supports only a narrower statement, the narrower statement is used.

Page titles, summaries and links use the same rule. They may describe an available page, but they may not add a capability merely to attract visitors. A page being available does not prove that search engines list it or that an external organization approves it.

Dates describe meaningful public change

“Last updated” changes when a page’s public content or behavior changes meaningfully. Small formatting and maintenance changes do not automatically make a page look newly reviewed. Dated changes that matter to a visitor are summarized in the Changelog.

When a factual or behavioral error is confirmed, the smallest correction is made and tested. A closed historical finding is not presented as current unless it can be reproduced. A possible refinement, style preference or unverified report is not promoted to a release defect simply because more polish could be added.

Identity and product claims have different sources

About CountNook identifies the owner and developer. Public identity and experience claims are limited to information the owner has approved. Product and technical claims are checked against CountNook’s actual implementation and evidence. Building a counter does not establish specialist expertise in the activity it records. Automated checks do not imply professional review, credentials or a human fact-checking sign-off.

Specific reports are more useful than general ratings

Send a reproducible content, accessibility or behavior issue through Feedback. Include the page, what you expected and what happened, but do not include private counter values or an exported workspace. Use Contact for a question about this policy, and read About CountNook for the project boundary behind it.