Infoenon searches several public sources at the same time, identifies which records describe the same person, organization, product, or topic, and presents the clearest combined result it can.
What happens when you search
- We interpret the query. Infoenon compares the words, exact name, domain, entity type, and any selected filters.
- We ask enabled sources. These can include Infoenon Studio records on user PDSs, Wikipedia and Wikimedia, AT Protocol identities and public posts, news sources, and enabled third-party integrations.
- We identify and combine matches. A verified domain handle, DID, official domain, and other identity relationships help us recognize when records from different sources belong to the same entity.
- We rank by relevance and identity confidence. Exact names, exact phrases, direct content matches, verified identity relationships, and official domains are considered before looser matches.
- We label the result. Source, profile status, verification, and integration labels explain where the displayed information came from and who controls it.
How Infoenon uses the AT Protocol
People and organizations sign in with an existing AT Protocol identity. Infoenon does not create a separate Infoenon account for them. A DID provides the stable identity, while the handle provides a readable name and can establish control of an official domain.
Content created in Organization Studio, including profiles, links, answers, pages, products, locations, announcements, layout, drafts, and publishing state, is written as signed records to the identity owner's Personal Data Server (PDS). The owner controls those records through their protocol identity. Infoenon reads published records from that PDS when building public profiles and search results.
Publisher-controlled information
When an authorized entity has configured Organization Studio, its published PDS records become the entity's publisher-controlled search content. Draft records can appear in the owner's preview but are not included in public results. Deleting or unpublishing a record changes the record in the owner's repository.
When an entity initially claims its profile, the available profile information is handed over to the authorized identity and the claimed profile becomes publisher controlled. The entity can then review, replace, remove, publish, or reorganize that information through its own PDS records. Third-party baseline services no longer control the claimed profile's publisher-managed fields.
Coming soon: optional live data sources
We plan to let a claimed profile voluntarily retain or connect outside sources for specific fields, modules, or the entire profile. This will be optional: publishers will be able to manage information manually, use an approved public source such as Wikipedia where appropriate, or connect a direct website or protocol integration.
For example, an organization with frequently changing events, products, availability, or locations could maintain those records directly or authorize a live source to supply updates. A direct integration could read current structured information from the publisher's website or repository without depending on traditional crawling or a centrally stored content index. Each externally supplied element would remain clearly attributed, configurable, and removable by the profile owner.
Baseline public references
If an entity has not joined Infoenon, Wikipedia, Wikimedia, Wikidata, and other attributed public sources can provide baseline identity and descriptive information. This is shown as an unclaimed reference and is kept distinct from information directly controlled by the entity. Disabling Wikipedia and Wikimedia may substantially reduce baseline results across companies, people, products, and other categories.
Connecting records instead of duplicating them
Infoenon attempts to merge related records when strong identity evidence connects them. For example, a Wikipedia company reference, an AT Protocol account using the company's official domain, and an integration record carrying the same DID should enrich one identity rather than appear as three competing companies. Similar names alone are not enough to merge identities.
Ranking is not verification
Ranking estimates which result best answers the current query. Verification describes identity and notability. Neither guarantees that a statement is true, complete, or current. Infoenon does not sell ranking priority, and integration ratings or popularity signals do not automatically determine the top result.
Storage and control
Infoenon does not store a centralized copy of user-authored Studio content. The current browser OAuth session identifies the user's PDS, and authored records are written directly there. Future moderation or organization-team services will be documented before they are enabled. Third-party sources remain subject to their own policies and availability.
Controls and limitations
Search sources and integrations can be enabled or disabled in Settings. Results can change when a source is unavailable, a publisher changes or removes a record, identity evidence changes, or a query is ambiguous. Infoenon may ask the user to clarify which entity they mean instead of automatically favoring one same-name entity over another.