Gov/en/Portal:Terms/Contract-Governance

💡 In simple words: In simple words: this page explains the rules for how agreements (contracts) between people on WikiDeal are made, checked, and kept fair.

⚠️ Not yet approved. This page describes a proposal that is still under community review. It is documented here so it can be discussed, improved and endorsed.

Contract Governance — Ideas, Sandboxes & Endorsed Models

From WikiDeal, the Wikipedia of e-commerce · Socio-Technical Innovation by Théo Bondolfi

WikiDeal reimagines contract culture. Rather than rigid, lawyer-drafted-only documents, it creates a layered governance architecture: open participatory sandboxes for ideas and debate, and frozen endorsed models validated by legal professionals. The key is the porosity between both spaces — community creativity feeds into professional validation, and validated models inspire further community refinement.

Contents

1 The Two Spaces

WikiDeal's contract governance is built on a fundamental distinction between two complementary spaces: an open, participatory sandbox where anyone can contribute, and a curated set of endorsed models that carry legal validation.

1.1 The Open Sandbox (Ideas & Debate)

Anyone can contribute. This is a fully open wiki space where the community shapes contract culture collectively:

• Users propose new clauses, adaptations, or contract options
• Discussion happens on the Talk/Discuss page of each clause
• Each clause proposal follows a structured format:
  • Content — the clause text itself
  • Motivation — why this clause matters
  • Stakes & Needs — who is affected and what they need
  • Mechanisms — how it works technically and legally
  • Statistics & Evidence — supporting data and references
  • User Feedback & Experience Reports — real-world accounts from community members

The sandbox is intentionally permeable. Ideas that gain community support and pass a legal review can be elevated into endorsed models. Conversely, endorsed models can be "reopened" into the sandbox for further evolution.

1.2 The Endorsed Contract Models (User Groups)

User Groups can launch an Open Call to package and validate a contract model. These endorsed models are fundamentally different from sandbox content:

• Fixed — not editable by the general public once endorsed
• Endorsed ✓ Endorsed — officially validated by a lawyer or legal professional
• Visible endorsement indicator — a badge or score showing the degree of legal validation
• Potentially multiple versions for the same use case — for example, "Babysitting Flexible" vs "Babysitting Standard", each calibrated to different trust levels

Endorsed models are living artifacts in a frozen state: the community can always propose improvements through the sandbox, which may feed a future revision cycle.

2 The Endorsement System

The key to WikiDeal's contract quality is the endorsement pipeline — a structured path from open community enrichment to legally validated models:

1. Open participatory enrichment phase → The sandbox is active. Community members propose, debate, and refine clauses. The Talk page is the engine room of collective intelligence.
2. Legal validation → A lawyer or jurist officially reviews and endorses the packaged model for a specific User Group. This step is voluntary but creates a clear trust signal.
3. Endorsement indicator → A visible badge or score appears on the contract model page, reflecting the degree of legal validation (e.g., "reviewed by a certified legal professional" vs "community-validated only").
4. Optional non-validated clauses → Signatories can add extra clauses under their own responsibility, without legal endorsement. These are clearly marked as ⚠ Unvalidated so all parties are aware of their status.

This pipeline ensures that quality and openness coexist: the community generates ideas freely, while professional endorsement provides a trusted, usable foundation.

3 The Culture of Contracts

WikiDeal is not just building contract tools — it is rethinking contract culture itself. A few key principles guide this vision:

• Plurality over uniformity. Multiple models can coexist for the same use case. There is no single "correct" babysitting contract — different communities may have different norms, trust levels, and risk tolerances.
• A spectrum of rigidity. Some models are more flexible (fewer mandatory clauses, more room for personal adaptation), while others offer full legal coverage. Users choose the level that fits their community.
• Community trust as infrastructure. The right balance between flexibility and rigidity is not imposed from above — it emerges from each User Group's collective experience and negotiation.
• Transparency as default. Whether a clause is sandbox-sourced, lawyer-endorsed, or unvalidated custom content — this is always visible to all parties before signing.

This spectrum approach allows WikiDeal to serve both informal community exchanges (where a lightweight, flexible contract is appropriate) and high-stakes professional contexts (where full legal coverage is essential) — often within the same platform.

See also

• Contract Structures
• Open Call
• User Group Toolbox

Categories: · · ·