---
name: Reputation
slug: reputation
type: social_infrastructure
status: running
version: 4.1.7
released: "prehistory"
maintainer: Everyone Who Has Ever Watched You
dependencies:
  - perception
  - consistency
  - memory
  - gossip_networks
  - time
license: Proprietary (you do not own this)
tags:
  - identity
  - social-capital
  - trust
  - risk-surface
  - enterprise-grade
---

Reputation

What It Actually Is

A distributed ledger of other people's opinions about you, which you cannot edit, only influence, and only slowly.

Product Overview

Reputation is a real-time, multi-stakeholder trust aggregation platform built on social memory and maintained by parties who did not sign any NDA. It operates without your consent, runs on infrastructure you do not control, and is backed by a 99.97% uptime SLA (the 0.03% downtime is called death).

It is not a personal branding tool. That is a different, much sadder product.

"I thought I was the admin. I was not the admin." — verified user

Reputation integrates natively with shame, career trajectory, and the internet, with no opt-out available at this time.

Pricing Tiers

Tier	Cost	What You Get
Free	Existing in public	A reputation you did not design
Growth	Sustained good behavior over years	Modest trust, forgiveness on minor bugs
Enterprise	Institutional power or fame	High visibility, amplified failure modes
Legacy	Death	Fixed. No further patches.

Note: Upgrading tiers requires compounding deposits of consistency. Downgrading is instantaneous and often free.

SLA and Support

Recovery Time Objective (RTO): 6 months to 6 years, depending on severity of incident.
Recovery Point Objective (RPO): Pre-incident reputation state is not guaranteed to be restorable.
Support channels: Apologies, time, demonstrated change. Chatbots not accepted.
Escalation path: public apology (high risk, irreversible, consult legal).

Reputation SLAs are not contractually enforceable. No court can compel belief.

Known Bugs

Halo effect: A single positive signal inflates all unrelated trust metrics.
Horn effect: Inverse of above. Equally irrational. Much faster.
Recency bias: Users weight last interaction at approximately 400% of historical average.
Survivorship distortion: Reputations that recover are visible. Ones that do not are not discussed, which skews user expectations about recoverability.
Context collapse: A message sent to one stakeholder group renders incorrectly across all others. No patch scheduled.

Deprecation Notice

Affected versions: Any reputation built primarily on a single platform, role, or relationship.

Single-threaded reputations are deprecated. Consolidating all social capital into one context (one employer, one community, one identity) creates catastrophic single points of failure. We strongly recommend diversifying across multiple stakeholder environments before your next major incident.

End-of-life for affected versions: Whenever the context disappears. Which it will.

Changelog

v4.1.7

Improved latency for reputation transfer across professional networks.

v4.0.0

We owe users an apology for the early internet era. Permanent indexing of youthful errors was shipped without adequate user notification. We are sorry. We are not going to fix it.

v3.2.1

Gossip throughput increased following urbanization. This was not intentional. It was also not avoidable.

v1.0.0

Initial release in small tribal communities. Worked as designed. Did not scale.

FAQ

Can I delete my reputation? You can relocate. This is not the same thing.

What if the reputation is inaccurate? Please submit a correction to everyone who holds it, individually, over a period of several years.

Is reputation transferable? Partially. See: references, inherited status, nepotism.

drafting spec…