This draft articulates Desirable Property 18 (DP18) as the condition under which the meta-layer can learn from participation without collapsing into surveillance, popularity contests, social credit, or reputation systems that permanently trap people in old contexts.
DP18 defines how communities gather feedback, convert signals into accountable learning, and recognize trustworthy contribution over time. It treats feedback and reputation as civic infrastructure, not engagement metrics.
Feedback loops are how the meta-layer senses whether its governance, incentives, safety systems, interfaces, and community norms are working. Reputation is how the system remembers patterns of contribution, care, reliability, and harm without reducing people to a single score.
If DP18 is weak, predictable failures follow: communities ask for feedback but do not act on it; reputation becomes a vanity metric; harmful actors launder trust across contexts; contributors burn out because recognition is invisible; AI systems optimize for shallow approval signals; and governance adapts only after legitimacy breaks.
DP18 connects directly to:
DP18 does not prescribe a universal reputation score, a single feedback interface, or one model of rewards. It defines the minimum conditions under which feedback and reputation remain contextual, contestable, privacy-preserving, and aligned with community flourishing.
Today’s web is saturated with signals, but starved of trustworthy feedback.
Likes, shares, followers, ratings, badges, view counts, and engagement graphs appear to measure social value. In practice, they often measure visibility, habit formation, emotional provocation, automation, or the ability to game a platform’s ranking system.
This produces recurring failures:
DP18 reframes feedback and reputation as learning infrastructure. Feedback must produce visible adaptation. Reputation must be contextual memory, not global judgment.
A healthy meta-layer must be able to answer:
Without DP18, the meta-layer cannot mature. It can collect comments, votes, and metrics, but it cannot reliably learn.
Communities are asked for input, but feedback has no visible path into decisions or operations.
Example: A town hall gathers participant concerns, but the same interface defaults, moderation rules, and incentive structures remain unchanged without explanation.
Why this matters: Feedback without response erodes trust faster than silence because it simulates agency while preserving control.
Reputation collapses into follower counts, visibility, or applause.
Example: A participant becomes trusted because their posts receive high engagement, even though their contributions are often misleading or inflammatory.
Why this matters: Popularity is not reliability. DP18 requires multidimensional, context-bound reputation.
A signal increases visibility, visibility increases signal volume, and the system treats the resulting amplification as legitimacy.
Example: Early upvotes push a submission into prominence; prominence generates more upvotes; the system mistakes attention momentum for quality.
Why this matters: Feedback loops must be bounded. Otherwise reputation becomes a mechanism for self-reinforcing inequality or manipulation.
Actors transfer trust from one context into another where it has not been earned.
Example: A participant with high reputation in a gaming community receives influence in a medical advice zone without relevant credentials or history.
Why this matters: Reputation must preserve context, scope, and provenance. Portability without boundaries becomes a trust exploit.
Negative reputation becomes permanent, opaque, or disproportionate.
Example: A participant makes a mistake in one zone and is silently down-ranked everywhere without notice, appeal, or decay.
Why this matters: Accountability must support learning and repair. Systems that never forgive incentivize abandonment, evasion, and identity cycling.
Coordinated or highly resourced groups dominate feedback channels.
Example: A small faction floods surveys, flags, votes, or comments to steer governance toward its preferred outcome.
Why this matters: Feedback systems must distinguish broad legitimacy from coordinated pressure.
Feedback mechanisms reproduce structural exclusion.
Example: Town halls occur in one language and time zone, while reputation rewards favor participants already fluent in dominant cultural norms.
Why this matters: Adaptive governance requires feedback from those most affected, not only those most available or socially rewarded.
AI systems learn to maximize visible approval signals rather than community-defined value.
Example: An assistant generates emotionally pleasing but low-integrity responses because users reward confidence and fluency more than accuracy.
Why this matters: AI feedback loops must be evaluated against zone policy, truthfulness, safety, and long-term outcomes, not only immediate satisfaction.
Reputation systems collect excessive behavioral data to infer trustworthiness.
Example: A system tracks every interaction, dwell time, private message, and social association to generate reputation scores.
Why this matters: Trust cannot be built by violating data sovereignty. DP18 must operate under DP4 constraints.
Reputation grants access or authority, then authority produces more reputation, making roles difficult to contest.
Example: Early stewards accumulate status and retain control even as their contribution quality declines.
Why this matters: Reputation-linked roles require decay, review, rotation, and contestability.
Feedback and reputation signals move across systems but lose meaning.
Example: A five-star rating exports without information about rubric, rater identity class, zone norms, time horizon, or dispute status.
Why this matters: Interoperable reputation must preserve semantic context or visibly degrade.
Feedback loops and reputation in the meta-layer must enable communities to learn from lived experience, recognize trustworthy contribution, correct harmful behavior, and adapt governance over time while preserving agency, privacy, context, contestability, and the possibility of repair.
Reputation is not a universal score. It is contextual memory under governance.
Feedback is not engagement. It is a structured pathway from signal to learning to action.
Example: A community receives recurring feedback that a moderation rule is being applied unevenly. The system clusters the feedback, surfaces affected groups, opens a review process, publishes a decision receipt, updates the rule, and tracks whether the change improves outcomes over time.
What this feels like: Participants can see that their experience matters, not because every request is granted, but because every meaningful signal has a legitimate path into community learning.
Without this: The meta-layer repeats the failure of today’s platforms: it extracts signals from people while denying them visible influence over the system those signals shape.
DP18 requires a feedback and reputation layer that converts participant signals into governed learning.
This layer includes:
The layer must operate at the interface where participants act and are affected, while preserving the governance and privacy boundaries of each zone.
A feedback and reputation layer is not a database of social judgments. It is an accountable learning system.
Failure mode: social credit drift, where contextual feedback becomes generalized behavioral scoring.
Feedback must be represented as structured objects, not only comments or reactions.
A feedback object SHOULD include:
This allows feedback to be routed, aggregated, audited, and acted upon without flattening all signals into likes or complaints.
Failure mode: signal mush, where all feedback becomes undifferentiated noise.
Feedback systems must define what happens after feedback is submitted.
For each class of feedback, systems SHOULD specify:
Participants do not need to control every outcome, but they must be able to see whether feedback entered a legitimate process.
Failure mode: black-hole feedback, where reports, suggestions, and concerns vanish without trace.
DP18 requires ongoing feedback channels, not one-time consultation.
Mechanisms MAY include:
Continuous feedback must be designed for accessibility across language, time zone, ability, bandwidth, and technical literacy.
Failure mode: episodic listening, where communities are consulted only during crisis or launch moments.
AI and automation may support feedback systems by summarizing large volumes of input, detecting patterns, identifying anomalies, and surfacing underrepresented concerns.
However, adaptive systems MUST remain bounded by:
AI may help communities see patterns. It must not quietly decide whose experience counts.
Failure mode: automation capture, where AI summaries become de facto governance decisions.
Reputation must be scoped to context, contribution type, and governance zone.
A reputation object SHOULD include:
This prevents reputation from becoming a single global score while still allowing communities to remember meaningful patterns.
Failure mode: global reputation collapse, where one number pretends to summarize a person, agent, or organization across all contexts.
Reputation may inform compensation, rewards, access, visibility, and recognition, but only under explicit governance.
Reputation-linked compensation SHOULD satisfy the following conditions:
Positive contribution should be rewarded without creating a system where people perform for metrics rather than serve the community.
Failure mode: reputation farming, where actors optimize for visible reward signals rather than actual value.
Roles and capabilities may adjust based on reputation, contribution history, and trust signals.
Examples include:
Role changes MUST be:
Reputation may open doors, but it must not create unaccountable hierarchy.
Failure mode: role capture, where reputation-linked access becomes permanent power.
Reputation must change over time.
Systems SHOULD support:
The goal is neither amnesia nor permanent stigma. The goal is governed memory.
Failure mode: frozen reputation, where old signals dominate present reality.
Participants and communities must be able to report harm, abuse, manipulation, and bad behavior through structured channels.
Reporting systems SHOULD support:
Reports are feedback objects with safety consequences. They must be treated with care, not merged into generic sentiment metrics.
Failure mode: weaponized reporting, where reporting tools become harassment or governance capture instruments.
DP18 requires mechanisms to recognize good behavior, not only punish bad behavior.
Positive signals MAY include:
Systems SHOULD make quiet, prosocial labor visible without forcing all care work into performance.
Failure mode: negative-only memory, where systems remember harm but fail to recognize repair, support, and stewardship.
Reputation must be plural.
A participant may be highly trusted for one function and untrusted for another. A contributor may be excellent at technical review but poor at facilitation. An AI agent may be strong at summarization but not authorized for dispute mediation.
Reputation dimensions MAY include:
Failure mode: single-axis trust, where one form of contribution grants unrelated authority.
Reputation should be portable where useful, but only with context preserved.
Portable reputation MUST carry:
When context cannot be preserved, systems MUST signal degradation.
Failure mode: semantic stripping, where reputation travels as a badge or score without the meaning needed to interpret it.
Communities SHOULD have dashboards that surface aggregate feedback and reputation patterns without exposing unnecessary personal data.
Dashboards MAY include:
Dashboards must be designed to support learning, not surveillance or public shaming.
Failure mode: dashboard theater, where metrics are displayed but do not affect decisions.
Feedback loops should support safe experimentation.
When communities test policies, interfaces, incentives, or reputation mechanisms, experiments SHOULD define:
This allows communities to try new mechanisms without making every experiment permanent.
Failure mode: irreversible experimentation, where communities bear the cost of failed changes without recourse.
Feedback submissions and system changes should generate receipts.
A feedback receipt MAY include:
An adaptation receipt MAY include:
Receipts close the loop between voice and action.
Failure mode: untraceable adaptation, where systems change without participants knowing why.
AI systems may participate in DP18 in multiple roles:
DP18 requires that AI feedback loops be especially constrained because automated systems can scale signals, interpret signals, and act on signals faster than communities can deliberate.
AI agents, models, tools, and automated services SHOULD have scoped reputation profiles when they act in ways that affect participants.
These profiles MAY track:
AI reputation must be tied to version, deployment context, and operator accountability.
Failure mode: agent amnesia, where an AI system causes repeated harm but each deployment is treated as isolated.
AI may summarize, cluster, translate, and analyze feedback, but must preserve dissent and uncertainty.
Systems SHOULD prevent AI from flattening minority concerns into majority sentiment.
A good synthesis identifies:
Failure mode: consensus hallucination, where AI creates the appearance of agreement where disagreement remains.
Feedback from participants can help communities refine containment policies for AI agents.
Examples include:
Containment feedback should trigger policy review, audit, rollback, rate limits, or suspension where appropriate.
Failure mode: containment lag, where AI behavior changes faster than feedback systems can respond.
Feedback and reputation systems must comply with data sovereignty.
DP18 systems SHOULD practice:
Reputation must not become a pretext for continuous behavioral surveillance.
Failure mode: trust through surveillance, where the system claims safety by collecting more data than communities can legitimately govern.
Feedback and reputation systems are governance systems. They must themselves be governable.
Communities SHOULD define:
This governance must be visible, versioned, and contestable.
Failure mode: hidden reputation law, where invisible formulas determine social standing and access.
A DP18-aligned implementation should be evaluated against the following questions.
Use separate reputation domains for different capabilities rather than one universal score.
Example domains:
Signals should include uncertainty. A verified expert correction, a peer endorsement, an anonymous concern, and a bot-like mass vote should not carry the same weight.
Feedback, moderation, role changes, rewards, and reputation updates should produce receipts that can be audited without exposing unnecessary private data.
Signals should age unless renewed by current evidence. Decay prevents permanent lock-in and reduces the power of old or stale interactions.
Reputation-linked roles should require periodic review or renewal, especially for stewards, moderators, grant reviewers, and high-impact AI operators.
Feedback from those directly affected by a policy or harm may require special visibility or routing, while still protecting against capture.
High-impact reputation changes should move from automated detection to human or community review before affecting access, compensation, or public standing.
Portable reputation should export as bundles containing claims, provenance, rubrics, expiry, dispute status, and interpretation limits.
Communities should periodically review whether feedback loops are actually improving governance, safety, inclusion, and contribution quality.
DP18 depends on accountable identity to prevent sybil abuse, retaliation, and reputation laundering. DP1 provides the identity substrate; DP18 governs the memory of behavior and contribution.
Participants must understand and contest reputation effects. Feedback systems must produce real agency, not symbolic participation.
DP18 supplies the learning loops that allow governance to adapt. DP3 defines how decisions change; DP18 defines how lived experience becomes actionable signal.
Feedback and reputation must operate under data minimization, purpose limitation, and consent. Reputation cannot justify surveillance.
Reputation and feedback must preserve meaning across systems or degrade visibly.
Reputation is zone-scoped by default. Communities define which signals matter, which roles reputation unlocks, and how repair works.
DP18 provides the recognition and evaluation substrate for fair incentives. DP9 governs how value flows from contribution.
AI agents need scoped reputations, feedback-triggered containment, and human-ratified adaptation.
Feedback loops and reputation logic must be legible enough for participants to understand how trust is being shaped.
Communities should be able to own and govern their feedback data, reputation schemas, and contribution histories.
A system claiming DP18 alignment SHOULD demonstrate:
DP18 is currently an ML-Draft and serves as exploratory scaffolding for how feedback loops and reputation can function as accountable learning infrastructure in the meta-layer.
Advancement toward ML-RFC status SHOULD require:
ML-RFC promotion SHOULD be contingent on:
Early ML-RFC candidates may focus on:
DP18 is expected to evolve iteratively, with partial RFCs emerging for specific components rather than a single monolithic specification.
DP18 makes the meta-layer capable of learning.
It ensures that feedback is not extracted and ignored, that reputation is not reduced to popularity, and that communities can recognize contribution without building permanent social cages.
A DP18-aligned meta-layer remembers enough to be accountable, forgets enough to allow growth, and adapts visibly enough for participants to trust that their experience matters.
Feedback becomes civic signal.
Reputation becomes contextual memory.
Learning becomes shared infrastructure.
This is the difference between a system that listens and one that evolves.