Product documentation

How RSRCH data works

Understand RSRCH Sources, people, organizations, accounts, places, canonical URIs, evidence, AI enrichment, sharing, and public visibility.

Your working documents and imported contacts are private by default. Documents and blocks become public only when deliberately published. Public entity pages contain separately reviewed projections suitable for public display.

Public data model

Four kinds of public entity

RSRCH organizes public research as stable entities connected by typed relationships and supporting evidence. A public entity page is a reviewed snapshot of one entity, not a copy of your private research.

Online account

A provider-neutral public profile for an online identity. It can show the account kind, public handle, profile URI, and image. A reviewed relation can connect it to a person or organization without treating the account as that Party.

Party

A person or organization described by public names, descriptions, classifications, dates, images, relationships, and evidence when those facts are approved for display.

Place

A coarse public location: a locality, subdivision, or country. Exact addresses and coordinates are excluded.

Source

One citable referent, such as an article, dataset, social post, filing, patent document, or web resource. Its type, media kind, location, authors, publisher, and status remain explicit facts.

Party kinds

Person · Organization

Place kinds

Country · Locality · Subdivision

Account kinds

Automated account · Organization account · Personal account · Pseudonymous account · Shared account · Unclassified account

Private contacts and public Parties

An imported contact is a private workspace record, not a public Party. A public profile URL or identifier can contribute to a Party proposal only after explicit review. The contact owner, private contact record, email, phone, address, notes, and unreviewed handles do not cross into that public proposal.

Sources

A Source is one citable referent

A Source identifies the thing you cite. Its identity stays separate from the URL where it was observed, a particular version or fragment, and the evidence used to describe it. This keeps a corrected article, a moved web page, or a different edition from becoming a silent identity change.

A public Source page presents metadata, public relationships, evidence references, and an optional reviewed summary. It does not republish the article, post, media, dataset, or other content that the Source represents.

Resource types

Article
Archival record
Book
Book chapter
Blog post
Dataset
Decision
Filing
Legislation
News article
Patent document
Proceeding
Registry record
Report
Social post
Software artifact
Standard
Trial
Web resource
Other

Media kinds

Audio
Data
Image
Interactive
Mixed media
Software
Text
Unclassified media
Video

Resource facets

Availability: Whether the public resource is available, restricted, private, deleted, missing, or temporarily unavailable. Values: access restricted, available, deleted, not found, private, temporarily unavailable, unknown.
Correction state: Whether the resource is original, corrected, superseded, or not yet classified. Values: corrected, original, superseded, unknown.
Editorial standing: Whether the resource is active, cancelled, retracted, or not yet classified. Values: active, cancelled, retracted, unknown.
Patent edition: The edition of a patent document, such as an original, correction, reissue, or supplement. Values: correction, original, other, reissue, supplement.
Patent stage: The stage represented by a patent resource, such as an application record, publication, grant, or search report. Values: application publication, application record, grant, other, search report.
Social post form: Whether a social post is original, a reply, a repost, or a quote post. Values: original, other, quote post, reply, repost.
Social thread role: Whether a social post stands alone, starts a thread, or belongs to a thread. Values: member, root, standalone, unknown.
Web article form: The editorial form of a web article, such as analysis, opinion, a live blog, or a press release. Values: analysis, live blog, opinion, other, press release, standard.

Identifiers and canonical URIs

Stable identity, separate from spelling

Each public entity has an opaque RSRCH locator. The URI stays stable when a display name, handle, or external URL changes. Knowing a URI does not grant access, and a URI resolves only while the current public snapshot remains eligible for display.

Online account: https://rsrch.chat/account/<opaque-locator>
Party: https://rsrch.chat/party/<opaque-locator>
Place: https://rsrch.chat/place/<opaque-locator>
Source: https://rsrch.chat/source/<opaque-locator>

When an entity is eligible for public display, its canonical URI is the dedicated page used for metadata, reviewed summaries, citations, search discovery, and sharing previews. Published documents use a separate canonical address: https://rsrch.chat/<username>/<slug>/pub.

How normalization works

Recognize the scheme. A web URL, social handle, publication identifier, and patent identifier follow different rules.
Preserve the observed form. RSRCH can show the public spelling while using a normalized value for exact comparison.
Match conservatively. Only compatible, exact bindings can be reused automatically.
Treat similarity as evidence. Redirects, similar names, shared domains, and content similarity can trigger review, but do not prove that two entities are the same.

Context matters. A social handle is interpreted with its provider, a publication or patent identifier with its scheme and authority, and a web address as a URL. RSRCH can retain the spelling people recognize while keeping the normalized comparison value separate.

Evidence and freshness

Public facts keep their context

Public entity pages can include evidence context with supporting Sources, confidence, observation dates, validity windows, and content fingerprints. Summaries, identifiers, and relationships explicitly reference their supporting evidence. Relationships are directed and typed, so “authored by,” “published by,” and “official account of” remain different claims.

RSRCH checks whether referenced entities and evidence are still publicly available. If a linked page is no longer eligible, its label can remain readable without exposing a stale link. A public page can disappear when its evidence, rights, dependencies, or current identity no longer support publication.

Confidence vocabulary

Confidence records the kind of support behind evidence and how a claim was formed. It is not a universal probability score.

Direct authority
Registry evidence
Publisher evidence
Aggregated evidence
Extracted evidence
Inferred evidence
User-supplied evidence

Supported relationship vocabulary

cites
references
is identical to
is version of
is new version of
is previous version of
is expression of
is manifestation of
is item of
is part of
is published in
is supplement to
is derived from
reviews
documents
describes
is translation of
corrects
retracts
obsoletes
supersedes
is preprint of
official copy of
archive capture of
amends
repeals
commences
consolidates
codifies
enacts
implements
transposes
filing in
decision in
affirms
reverses
vacates
overrules
distinguishes
replies to
reposts
quotes source
thread part of
cancels
syndicated from
mirror of
publication of application
grants application
corrects publication
reissues
enters regional phase
claims priority to
is cited by
is referenced by
has version
has new version
has previous version
has expression
has manifestation
has item
has part
publishes
has supplement
has derivation
is reviewed by
is documented by
is described by
has translation
is corrected by
is retracted by
is obsoleted by
is superseded by
has preprint
has official copy
has archive capture
is amended by
is repealed by
is commenced by
is consolidated by
is codified by
is enacted by
is implemented by
is transposed by
has filing
has decision
is affirmed by
is reversed by
is vacated by
is overruled by
is distinguished by
has reply
is reposted by
has quote post
has thread member
is cancelled by
is syndicated as
has mirror
has publication
is granted by
is corrected publication by
is reissued by
has regional phase
is priority claimed by
advisor to
board member of
founded by
investor in
member of
operates brand
owned by
parent of
predecessor of
subsidiary of
successor of
affiliated with
author of
authored by
contained by
contributor to
controlled by
created by
creator of
current place
employed by
employs
has contributor
headquarters
located in
official account of
part of
position at
principal office
published by
publisher of
represents
same as

Summaries and enrichment

AI proposes; evidence and people decide

Enrichment can propose summaries, topics, profile hints, people and organizations mentioned by a Source, identifiers, and related Sources. A proposal does not establish a fact, merge identities, or make information public.

When useful, enrichment can search the public web and retrieve readable page text for relevant results. That material supports structured candidates; enrichment does not publish the retrieved page content.

People and organizations mentioned by a Source
Candidate public profile facts
Candidate author, language, publisher, site, and resource subtype facts
Candidate related Sources
Evidence-linked summary sentences
Candidate topics

Discover and read public source material.Enrichment can use the Source itself, public web search, and readable text from relevant pages.
Produce structured candidates.Suggested facts and summary sentences remain separate from accepted public data.
Check support.Each proposed summary sentence must point to retained source text and pass reference and meaning checks.
Review and promote.A person accepts or rejects the proposal before an approved summary can enter a public snapshot.

Sharing and visibility

Each sharing action has a bounded scope

Surface	What becomes visible
Private workspace	Only the owner and people with an explicit document grant can read the working document. Imported contacts remain private.
Shared document	A named Suite member receives read or edit access to that document. Private chat and unrelated documents do not become visible.
Shared block	A named Suite member can receive read or edit access to the selected block and its descendants. Sign-in and an active grant are required; the link alone does not grant access.
Published block	A deliberate, read-only checkpoint of the selected block and its descendants becomes public at a shareable link. It is not listed for search indexing and changes only when the owner updates the publication.
Published document	A deliberate, read-only checkpoint of the authored document becomes public. Later private edits do not change that published revision.
Public profile directory	A username page lists that member's current published documents. It is a public discovery page, not a biographical profile or a view into private workspace activity.
Public entity	A separately reviewed public snapshot describes one Source, Party, Account, or coarse Place. It is not a view into the private workspace or the full research graph.

Public entity pages can contain

Public titles, names, descriptions, and reviewed summaries
Public identifiers, profile URLs, topics, and typed relationships
Evidence references, confidence, observation dates, and validity dates
Source resource type, media kind, availability, authors, and publisher
Approved Party, account, and coarse Place profile facts

Public entity pages exclude

Private documents, chat, tags, grants, and imported contacts
The full article, post, media, dataset, or other content represented by a Source
Email addresses, phone numbers, and private rolodex fields
Exact street addresses and coordinates from Party, Account, and Place profiles
Private system identifiers and access-control records

A published document or block exposes the authored checkpoint selected by its owner, so review that content before publishing. Shared blocks remain signed-in collaboration surfaces. Published blocks are public but excluded from search indexing. Published documents, public profile directories, and approved public entity pages are intended for public discovery.

Public profile directories use https://rsrch.chat/<username>and list current published documents. They do not assert a person's or organization's identity beyond the visible Suite username and publication list.

Changes and withdrawal

Publication is deliberate and reversible

Publishing a document creates an immutable public checkpoint. Later private edits create new working state and do not rewrite that checkpoint. Publishing or updating a block likewise creates a public checkpoint of that selected subtree. A public entity snapshot is reviewed separately from document and block publication.

Unpublishing, withdrawing approval, suppressing an entity, erasing a required dependency, or losing the right to display it removes the current public route. Missing and unavailable public pages use the same not-found response so the route does not reveal private state.

Availability

Coverage grows through review

Not every Source, identifier scheme, or public entity has a page. Public catalog and enrichment features can be introduced in phases, and an entity becomes discoverable only after its current public projection is approved. An opaque URI pattern describes identity; it does not promise that a page exists.