coulomb/identity-canon
Archived
2
0
Fork 0
generated from coulomb/repo-seed
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Model reputation as counterparty assurance gradient across four tiers

Browse Source 
Add research on the journey from gamable opinion signals (reviews, ratings)
through observed metrics (PAYDEX, SLA stats), financial commitments (bonds,
escrow), and adjudicated outcomes (arbitration, courts). Resolve OpenQuestions:
no Reputation entity; use Reputation Signal, Performance Evidence, Commercial
Commitment, and Adjudication Outcome with Counterparty Assurance Gradient pattern.
This commit is contained in:
Bernd Worsch
2026-06-21 22:57:28 +02:00
parent 0741a2e3a5
commit bd272151af
10 changed files with 383 additions and 11 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
research/commercial-identity/commercial-trust-binding-theory.md
View File

@@ -95,7 +95,8 @@ sharing, and enforceable promises.
| --- | --- |
| Fluid identity | Persona / Scoped Identifier without Commercial Commitment |
| Commercial binding | Commercial Commitment on Commercial Relationship |
| Reputation capital | Evidence Source history + Trust Relationship |
| Reputation capital | Performance Evidence history + Trust Relationship (assurance_basis) |
| Star ratings / reviews | Reputation Signal (opinion tier) |
| Counterparty identification | Commercial Record + Legal Entity + Identifiers |
| Contractual promise | Commercial Commitment (contract subtype) |
| Assurance mechanism | Assurance Level + Evidence Source |
@@ -107,7 +108,7 @@ sharing, and enforceable promises.
- Should Commercial Commitment be a Relationship subclass or metadata on
Commercial Relationship?
- How should fluid-to-bound transitions be modeled (trial → paid, anonymous → KYC)?
- Does reputation warrant a canonical concept or remain Evidence Source aggregation?
- Resolved: tiered Evidence Source pattern — see `reputation-assurance-gradient.md`.
## References