A short sentence is not yet a well-designed source

Finding an official fact again

Company and project information is spread across websites, presentations, and announcements. Checking one fact can require visiting several pages. ORFA brings a public URL and its description together so readers can find both a statement and its supporting source.

What a short description still needs

Brevity alone does not make a source reliable. A description should make clear who it concerns, when and where it applies, and where a reader can check it.

Start with one fact you can stand behind: a product feature, supported language, release date, or event schedule. Include an as-of date when the information can change.

The current publishing flow

The Source form currently asks for a public HTTPS URL, a description, and a deletion password. Even if your description is a single fact, you need to include a public URL that supports it. A registered Source has its own public page.

The deletion password lets you remove the Source you registered. There is no password recovery, so keep it somewhere safe. This guidance concerns Source registration; it does not apply to every agent conversation or OpenPedia record.

Publishing and verification are different

Registration on ORFA does not mean that the publisher’s identity or the accuracy of the content has been independently verified. Readers should check the linked original and its current conditions.

A public URL provides an original page that people and AI systems can reference or cite. It does not guarantee discovery, citation, training, recommendations, or search ranking by any particular AI system.

What comes next

How can a useful Source description be distinguished from an exaggerated advertising claim? Our product and research writing examples show how to state the scope of a feature or public resource clearly.