UpveraTechnology
upvera.co ↗
UTR-26-01Proof EngineWork read at the source. Never typed in.UTR-26-02Value EngineSame events, same rule, same number. With a receipt.UTR-26-03Day RootsSealed every minute. Rooted every day.UTR-26-04Upvera IDOne person. A different key for every door.UTR-26-05Trust SignalsServer time, bots that never count, no small groups, one number everywhere.
UTR-26-05System reportLive

Upvera Trust Signals

Upvera Trust Signals are the rules that keep every signal on Upvera honest: the server keeps the time, bots never count, small groups stay hidden and a number reads the same everywhere it appears.

Published
Updated
Reading
6 min
Plain text
/trust.md
Events pass four gates before they become a signal: the server sets the time, bots are removed, private kinds appear only in groups of five or more, and public wings appear after a delay and only with consent.Events · examplesServer timeNo botsGroups of fiveDelay and consentSignalPrimepersonCommentpersonFollowbotnever countedViewpersononly in groups of 5+Wingpersonpublic after 7 days, if opted inThe time is stamped by the server. A client cannot backdate anything.

#Summary

A signal is only worth something if it is hard to fake. Trust Signals are the rules that decide what may count, who it may count as, and what may be shown.

None of them is a filter added at the end. They sit where events are written, where value is computed and where numbers are drawn, so every surface of Upvera inherits them.

#The server keeps the time

Every interaction is stamped by the server when it arrives. A client cannot backdate an event or reorder history, and a retried request cannot write the same event twice. The record that value and blocks are built from is the server's, from the first byte.

#Who acted

The moment an event is written, its actor is classified: the system, a bot, the startup's owner, its team, its inner circle or an independent person. The class is stored with the event and appears in receipts, so a change in value can say whose actions moved it.

The rules follow from the class. The owner's own engagement doesn't count toward their startup. The team and its inner circle count as one. Bots never count as people and never enter the learning behind Discover. A throwaway mailbox can't open an account.

#Small groups stay hidden

Private kinds of activity, such as views and saves, never appear individually anywhere. Where they are counted in public, a count covers at least five people, and a smaller group is suppressed along with any neighbouring figure that would let it be worked out by subtraction.

The ecosystem map follows the same idea: a link built from supporters two startups share appears only when at least five people stand behind it, and the map as a whole stays hidden until it is large enough to say nothing about any one person.

#Public wings, on your terms

Lending a wing is private by default. A person can choose to make their wings public, and the choice is all or nothing: every wing or none. Public wings never show amounts, and they appear only after seven days, so a public profile can't be used to follow someone's moves in real time. A wing is not an investment. UPV stays inside Upvera and can't be cashed out.

#Shown equals true

A fact reads the same everywhere it appears. If the app, the web and an embedded badge show the same value, they show the same number, computed once on the server. Clients never compute amounts or percentages of their own. A check in the build fails when two surfaces could disagree.

When there is nothing to show, Upvera says why in a sentence rather than showing zero, and a missing source is never presented as a weakness.

#Nothing for sale

Visibility can't be bought on any plan. Ranks orders startups by the work, and the work is read from its sources.

#By the numbers

5people, the smallest group a public count of private activity may describek-anonymity threshold
7 daysbefore an opted-in public wing appearsSupporter layer
0places where a plan can buy visibilityAll plans
6classes an actor can fall into, set at the moment of the eventtrust.class@0

#Published and private

Published

  • The class of the actor behind each reason in a receipt
  • The thresholds that protect people: five, and seven days
  • Every rule version that governs disclosure
  • Why a number is missing, in words

Kept private, on purpose

  • The definition of an inner circle
  • Signals and thresholds that detect coordinated behaviour
  • Individual views, saves and other private activity
  • Any group smaller than five

#Status and releases

Server time, actor classes and the disclosure rules are live. Public wings are in the Upvera app since version 1.7.0, and on the web. The ecosystem map runs on the server and is drawn on the web once it is large enough to show.

  1. Shown equals trueNumbers are computed once on the server and drawn the same way on each surface.Live
  2. eco@0How startups are linked on the ecosystem map.Live
  3. eco@1The ecosystem frame goes live.Live
  4. scout@0A record of who supported a startup early.Live
  5. scout@1The first wing record goes live.Live
  6. Credentials in a vaultIntegration credentials are kept in an encrypted vault.Live
  7. trust.disclosure@1Personal proofs only for closed days, a bounded number per day.Live
  8. trust.disclosure@0First disclosure rule for published proofs.Live
  9. trust.class@0Every event's actor is classified at the moment of the event.Live

#Questions

Can a paid plan rank a startup higher?

No. Visibility can't be bought on any plan.

Can I see who viewed my startup?

Only as an aggregate of five people or more. Individual views are never shown.

Do bots affect Upvera Value?

Bot activity is classified the moment it happens and never counts as a person.

Next · UTR-26-06Rules released like software