Attested Credential Registry¶

Verification registry — instantiates Reputational Signal Governance

Anchors reputation to independently verified credentials and attestations, so trust does not have to rest on informal history alone.

An Attested Credential Registry supplies the part of a reputation that informal history cannot: facts that a trusted third party has checked and stands behind. It holds credentials — licenses, certifications, audits, verified identities — each bound to a subject and each carrying a chain back to the authority that issued or verified it. Its defining move is independence: the signal's weight comes not from the crowd's opinion but from an external attestor whose reputation is now on the line. That makes it the right tool exactly where peer history is thin, new, or gameable, and where a wrong trust decision is expensive.

Example¶

A hospital brings on a locum physician for a three-month gap. Peer ratings and prior-shift anecdotes are nowhere near enough to grant operating privileges, so before the doctor sees a patient the credentialing office runs the attested registry: it verifies the medical license directly with the state board, confirms board certification with the specialty board, checks the national practitioner data bank for malpractice and sanction history, and records each check with its source and date. This is primary-source verification — the fact is confirmed with the issuer, not taken from the applicant's own CV.^[1]

The registry entry is not "colleagues say she's good." It is "license #—— active and unrestricted, verified with the board on this date; certification current; no reported sanctions." That anchored bundle is what lets a stranger institution extend real trust fast — and it is scoped to her, a single verified identity, so the standing cannot be borrowed or spoofed by someone else.

How it works¶

Bind each claim to a verified subject. The registry first fixes who the credential belongs to (a resolved, verified identity), so attestations attach to the right actor and cannot be transferred or impersonated.
Verify at the source. A claimed credential is confirmed with the issuing authority, not accepted on the subject's word, and the verification's provenance and date are stored with it.
Carry the attestor forward. Each entry names who vouched and how, so a reader can weigh the anchor by the credibility of its source.
Expire and re-verify. Credentials have validity windows; the registry flags lapses and re-checks on a cadence rather than trusting a one-time green light forever.

Tuning parameters¶

Verification depth — self-attested → primary-source verified → independently audited. Deeper is more trustworthy and much slower and costlier.
Attestor independence — how arm's-length the verifier is from the subject. Greater independence hardens the anchor but narrows who can supply it.
Required-credential set — which claims must be attested versus merely asserted. A wider mandate raises assurance but excludes capable actors who lack paperwork.
Re-verification cadence — how often live credentials are rechecked. Frequent rechecks catch lapses early at ongoing cost.
Fail-open vs fail-closed — what happens when a credential can't be verified: provisional access, or none until confirmed. Fail-closed is safer and slower.

When it helps, and when it misleads¶

Its strength is that it is a hard anchor in a sea of soft opinion — it resists fabricated history and gives a cold-start subject something solid to stand on, which is why regulated and high-stakes settings lean on it. It pairs naturally with informal signals rather than replacing them.

It misleads through credentialism: a valid license certifies a floor, not good conduct, and treating the checkmark as a character reference reads far more into it than verification supports. It also carries real exclusion cost (capable people without formal papers) and verification expense, and its classic misuse is letting a "verified" badge imply an endorsement the registry never made — verification of a fact quietly presented as approval of the actor. The discipline that keeps it honest is to scope attestation tightly to what is actually verifiable, state what each anchor does and does not certify, and let behavioral signals carry the rest.

How it implements the components¶

independent_audit_or_attestation_anchor — its core: grounding reputation in claims a third party has independently verified and stands behind.
reputation_subject_boundary — verification resolves and fixes whose reputation this is, binding each credential to one confirmed identity so standing can't be borrowed or spoofed.

It deliberately does not capture day-to-day conduct or gather first-hand testimony — ongoing behavior is Contribution Ledger's job, and peer endorsement is Peer Reference or Vouching's; the registry anchors verified facts, not lived experience.

Instantiates: Reputational Signal Governance — the registry supplies the externally verified anchor that keeps a reputation from resting on informal history alone.
Sibling mechanisms: Peer Reference or Vouching · Contribution Ledger · Verified Transaction History · Rating and Review System · Reputation Score or Standing Index · Decay-Weighted Score Update · Appeal and Correction Workflow · Complaint and Resolution Record · Moderation Record with Reentry · Sybil, Collusion, and Brigading Detection · Trust-Tier Badging · Reputation Portability Protocol

Notes¶

The registry and Peer Reference or Vouching are the two ways to import trust an actor's own history can't supply, and they differ on who backs the claim. A registry entry is backed by an institution's verification of a fact; a peer reference is backed by an individual's first-hand experience. High-stakes, standardized trust wants the registry; situational, hard-to-formalize judgment wants the peer channel — and mature systems run both.

References¶

[1] Primary-source verification — confirming a credential directly with the authority that issued it rather than accepting a copy from the holder — is the standard used in healthcare credentialing precisely because self-reported credentials are the easy thing to forge. ↩