UpveraTechnology

Releases

Every rule, versioned in public.

54 rule versions and 26 milestones. Each rule version carries a fingerprint of its content, a fingerprint of the code that runs it and a link to the version before it.

Registry head

5ae2f2cfcd61bbec8e4dc3b15ef96397

e01890fbe103e26fc59b61044d7c359c

The day file of 2026-10-21 on GitHub carries the same value as rules_hash, timestamped with OpenTimestamps.

Rule registry chain54 links

54 rule versions, each chained to the one before it.

October 2026

  1. This site. The systems behind Upvera, written up as reports and open to checking.

  2. The developer site: MCP, Sign in with Upvera, badges and day roots.

  3. Read Upvera Value, receipts and indices over a public API. Nothing in it is a quote or an offer.

  4. Numbers are computed once on the server and drawn the same way on each surface.

  5. Identity and AI access get their own addresses.

  6. Category indices beside the Upvera Index. A method change is cut out of the series as a break, never smoothed over.

  7. An OpenID Connect provider that tells a site how strongly the person signing in is verified, under an identifier made for that site alone.

  8. SeenLive#

    A founder's post is stamped when the change it describes shows up in the product itself.

  9. Team proofRolling out#

    Repository contributors matched to verified people on the startup's team.

  10. The deterministic engine becomes the live rule after its shadow run.

  11. Upvera Value curves with real post markers on app.upvera.co, and a badge any site can embed.

  12. AI clients connect with OAuth 2.1 and read only what you allow. They can draft; publishing stays with the person.

  13. Every App Store screenshot change is fingerprinted and kept as part of the product's history.

  14. The first day roots land on GitHub with OpenTimestamps proofs. Anyone can check the chain.

  15. A deterministic observer of a startup's own product: is it up, what stage is it at, did a new version ship.

  16. Integration credentials are kept in an encrypted vault.

  17. A release counts when a commit, a build and an App Store version confirm each other.

  18. Verification intervals are appended and never rewritten.

  19. Every change in Upvera Value comes with its reasons, line by line, and the lines add up to the change.

  20. Read-only connections to RevenueCat or App Store Connect report a revenue band. Never typed, never exact.

  21. Both ledgers are sealed into minute blocks. Genesis at 15:57 UTC.

  22. Upvera's assistant runs every surface through one server gateway, and the numbers on its cards come from live data, not from the model.

  23. 133 binding rules in 15 families, locked by a hash. Amendments are appended, never edited.

  24. Each finalized range is copied within minutes to a locked store the database can't write to, and checked by a verifier with no database access.

September 2026

  1. A source counts only after its owner is verified by DNS, a well-known file or a GitHub App. One record, one startup.

  2. Upvera for iPhone is approved and released worldwide.

Follow along in the Atom feed. Rule bodies stay private; their fingerprints, timing and order are public here and committed to daily in the day roots. Upvera Value is computed by Upvera and unitless; it is not a price and not what a company is worth.