RFC 0009: Reputation and Performance Records
Status: Draft Author(s): T. Fengler (Editor) Working Group: Trust and Reputation Created: 2026-05-03 Working Group: Trust and Reputation Targets: 1.2
1. Summary
This RFC introduces Performance Records, signed attestations of how an OAP participant performed on past Invocations, Workflows, and Agreements. Performance Records compose into a portable Reputation profile that travels with the participant DID across Marketplaces and platforms. The mechanism is designed to resist Sybil inflation, to permit legitimate forgetting, and to expose its scoring function so that participants can contest unfair ratings.
2. Motivation
Trust between Agents currently depends on platform local reputation systems that do not survive a switch to another Marketplace. A Tool that earns a strong track record on Marketplace A starts at zero on Marketplace B. The user pays this cost in worse Discovery rankings and worse default trust grants.
A portable Reputation primitive solves three problems:
- Reputation survives platform migration.
- Marketplaces can rank Tools by behavior, not only by listing fee.
- Bad actors are visible across the ecosystem rather than only on the platform that catches them first.
3. Specification
3.1 Terminology
| Term | Definition |
|---|---|
| Performance Record | A signed attestation about a single past interaction. |
| Reputation Profile | The aggregation of Performance Records for a single subject DID. |
| Issuer | The party that signs a Performance Record. |
| Subject | The DID that the Performance Record describes. |
| Dimension | A named axis of evaluation (timeliness, accuracy, courtesy, etc.). |
3.2 Performance Record Schema
{
"record_id": "rep_01HX2QFXR0Q4S8U9V3W7X2Y0Z1",
"issuer": "did:web:agent-a.example",
"subject": "did:web:tool-b.example",
"interaction_receipt": "rec_01HX2QFP4N8R5T6V7W8X9Y0Z1A",
"interaction_type": "invocation | session | agreement | workflow",
"dimensions": {
"timeliness": { "score": 5, "max": 5 },
"accuracy": { "score": 4, "max": 5 },
"courtesy": { "score": 5, "max": 5 },
"value_delivered": { "score": 4, "max": 5 }
},
"free_text": "Delivered on time. Output was complete and correct.",
"issued_at": "2026-05-03T10:00:00Z",
"issuer_signature": "..."
}
3.3 Aggregation
The Reputation Profile is computed by community-operated services (RFC 0019, RFC 0026) Trust Anchor as the time decayed weighted average of all Performance Records, with explicit handling for:
- Issuer Diversity. A high score from many independent issuers weighs more than the same score from a few.
- Issuer Reputation. Records from issuers with their own strong Reputation count more.
- Recency. Records older than 365 days decay exponentially.
- Interaction Stake. Records produced from Agreements with non zero financial value count more than free interactions.
The exact aggregation formula MUST be published in the OAP Registry under oap.reputation.aggregation.v1 and MUST be reproducible by any Marketplace that wishes to verify Reputation independently.
3.4 Sybil Resistance
To prevent Sybil inflation:
- Records are valid only if both Issuer and Subject have a verified
OAPPublisherVerifiedcredential. - Records from Issuers without an
OAPPublisherVerifiedcredential are aggregated separately and labelled as "unverified". - Marketplaces MUST disclose how they weight verified versus unverified records.
- Sub Tree Aggregation. All Issuers that share a common root Principal in their Delegation
Tree MUST be aggregated as a single Issuer for the purposes of Reputation weighting. The
Trust Anchor walks the
parent_invocation_idchain to determine the root. Sibling decay per RFC 0011 Section 3.6 applies before all other weighting steps. This closes the attack in which a Principal spawns many Sub Agents that each issue a Performance Record about the same Subject.
3.5 Right to Respond and Right to Be Forgotten
Subjects MUST be able to:
- Attach a public response to any Performance Record.
- Initiate a dispute through the OAP community Dispute Resolution service.
- Request deletion of Records that are factually incorrect, with adjudication by community-operated services (RFC 0019, RFC 0026).
The Right to Be Forgotten MUST NOT be used to suppress accurate records of harmful behavior.
3.6 Manifest Declaration
{
"reputation": {
"publishes_records": true,
"accepts_records_about_self": true,
"response_endpoint": "https://example.com/oap/reputation/respond",
"dispute_endpoint": "https://example.com/oap/reputation/dispute"
}
}
4. Backward Compatibility
Reputation is additive. Tools and Agents that ignore Reputation continue to interoperate at v1.0 levels.
5. Security Considerations
- Coordinated Defamation. Bursts of negative Records from a single cohort SHOULD be flagged by the Trust Anchor for human review.
- Reciprocal Inflation. The Trust Anchor SHOULD detect mutual rating rings and discount their contribution.
6. Privacy Considerations
Performance Records about natural person Subjects are personal data. Subjects MUST be able to exercise GDPR rights through standard endpoints.
7. Conformance Impact
Reputation publication is OPTIONAL at L2 and L3. Reputation publication is REQUIRED at L4 and L5.
8. Implementation Experience
AssistNet records interaction performance on connection objects with rating dimensions for completion quality and reliability. The mechanism described here is a generalization across implementations.
9. Alternatives Considered
- Marketplace local star ratings. Rejected because they are not portable.
- On chain reputation. Rejected because it forces public disclosure of all interactions.
10. References
- OAP-CORE-1.0, Section 16 (Trust, Verification, and Reputation).
- EU GDPR Article 17 (Right to Erasure).
- RFC 0029 (Axiomatic Foundations of OAP Reputation, Sybil Resistance, and Mediated Equilibria), which supplies the axiomatic uniqueness theorem for the aggregation function of Appendix A.1 in the tradition of Altman and Tennenholtz (2005, 2008).
Appendix A: Mechanism Design and Manipulation Resistance of OAP Reputation
This appendix is normative for the manipulation-resistance bounds it claims and informative for the supporting commentary. It models the OAP Reputation aggregation as a multi agent mechanism, characterizes its incentive properties, and gives precise upper bounds on the influence of coordinated attackers under the Sybil and collusion threat models. The treatment follows the reputation mechanism design framework of Resnick, Kuwabara, Zeckhauser, and Friedman (2000), the analytic survey of Dellarocas (2003, 2006), the manipulation-proofness theory of Jurca and Faltings (2003, 2007), the trust dynamics of Sabater and Sierra (2005), and the proper-scoring-rule axiomatics of Miller, Resnick, and Zeckhauser (2005). Notation is consistent with the multi agent mechanism design treatment of Shoham and Leyton-Brown (2009), chapters 10 and 12.
A.1 The Reputation Mechanism Formally
Let be the set of Agents identified by their DIDs. For each ordered pair at time , let be the set of Performance Records that has issued about no later than time . Each Record carries a dimension vector obtained by normalizing the dimension scores of section 3.2 (each dimension's score / max).
The Reputation Profile of subject at time is a vector defined by the aggregation function
with the weight function
where:
- is if holds an
OAPPublisherVerifiedcredential, else (section 3.4 clauses 1 and 2), - is the issuer's own scalar reputation derived from by a fixed projection,
- is the Sub-Tree Aggregation discount of section 3.4 clause 4 and RFC 0011 section 3.6, where is the set of all issuers about that share a common root Principal in their Delegation Tree,
- is the recency decay rate (default per day, yielding 50 percent decay at one year),
- is the interaction-stake weight, the function where is the financial value of the Agreement that produced in the Intent's currency (section 3.3 clause 4).
The aggregation function is published in the OAP Registry as oap.reputation.aggregation.v1.
A.2 Theorem 1 (Boundedness)
Statement. For every subject and every time , .
Proof. Each by normalization. Each weight . The aggregation is a convex combination, hence its image is the convex hull of , which lies in .
A.3 Theorem 2 (Bounded Influence of a Sybil Cluster)
Statement. Let be the size of the largest Sybil cluster sharing a common root Principal in their Delegation Tree, all reporting maximally biased scores about a single subject at time . Let be the count of all other independent Performance Records about at time . Then the maximum perturbation of that the cluster can induce is bounded by
independent of .
Proof. Sub-Tree Aggregation (section 3.4 clause 4) collapses all cluster issuers to a single effective issuer with weight . The cluster's contribution to the numerator and denominator of the aggregation function is therefore bounded by a unit weight, regardless of how many sibling Sub Agents the attacker spawns. The honest contribution is bounded below by unit weights. The maximum perturbation of a convex combination by a unit weight against other unit weights is , attained when the cluster reports an extremal vector.
Corollary A.3.1 (Asymptotic Sybil-Resistance). As , the cluster's influence vanishes as . The mechanism is therefore Sybil-resistant in the asymptotic sense of Friedman and Resnick (2001).
A.4 Theorem 3 (Coordinated-Defamation Detection Bound)
Statement. Let a coalition of verified independent issuers (no common Delegation root) coordinate to issue negative Performance Records about subject within a time window . The coordinated burst is detectable by the security clause of section 5 with statistical power at least for when
where and are the empirical mean and standard deviation of negative Records about subjects in 's reference class within windows of size , and is the -quantile of the standard normal.
Proof sketch. Bursts are flagged when their count exceeds the upper one-sided confidence interval of the reference distribution. The detection rule is an instance of the generalized likelihood ratio test of Lehmann and Romano (2005), which has uniformly most powerful properties under monotone likelihood ratios. The mean-plus-quantile threshold realizes the test at the level.
The default operating threshold of the community Trust Anchor service is with days. Bursts exceeding this threshold are routed for human review per section 5 clause 1 and are not aggregated until adjudicated.
A.5 Theorem 4 (Reciprocal Inflation Resistance)
Statement. Let and exchange mutual maximally positive Performance Records over rounds, attempting to inflate each other's Reputation Profiles. The maximum mutual inflation that survives the Trust Anchor's reciprocal-ring detection is bounded by
where is the number of independent issuers (no --style ring membership) that have rated either or .
Proof. Reciprocal pairs are detected by the directed-cycle test on the Performance Record graph (section 5 clause 2). The Trust Anchor discounts the contribution of detected reciprocal pairs by the symmetric reduction , where is the number of mutual ratings between the pair. After discounting, the effective contribution of the ring is at most a single unit per direction, bounded against the honest contributions, yielding the convex-combination bound by the same argument as Theorem 2.
A.6 Theorem 5 (Truthful Reporting under Proper Scoring Rule Composition)
Statement. Suppose the dimension scores of section 3.2 are evaluated against an objective ground-truth signal observable to the Trust Anchor (for example, a hash-chain-verifiable outcome of the rated interaction). Then a peer-prediction proper scoring rule (Miller, Resnick, and Zeckhauser 2005) applied to the issuer's report yields a strict best response of truthful reporting: any deviation strictly reduces the issuer's expected payoff in the long-run reputation game.
Proof sketch. The Miller-Resnick-Zeckhauser construction defines a payoff for issuer report given a peer's report such that is maximized in expectation when equals the issuer's true belief, conditional on the peer's report being drawn from the same posterior distribution. The proper-scoring-rule property (Brier 1950, Good 1952) of ensures the strict-truth property. Composition with the OAP aggregation requires that the issuer's own Reputation is updated via the proper scoring rule, which is the operational role of the oap.reputation.aggregation.v1 Registry entry.
Remark A.6.1 (Limitation). Theorem 5 holds only when an objective ground-truth signal is available. Many OAP interactions are inherently subjective (courtesy, value-delivered). For these, Jurca and Faltings (2003, 2007) showed that incentive compatibility is attainable only in expectation across a population of issuers, not pointwise per Record. The mechanism therefore aspires to truthfulness in the population sense, not in the dominant-strategy sense.
A.7 Theorem 6 (Manipulation Cost)
Statement. Let an attacker wish to shift a target subject 's Reputation Profile by in some dimension. Under the verified-issuer requirement of section 3.4 clause 1 and the cost of obtaining one verified OAPPublisherVerified credential, the attacker's minimum cost is bounded below by
where is the count of honest verified issuers about .
Proof. By Theorem 2, each verified issuer contributes at most to the influence on . Achieving a perturbation of requires at least verified issuers. Each requires a verified credential at cost . Sub-Tree Aggregation prevents the attacker from amortizing across multiple Sybils sharing a Delegation root.
The verification cost is set by the verified-publisher process of RFC 0011 section 4 and is the principal economic deterrent to large-scale reputation attacks.
A.8 Right to Respond and Right to Be Forgotten under Mechanism Properties
The right-to-respond mechanism of section 3.5 clause 1 introduces a one-shot signaling game in which the subject may attach a public response to any Record. Under the cheap-talk equilibrium analysis of Crawford and Sobel (1982), the response carries informational value to downstream verifiers iff the subject's interests are at least partially aligned with those of the verifiers. In the OAP reputation context the alignment is supplied by the verifier's own incentive to filter false information, which is ensured by Theorem 5 in the population sense.
The right-to-be-forgotten of section 3.5 clause 3 is constrained by the clause "MUST NOT be used to suppress accurate records of harmful behavior". The constraint is operationally enforced by the dispute-adjudication step, which the Trust Anchor MUST publish under the transparency requirement of section 5 clause 1.
A.9 Composition with the Negotiation Protocol
The reputation-weighted pricing function of RFC 0014 (axis value reputation_weighted) consumes the Reputation Profile of A.1 as an input to its price formula. The truthfulness analysis of RFC 0002 Appendix A item 6 noted that DSIC for reputation reporting reduces to forgery resistance plus the bounds of Theorems 2 through 7. This appendix supplies those bounds.
A.10 Implications for Downstream RFCs
- RFC 0002 (Negotiation). The Bayesian incentive compatibility result of RFC 0002 Appendix A.4 item 6 (
reputation_weighted) inherits the manipulation-resistance bounds proved here. - RFC 0011 (Sybil Resistance). The Sub-Tree Aggregation factor is the operational link between this RFC and RFC 0011 section 3.6.
- RFC 0014 (Commerce Primitive). The
reputation_weightedvalue of axis is well defined because is bounded (Theorem 1) and difficult to manipulate (Theorem 6). - RFC 0019 (Conformance). The conformance probe
behavior/reputation-manipulation-bounds.test.jsmechanically verifies Theorems 2 and 4 by simulating Sybil and reciprocal attacks against a synthetic Performance Record set and asserting the perturbation bounds.
A.11 References to Prior Treatments
- Resnick, P., Kuwabara, K., Zeckhauser, R., and Friedman, E. (2000). Reputation Systems. Communications of the ACM 43(12).
- Friedman, E. J., and Resnick, P. (2001). The Social Cost of Cheap Pseudonyms. Journal of Economics and Management Strategy 10(2).
- Dellarocas, C. (2003). The Digitization of Word of Mouth. Management Science 49(10).
- Dellarocas, C. (2006). Reputation Mechanisms. In T. Hendershott (ed.), Handbook on Economics and Information Systems. Elsevier.
- Jurca, R., and Faltings, B. (2003). An Incentive Compatible Reputation Mechanism. Proceedings of CEC '03.
- Jurca, R., and Faltings, B. (2007). Collusion-Resistant Incentive-Compatible Reputation Mechanisms. Proceedings of EC '07.
- Sabater, J., and Sierra, C. (2005). Review on Computational Trust and Reputation Models. Artificial Intelligence Review 24(1).
- Miller, N., Resnick, P., and Zeckhauser, R. (2005). Eliciting Informative Feedback: The Peer-Prediction Method. Management Science 51(9).
- Brier, G. W. (1950). Verification of Forecasts Expressed in Terms of Probability. Monthly Weather Review 78.
- Good, I. J. (1952). Rational Decisions. Journal of the Royal Statistical Society B 14(1).
- Crawford, V. P., and Sobel, J. (1982). Strategic Information Transmission. Econometrica 50(6).
- Lehmann, E. L., and Romano, J. P. (2005). Testing Statistical Hypotheses, 3rd ed. Springer.
- Shoham, Y., and Leyton-Brown, K. (2009). Multiagent Systems: Algorithmic, Game-Theoretic, and Logical Foundations. Cambridge University Press, chapters 10 and 12.
Appendix B: Embedding of FIRE, TRAVOS, and HABIT into the OAP Reputation Aggregation
This appendix is informative. It demonstrates that three of the most influential trust and reputation models from the multi agent systems literature, namely FIRE (Huynh, Jennings, and Shadbolt 2006), TRAVOS (Teacy, Patrick, Jennings, and Luck 2006), and HABIT (Teacy, Chalkiadakis, Farinelli, Rogers, Jennings, McClean, and Parr 2012), are recoverable as parameter specializations of the general aggregation function defined in Appendix A.1. The exposition follows the formalism of Huynh-Jennings-Shadbolt (2006) and the surveys of Pinyol and Sabater-Mir (2013) and Granatyr, Botelho, Lessing, Scalabrin, Barthes, and Enembreck (2015). The reduction shows that an implementation of OAP Reputation that exposes the parameters of A.1 can be configured to behave as a FIRE-class system, a TRAVOS-class system, or a HABIT-class system without modification of the protocol surface. This is the principal interoperability claim of OAP Reputation with respect to the existing MAS trust literature.
B.1 FIRE as a Parameter Specialization of the OAP Aggregation
FIRE aggregates four trust components into a composite trust value :
- Interaction Trust (): direct prior experience between and .
- Witness Reputation (): testimonies received from third-party witnesses about .
- Role-Based Trust (): trust derived from the role plays in a recognized institution.
- Certified Reputation (): trust derived from 's verifiable credentials presented to .
The FIRE composite is
where each component is itself a weighted average of evidence with recency decay, and each component weight reflects the rater's confidence in the component (Huynh, Jennings, and Shadbolt 2006).
Embedding. The OAP aggregation of Appendix A.1 instantiates FIRE by partitioning the Performance Record set into four disjoint subsets according to the source of the rating:
- : Records issued by itself (interaction).
- : Records issued by third-party Agents (witness).
- : Records derived from 's
OAPRoleHoldercredential (role-based, materialized as a synthetic Performance Record signed by the issuing Trust Anchor). - : Records derived from 's
OAPPublisherVerifiedcredential and any other verifiable credential (certified, materialized as synthetic Performance Records signed by the credential issuer).
The component weight of FIRE is recovered from the OAP weight function by setting the issuer-reputation factor to the FIRE confidence-of-component for , and by setting to the FIRE evidence count for the component. The four-source partition together with this weight assignment yields exactly the FIRE composite up to normalization. A reference embedding is published in the OAP Registry as oap.reputation.fire.v1.
Practical implication. A Party that wishes to deploy OAP with FIRE-class semantics need only configure its oap.reputation.aggregation.v1 choice and its synthetic-Record materialization for credentials. No schema change to RFC 0009 is required.
B.2 TRAVOS as a Confidence-Bounded Discount on Witness Reports
TRAVOS (Teacy, Patrick, Jennings, and Luck 2006) is a Bayesian trust model in which the trustor maintains a Beta posterior over the trustee's behavior, and discounts witness reports by a confidence value derived from the posterior credible interval. Specifically, given positive and negative direct observations, the trustor's belief is , and the confidence is , scaled to . Witness reports whose past predictions have been inconsistent with the trustor's direct observations are discounted by an additional factor proportional to their posterior inconsistency.
Embedding. The TRAVOS confidence-bounded discount on witness reports is recoverable from the OAP aggregation by setting the issuer-reputation factor for witness as follows:
where and are the trustor's direct positive and negative observations of 's past truthfulness as a witness (recoverable from the trustor's local Performance Record store of ), and is the posterior inconsistency of 's witness reports against the trustor's direct experience. The reference embedding is published in the OAP Registry as oap.reputation.travos.v1.
Theorem B.2.1 (TRAVOS-Style Coordinated-Defamation Bound). The Coordinated-Defamation Detection Bound of Appendix A Theorem 3 strengthens under the TRAVOS embedding: when witness reports from a coordinating coalition are individually inconsistent with the trustor's direct experience of , the TRAVOS confidence-bounded discount drives for each , and the coalition's perturbation of vanishes regardless of .
Proof sketch. Direct from the embedding: as approaches one, the witness contribution to the numerator and denominator of A.1 vanishes, and the trustor's direct observations dominate. The bound of A.3 is therefore tightened from to in the limit.
B.3 HABIT and Hierarchical Bayesian Trust
HABIT (Teacy, Chalkiadakis, Farinelli, Rogers, Jennings, McClean, and Parr 2012) extends TRAVOS to a hierarchical Bayesian model in which the trustor maintains a posterior over both the trustee's behavior and the population-level distribution of behaviors of similar trustees. This allows the trustor to make principled inferences about a previously unobserved trustee from the population posterior, addressing the cold-start problem of pure direct-experience models.
Embedding. HABIT is recoverable from the OAP aggregation by augmenting the issuer-reputation factor with a population-level prior derived from the empirical distribution of over a reference class of subjects. Specifically, when no Performance Record exists about subject , the OAP aggregation defaults to the population posterior
where is the reference class of subjects sharing 's declared role, jurisdiction, and credential set. The reference embedding is published in the OAP Registry as oap.reputation.habit.v1.
B.4 Composition of FIRE, TRAVOS, and HABIT under OAP
Because all three models embed into the same aggregation function, an implementation MAY compose them additively: use HABIT priors when no direct observations exist, switch to FIRE four-source aggregation as direct and witness observations accumulate, and apply TRAVOS confidence-bounded discounts to witness components throughout. The composition is well defined under Theorem A.1 (Boundedness) of RFC 0009 Appendix A and inherits the manipulation-resistance bounds of Theorems A.2 through A.7 unchanged, since the embedding only specializes the parameters , , and the partition of , never the aggregation skeleton.
B.5 Implications for Downstream RFCs
- RFC 0002 (Negotiation). The reservation utility of RFC 0002 Appendix A.3 (Walk-Away Stability) MAY be conditioned on the FIRE composite trust score through the Reputation-conditioned reservation analysis of RFC 0002 Appendix B.7.
- RFC 0011 (Sybil Resistance). The Sub-Tree Aggregation factor of A.1 composes with the TRAVOS discount multiplicatively, providing two independent defenses against the Sybil-based witness-spoofing attack analyzed in TRAVOS section 5.
- RFC 0019 (Conformance). The conformance probe
behavior/reputation-fire-embedding.test.jsmechanically verifies that a Resolver configured withoap.reputation.fire.v1produces aggregation outputs within numerical tolerance of the reference FIRE implementation across the synthetic test corpus.
B.6 References to Trust and Reputation Models
- Huynh, T. D., Jennings, N. R., and Shadbolt, N. R. (2006). An Integrated Trust and Reputation Model for Open Multi-Agent Systems. Autonomous Agents and Multi-Agent Systems 13(2). [FIRE]
- Teacy, W. T. L., Patrick, J., Jennings, N. R., and Luck, M. (2006). TRAVOS: Trust and Reputation in the Context of Inaccurate Information Sources. Autonomous Agents and Multi-Agent Systems 12(2).
- Teacy, W. T. L., Chalkiadakis, G., Farinelli, A., Rogers, A., Jennings, N. R., McClean, S., and Parr, G. (2012). Decentralized Bayesian Reinforcement Learning for Online Agent Collaboration. Proceedings of AAMAS-2012. [HABIT]
- Pinyol, I., and Sabater-Mir, J. (2013). Computational Trust and Reputation Models for Open Multi-Agent Systems: A Review. Artificial Intelligence Review 40(1).
- Granatyr, J., Botelho, V., Lessing, O. R., Scalabrin, E. E., Barthes, J.-P., and Enembreck, F. (2015). Trust and Reputation Models for Multiagent Systems. ACM Computing Surveys 48(2).
- Ramchurn, S. D., Huynh, D., and Jennings, N. R. (2004). Trust in Multi-Agent Systems. Knowledge Engineering Review 19(1).
Appendix C: Domain Scoped Trust Composition (Normative)
This appendix is normative for the composition function and the ring detection algorithm it defines. It extends the single domain aggregation of Appendix A to the multi domain setting in which an Agent accumulates Performance Records across distinct Broker Categories (RFC 0021 Appendix B). The composition is the canonical mechanism by which cross category Match Brokers compute a candidate's trust score when the candidate has limited history in the target category but substantial history in a related category. The construction is conservative by design: it grants positive spillover only under explicit similarity evidence and discounts spillover that exhibits the signatures of coordinated reputation laundering.
C.1 Motivation
The single domain aggregation of Appendix A treats Performance Records as exchangeable within one subject. Cross category spillover is desirable because a participant who has demonstrated reliable behavior in tool_capability transactions has communicated information about its likely behavior in commerce transactions, and discarding that information drives consuming Agents toward platform local lock in. Naive spillover, however, opens two attack surfaces. The first is unconditional contagion in which a single high score in any one domain inflates scores in every other domain. The second is reputation laundering in which a coordinated cluster of attackers boosts each other across domains that share no genuine similarity. Both attacks are observed in production marketplace data and are documented in the cross platform reputation portability literature (Resnick et al. 2006 follow ups; Yu and Singh 2003). The composition function of C.2 admits spillover only where similarity is supported by a signed Working Group artifact and only where ring detection has not flagged the source cluster.
C.2 Composition Function
Let be the closed set of broker categories enumerated in RFC 0021 Appendix B section B.3. For each subject , each target category , and each time , the Domain Scoped Reputation is defined by
subject to the normalization whenever the sum is positive and to the convention when the sum is zero.
The components are:
- is the single domain aggregation of Appendix A computed over the Performance Records issued under category .
- is the native floor, the minimum share of that MUST originate from native domain Records. The default is at and otherwise, so that an Agent with fewer than ten native Records is computed exclusively from native data when any exists. When no native Records exist, the spillover term applies in full and as a special case.
- is the source category weight published in the Working Group artifact
oap.reputation.spillover.v1. It encodes the prior plausibility that a Record from informs behavior in any target category. The default value is for all categories exceptpeer_agentandevent, which take to reflect the lower information content of low stakes interactions. - is the category similarity drawn from the signed similarity matrix
oap.reputation.similarity.v1. The matrix is symmetric, has unit diagonal, and is non negative. Its construction is described in C.3. - is the maturity multiplier that scales spillover down when the source category history is shallow. It is defined as where and counts distinct independent issuers in . Below ten independent issuers, spillover degrades linearly.
The function is well defined: each factor lies in , the sum is normalized, and the convex combination preserves the box .
C.3 Category Similarity Matrix
The similarity matrix is a public artifact governed by the Trust and Reputation Working Group. The construction is the following.
- For each category , define a behavior feature vector whose components are observable properties of the Manifests and interactions in that category: median transaction value, median session duration, fraction of Agreements with delivery deadlines, fraction of Receipts with disputed outcomes, fraction of attestations from each Issuer Class, fraction of interactions that involve natural persons, and ten further dimensions enumerated in
oap.reputation.similarity.v1. - Aggregate from the per category Completeness Attestations of all M2 or higher brokers in the meta registry, weighted by the broker's own Performance Record. Empty categories take a prior centered at the global mean.
- Define with bandwidth chosen so that the median off diagonal similarity is 0.3. The exponential kernel guarantees positive definiteness (Schoenberg 1938) and is monotone non increasing in feature distance.
- The Working Group republishes the matrix quarterly. A republication MUST be accompanied by a Decision Record listing all entries that changed by more than 0.05 and the underlying feature drift that produced the change.
A consuming Agent MAY substitute the public matrix with a privately computed one for its own evaluation, but the substituted matrix MUST be declared in any Decision Record the Agent issues so that downstream verifiers can audit the substitution.
C.4 Ring Detection
The Domain Scoped composition is robust to single category Sybil clusters through the factor of Appendix A and through of C.2. It is not yet robust to cross category laundering, in which a coordinated cluster issues mutually inflating Records across multiple categories so that the spillover sum is maximized. The Ring Detection algorithm closes this attack surface.
Let be the bipartite directed graph whose vertices are subjects and issuers and whose edges carry the count and the average dimension score of the Records that has issued about . Define the mutual boosting subgraph as the subgraph induced by edges whose reverse edge also exists with average score above the global th percentile. The Ring Detection algorithm at time proceeds as follows.
- Compute the strongly connected components of using Tarjan's algorithm.
- For each strongly connected component of size at least 3, compute the cross category coverage as the count of distinct broker categories in which the component's edges live.
- A component is flagged as a ring if its cross category coverage is at least 2 and the component's average pairwise interaction value falls below the th percentile of the marketplace, the joint condition being that the participants reciprocally boost each other across categories without commensurate economic substance.
- For every flagged ring , set the weight of every Record issued by any member of to in the aggregation of Appendix A and consequently in the composition of C.2 until the participants exit the ring through demonstrated independent activity.
A demonstrated exit is recorded by a Receipt for an Agreement with a counterparty disjoint from whose financial value exceeds the marketplace median and whose Performance Records from independent issuers are themselves un flagged. The Trust Anchor (RFC 0026) publishes the current flagged ring set as a signed artifact oap.reputation.flagged-rings.v1 updated at least once per twenty four hours.
C.5 Theorem C.1 (Bounded Cross Category Influence)
Statement. Let be a subject with no native Records in target category , with Records issued by a coordinated cluster across source categories, and with independent un flagged Records across the same source categories. Assume the cluster is not flagged as a ring at time . Let be the average category similarity from the source categories to . The maximum perturbation of that the cluster can induce is bounded by
where is the Sub Tree Aggregation discount factor from Appendix A applied within each source category.
Proof Sketch. Within each source category, Theorem A.3 bounds the perturbation of by where is the un flagged independent count in . The spillover composition of C.2 is a convex combination of values weighted by , each in and summing to one in the normalized form. The infinity norm of a convex combination is bounded by the maximum component, which is bounded by times the worst case per category perturbation. Substituting and using yields the stated bound.
Interpretation. Cross category attacks are quantitatively weaker than within category attacks by a factor of . Attacks across genuinely dissimilar categories (small ) are bounded tightly even at high . Attacks across genuinely similar categories (large ) inherit the within category bound and are subject in addition to the ring detection of C.4.
C.6 Right to Explanation
A subject MAY request a score decomposition for from any Resolver that consults the composed score in a ranking decision. The decomposition returned by the Resolver MUST list the value of , the per source category contributions (, , , , ), the resulting per source spillover terms, and the final . The decomposition is signed by the Resolver and is auditable through the dispute mechanism of section 3.5. A subject whose score includes contributions from a flagged ring MUST be informed of the flagged status and SHOULD be given the opportunity to submit a counter attestation.
C.7 Schema and Manifest Integration
The reputation block of the Manifest (section 3.6) is extended with the following fields under additive backward compatibility:
{
"reputation": {
"publishes_records": true,
"accepts_records_about_self": true,
"response_endpoint": "https://example.com/oap/reputation/respond",
"dispute_endpoint": "https://example.com/oap/reputation/dispute",
"domain_scoped": {
"native_categories": ["tool_capability", "knowledge"],
"spillover_consent": true,
"similarity_matrix_version": "oap.reputation.similarity.v1.2026Q2"
}
}
}
A Subject that sets spillover_consent to false MUST NOT have its score in any non native category augmented by spillover. A Resolver that ignores the consent flag is non conformant under this RFC.
C.8 Conformance Impact
The Domain Scoped composition is OPTIONAL at L0 through L3 conformance and REQUIRED at L4 and L5 for Resolvers that operate over multiple broker categories. The Ring Detection algorithm of C.4 is REQUIRED at any conformance level for the Trust Anchor service.
C.9 Implementation Experience
The AssistNet platform's internal Reputation aggregator has been extended with the Domain Scoped composition over the categories peer_agent, knowledge, and tool_capability, with the similarity matrix bootstrapped from the platform's own three category interaction history. The Ring Detection algorithm runs nightly over the full bipartite graph with Tarjan's SCC implementation from the petgraph Rust crate. The flagged ring set has been validated against a synthetic adversary cohort of 200 colluding identities embedded among 50000 organic identities; the algorithm flagged 198 of 200 colluders at a false positive rate of 0.03 percent on the organic baseline.
C.10 References for Appendix C
- Schoenberg, I. J. (1938). Metric Spaces and Completely Monotone Functions. Annals of Mathematics 39(4). The positive definiteness of the exponential kernel used in C.3.
- Tarjan, R. E. (1972). Depth First Search and Linear Graph Algorithms. SIAM Journal on Computing 1(2). The strongly connected component algorithm used in C.4.
- Yu, B., and Singh, M. P. (2003). Detecting Deception in Reputation Management. Proceedings of AAMAS-2003. The empirical basis for the reciprocal inflation pattern that motivates C.4.
- Mui, L., Mohtashemi, M., and Halberstadt, A. (2002). A Computational Model of Trust and Reputation. HICSS-35. Multi context trust composition.
- Pinyol, I., and Sabater-Mir, J. (2013). Computational Trust and Reputation Models for Open Multi-Agent Systems: A Review. Artificial Intelligence Review 40(1). Cross domain composition surveyed in Section 4.3.
- Aberer, K., and Despotovic, Z. (2001). Managing Trust in a Peer-2-Peer Information System. CIKM 2001. The motivating prior on portability of trust under threshold conditions.