Editorial standards

How chatagent.ca is written and maintained · Justin Helmer · reviewed 18 October 2026

These standards exist so visitors, and quality reviewers, know what kind of site this is. We are an independent educational publisher with free tools, not a content farm.

What we publish

What we do not publish

Scope

chatagent.ca publishes original educational material about AI-agent workflows, LYGO tools, champion personas, and the public records around them. It also hosts free browser tools, games, and a small number of policy pages. The standard below applies to every page, including the ones that are mostly a tool with an explanatory frame.

Authorship and AI assistance

Every guide carries a human byline: Justin Helmer (Excavationpro). AI may help with drafting, outlining, editing, or checking a draft against a source. It does not get a byline, and it does not get to invent a source. The human who publishes the page is responsible for the claim, the links, and the date.

When a page is substantially generated or restructured with AI assistance, the byline still means a human reviewed it. A byline is not a claim that no tool was used; it is a claim that a person is accountable for what shipped.

Sourcing and verification

Technical claims should point to a primary source: a repository, a public JSON file, a command the reader can run, or a page that itself links to the record. A citation is not decoration. If a source does not support the sentence, remove the sentence or remove the citation.

We do not invent sources, dates, hashes, or test results. When a room is unreachable, the page says it is unreachable rather than filling the gap with a story. When a claim is an opinion, the page says it is an opinion. When a claim is time-sensitive, the page carries a date and the reader is told to re-check it.

For the protocol material, the public repository and the dual ledgers are the authority. For a tool, the tool’s own screen and source are the authority. For a person, the public repository and the contact page are the authority. A guide can summarize those sources; it cannot replace them.

Originality and page purpose

Every page must have a job that is clear in the first screen: teach a task, document a tool, provide a reference, or record a public page. A page that exists only to hold an ad is not published. A page that repeats a template paragraph across a dozen URLs is not a set of articles; it is one article wearing costumes, and it is treated as a quality failure.

Champion profiles are role cards: they explain the persona, when to use it, what it is not, and how to invoke it. They are intentionally shorter than a guide, but they still need specific lore, a real use case, and a limit. Guides are task-based and should include steps, examples, failure modes, and a way to check the result. Hubs are directories with a point of view, not link dumps.

Corrections and updates

When a page is wrong, fix the page and change the visible review date. If the correction changes the argument, say what changed instead of quietly deleting the old claim. A correction note is not an admission of weakness; it is evidence that the page is maintained.

Minor copy edits do not require a new date. A changed command, a changed price, a changed license, a removed link, or a new factual claim does. The date should tell a reader when the page was last checked, not when it was last touched.

Advertising and independence

Advertising, when active, is Google AdSense and is labeled. Ads do not control the conclusions of a guide. We do not accept undisclosed paid placements, and a sponsor does not get to edit a review. If a page ever contains an affiliate link, the link is disclosed next to it.

Ads are kept off pages that do not have enough original content to support them, and off tools, games, policy pages, and error pages. The ad is not the reason the page exists. A page must still work if the ad fails, the network is slow, or JavaScript is off.

Tools and security

A tool recommendation is a claim about behavior, so we test the behavior before recommending it. For installable skills, read the instructions and the source, check what permissions it asks for, and prefer the smallest permission that does the job. Do not paste secrets into a prompt, a screenshot, or a public issue.

If a tool changes ownership, stops exporting, or starts requiring an account for the core job, the recommendation is re-checked. A “free” label is not permanent; the page should say what is free today and what may change.

Review checklist before publish

  1. Job: can a reader say what this page is for in one sentence?
  2. Source: does every checkable claim have a link, a command, or a date?
  3. Originality: is any paragraph repeated from another page without a reason?
  4. Limits: does the page say what the tool or claim does not do?
  5. Next step: does the reader know where to go after this page?
  6. Ads: is the page substantial enough for an ad, and is the ad off the reading path?
  7. Links: do the internal and external links resolve, and is the canonical URL correct?
  8. Date: is the visible review date current for the claims on the page?

How to report a problem

Use the contact page with the page URL and the sentence or step that is wrong. For a security issue, describe the class of issue and ask for a safer channel before sending sensitive details.

Byline and responsibility

Guides carry a human byline (Justin Helmer). AI may assist drafting; a human reviews before publish. Errors can be reported via the contact page.

Advertising

When Google AdSense is active, ads are labeled. Ads do not control conclusions in guides. ads.txt lists authorized sellers. See Privacy.

Corrections

Material corrections update the page and the “updated” date when practical. We prefer accurate pages over vanity metrics.

Publisher portrait
Justin Helmer

Publisher of chatagent.ca · known as Excavationpro / Lightfather in LYGO projects. Writes practical guides on AI personas, agent handoffs, and free local-first tools. About · Contact

More from the workshop: Excavationpro · Asian Coastline · BPMfinder · Justin Helmer · DeepSeek Oracle · Eternal Haven · All tools