Editorial standards built for useful technical guidance

Primary sources before summaries

For platform behavior, we prefer the platform maker's current documentation. For First Light Beacon capabilities, we use the current public product page, help material, or verified product behavior. Every material external technical claim should link close to the statement it supports.

Third-party commentary can help identify questions, but it does not replace an official source when one is available.

Native behavior and FLB capability stay separate

A guide should first explain what the trading platform already does, then identify the operational gap, and only then explain where an FLB product may fit. We label defaults, configurable behavior, limitations, and inferences so readers can tell them apart.

We do not present monitoring software as a guarantee, trading indicators as predictions, or configuration guidance as a universal prescription.

Dates, links, and claims are checked

• Confirm that the page answers the stated question before introducing a product.
• Check cited technical statements against the linked source.
• Match visible FAQs, dates, authorship, and structured data.
• Use a reviewed date only when the content and its material links were reviewed.
• Avoid invented tests, software versions, outcomes, testimonials, or performance claims.

AI can assist; sources remain the authority

AI tools may assist with research, drafting, editing, code, and quality checks. That assistance is disclosed on a guide when it materially shaped the work. AI output is not treated as a source: technical statements are checked against the primary references linked from the page.

Material updates should be visible

When a platform, product capability, price, or material recommendation changes, we update the affected page and its reviewed date. If you find a technical error or a broken primary-source link, send the page and the specific issue through the First Light Beacon Help Center.