Skip to content
View raw

Trust and Recognition

A project update, a neighbor's endorsement, and an expert assessment each tell you something different. Together, they can give you more confidence in the work, or reveal questions you need to investigate.

We call these contributions trust signals: project updates, endorsements, evaluations, certifications, and funding records, each attributed to whoever provided it. Hypercerts makes them visible and connects them to their sources. Deciding which ones to rely on remains a matter of judgment.

Start with who published it#

Every record belongs to an AT Protocol account. Its DID identifies that account, and the repository's signed history lets software check that a version was published by it. A profile gives people a more readable introduction to the person or organization behind the account.

This answers “which account published this?” It is a starting point for asking “why should I trust it?” A familiar research organization, a local community group, and an unknown account may all publish assessments, but a reader will weigh them differently.

Also distinguish the publisher from the people named in the record. A platform might publish a receipt naming a funder and recipient. A team might name several contributors. Those names tell you what the publisher is saying; confirmation from the named parties adds another source.

Make recognition explicit#

Badges let a network or certifier recognize an account or a record, such as a project. A badge definition explains the recognition being offered. A badge award connects that definition to its recipient. A separate response lets the recipient accept or reject the award.

For example, a network could define a badge for a certification and award it to a project it has reviewed. An app displaying that badge needs to check who awarded it and whether that issuer is recognized by the certification scheme. The badge's name or icon alone tells you little.

An acknowledgement is another kind of response: it records acceptance or rejection of a subject or relationship. It can let someone confirm a contribution attributed to them, for example. The response is useful when the app checks that it came from the relevant account.

Some records also support additional signatures on their contents. These can provide further confirmation from a signer, separate from the signature on the publishing repository.

Trust grows through useful contributions#

A funder may value a specialist's technical assessment. Community members may give more weight to experiences reported by neighbors. Both can use the same connected records without agreeing on a single score.

More records do not automatically mean more trust. A contradictory evaluation may reduce confidence while making the overall picture more informative. A helpful app lets readers see the source, the reasoning, and the differences between accounts.

This matters for AI-assisted decisions too. An agent can follow the same links to evidence and assessments, rather than rely only on the polish of a project's written pitch. Its conclusions still depend on the sources and judgment rules it uses.

For record details, see Badges and Acknowledgements. Account & Identity Setup explains how accounts work in practice, including the Certified account service.

Next: Funding and Learning, where these signals become useful to the next funding decision.