Editorial, sourcing and verification policy

Help readers complete a real task

Guides should explain version scope, prerequisites, observable results, and recovery. The AMZDIR byline does not claim invented qualifications, experience, expert reviewers, or test results.

Source hierarchy and versions

• Prefer official tagged releases and matching documentation or code for release facts.
• Use upstream component documentation for component behavior, without assuming it proves Omarchy integration.
• Trace community tools to authors' repositories and inspect purpose, licensing, installation effects, and removal.
• Treat forums, videos, and social posts as dated leads rather than general compatibility evidence.

Rolling manuals, stable releases, and RCs can differ. Identify conflicts and check local help; a merged PR does not prove a fix is installed. Source lists collect the article's citations, not security endorsements.

Three evidence labels

• Reference-based guidance: cited explanations without an attached first-hand execution record.
• Tagged-source check: comparison with the named version; a source-check date is added only for work actually performed.
• Community-source directory: traceable author information, without independent testing or security-audit claims.

No article earns a hardware-test label from a successful website build. A future hands-on report must identify devices, Omarchy/kernel versions, channel, steps, output, failures, date, and shareable redacted evidence.

AI, translation and examples

AI may assist research, writing, translation, and site checks, but is not an independent reviewer or a firsthand user. Examples distinguish reading, changing, and deleting, and explain placeholders. Historical installers without current support evidence are not offered as one-step installation recommendations.

What dates mean

Published records first publication. Content updated records substantive body or source changes. Sources checked records the stated source work on that date. Shared footer edits, styling, or rebuilding do not refresh every article's content date. Sources can change afterward.

Corrections

Use an article's “Report an error” link or the contact page. Include its URL, version/channel, issue, and supporting evidence, without credentials.

Confirmed changes should reach both languages, metadata, and related entry points. Material corrections affecting installation, authentication, recovery, or version support are recorded in the public changelog. Typographical edits are not new technical verification. No fixed response or resolution time is promised.

Advertising and interests

Google AdSense supports maintenance, with labeled ad placements. Platform-selected advertising is not editorial advice or endorsement. Listing a tool is not compatibility certification; sponsored or commission-bearing recommendations should carry a nearby disclosure.

See the privacy policy for data handling. This site does not display an E-E-A-T certificate or score: E-E-A-T describes quality considerations, not a Google certification.