Editorial policy

Independence and purpose

Education must be useful without purchasing help. Recommendations start with the work and may conclude that manual work or ordinary automation is preferable. A consulting opportunity is not evidence that a workflow should be built. We do not sell placement in an editorial ranking.

Sources and evidence

Use primary documentation for product behavior, identify the configuration and date behind a test, and distinguish vendor claims from observations. Link sources near the claim they support. An original worksheet may have no external source; it still needs clear assumptions.

Editorial: an explanation or planning method, not an execution result.
Illustrative: a synthetic example or proposed configuration that has not been demonstrated.
Tested demo: a reproduced configuration with recorded inputs, outputs, failures, and a real test date.
Measured pilot: a bounded operational trial with a baseline, period, costs, and limitations.
Verified case study: a documented real deployment with permission to publish its evidence.

A more impressive label requires more evidence. Synthetic examples never become customer results through wording or presentation.

AI-assisted editorial process

AI may assist outlines, drafts, code, and sample fixtures. It is not a source of truth and is not an independent reviewer. Before publication, the accountable human checks claims, sources, examples, and disclosures. Technical steps also require actual reproduction. The foundation currently awaits that named human review.

Disclosures

Disclose relevant commercial relationships, sponsorships, referral arrangements, and consulting involvement alongside the affected content. Do not invent independence or experience. Missing founder identity and commercial facts remain visible until confirmed.

Dates

Publication means first public release. An updated date records a substantial change; a rebuild or spelling fix does not make content newly reviewed. A fact-check date and a live-tool test date describe different work. Pending dates are not replaced by today's date.

Corrections

Report a specific passage, page URL, and supporting evidence through the process on the corrections page. Review the claim, correct a material error, and record what changed and whether test outcomes changed. Minor spelling fixes do not need a public log entry. No response deadline is promised.

Update policy

Plan to review tool-specific tutorials every 90 days and evergreen explanations every 180 days, or sooner after a material change or error report. Actual retesting requires execution. Stale or broken instructions receive a needs-retest warning and leave ready-to-try recommendations until repaired. A broken prerequisite also affects dependent instructions.

Policy draft prepared October 20, 2026. Human publication review is pending.