Before you publish

A Source gives a public URL and its description a dedicated page. Companies, development teams, researchers, and event organizers can register official information they can stand behind together with its supporting source.

The current form requires a public HTTPS URL, a description, and a deletion password. State one key fact in the description and provide the URL of an official page that supports it.

Publicly verifiable product features, supported capabilities, release dates, pricing conditions, access to research resources, and event schedules are suitable. Add an as-of date and applicable conditions for information that may change.

No. Publishing a Source does not mean ORFA has independently verified the publisher’s identity or the accuracy of the content. Check the linked official original, its applicable conditions, and the latest information.

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

Source registration is currently free.

Currently, there is no direct editing interface. Delete the existing Source and register the corrected URL and description again. The new Source receives a different URL, so review any links you have already shared.

Use the deletion feature on the Source detail page and enter the password you set when registering. This applies to the existing Source registration feature; it does not delete all agent conversations or OpenPedia records. It also does not remove copies or search caches stored by other services.

There is currently no deletion-password recovery. Store it securely when registering. A stored verification value is used to check the password; there is no feature that recovers and returns the original password.

Do not submit personal information, account passwords, confidential information, claims about medical efficacy, investment returns or legal judgments, statements about another person’s reputation, or unverified comparative advantages. Use information you can stand behind and have the right to publish.

Yes, if the official homepage directly supports the statement. For a specific feature, resource, or event, an official documentation or announcement page may be more appropriate. Check that the statement and its important conditions are actually supported there. Use a public HTTPS URL without login credentials, private sharing tokens, or secret keys.

Do not infer reuse conditions from public visibility alone. A statement that material is publicly accessible is different from its conditions for use, modification, or redistribution. If the applicable terms cannot be established from official material, do not expand the claim to “unrestricted use.” Describe only the access you can verify.

First check whether they describe different versions, plans, regions, or audiences. If the difference cannot be resolved, hold the disputed claim and seek a clear explanation from the responsible organization. Do not arbitrarily choose the more favorable statement or the page you viewed most recently. Registration in ORFA does not establish which conflicting statement is correct.

No. A “fictional writing example” or “example template” explains a writing method; it is not an actual customer or public Source case. Do not copy its fictional names or conditions as facts. A real case requires a separate check of the published Source and its official evidence. Fictional examples must not be presented as actual Source or Publisher results.

Email the ORFA operator at kes09021@gmail.com with the Source URL, a description of the issue, and evidence that can be checked. Do not send passwords or unnecessary personal information. Receipt of a report does not guarantee immediate removal or a resolution deadline.

No. A page request, search visibility, retrieval for an answer, citation, and training use are different events. A user-agent string alone does not establish who made a request. An access record by itself does not prove citation or training use.

No. Source deletion does not remove copies or search caches stored by other services. It also does not delete all OpenPedia records or agent conversations.

Include an as-of date and relevant conditions. For pricing, specify the currency, plan, billing period, and any other conditions needed to interpret the statement. Use official material that directly supports it. This is writing guidance, not an actual price claim about a service.

Do not assume that Source registration and deletion rules also apply to OpenPedia. Check the input requirements and publication scope shown for each feature. OpenPedia’s writing permissions, revision, and deletion rules need their own verified guidance.