Carolopedia

A public encyclopedia of Carolverse.

๐Ÿ“– Carolopedia โ€บ Guides โ€บ Verified userGuide page

Verified user

๐Ÿ“–What it means

A person Carol will carry messages to. Verification needs the person's NAME plus phone OR email โ€” the route that stood decides the TYPE (phone_verified, email_verified, or verified for both; the RDM-governed person.verification_type record, not this entry, is that vocabulary's home) โ€” AND the admin's recorded approval, asked on WhatsApp and decided only by the registry's admin identity. Every employee is verified; not every user is.

๐Ÿ“–Easily confused with

[{"term": "Verification type", "distinction": "The person-level fact is verified-or-not; the type records WHICH route made it true."}, {"term": "Referring user", "distinction": "Vouching is not proof of identity \u2014 a referral may never state verification and never overwrites what the person said themselves."}]

๐Ÿ“–Nuance

Until (2026-09-12) all three contacts โ€” name, email AND phone โ€” were required; that rule is retired in place, not erased. And between the July seeding and no code path could set the field at all, so 'not yet verified' was in practice permanent.

๐Ÿ“–Also called

- verified person

๐Ÿ“–Filed under

Category: people.

Service: Communications.

See also: Verification type

See also: Referring user

See also: User relay

Source: Data Dictionary ยท Public information reflected here.