WikiDeal - User contributions [en]

Policies/en/Steering-Committee-Charter

2026-07-09T16:30:37Z

Creativesoul4ever: clarified expert's profile

''This is a draft charter page, under construction. Status: proposal, to be adopted. It is offered as a first base position (initial hypothesis), proposed as a base for discussion, to be reviewed and validated before adoption. See the [[Policies/en/Disclaimer|detailed disclaimer]].''

= Steering Committee charter =

The '''Steering Committee''' is the founding governance body of WikiDeal. It is currently '''in the process of being constituted''': this is the very beginning of the project, and nothing is fixed at this stage. For the time being, this responsibility rests with the Council of the [https://ynternet.org Ynternet.org Foundation].

== Purpose ==

The Steering Committee is intended to guide the first steps of WikiDeal governance. Its members are invited to give their opinion and advice on the direction of the project. Over time, the Steering Committee is intended to hand over its responsibilities to the thematic committees ([[Policies/en/Technology-Committee-Charter|Technology]], [[Policies/en/Market-Committee-Charter|Market]], [[Policies/en/Governance-Committee-Charter|Governance]] and the other committees listed in the [[Policies/en/Main|policies index]]), as those committees come into existence.

== Appointment ==

The Steering Committee is appointed by the Council of the Ynternet.org Foundation.

== Composition ==

The Steering Committee is composed of:

* members of the Council of the Ynternet.org Foundation;
* members of the Scientific Council of the Ynternet.org Foundation;
* experts invited by Ynternet.org Council, recognized for their previous added value in equivalent projects on digital commons.

== An organic constitution process ==

The constitution of the Steering Committee is intended as an organic process:

* Members are invited to give their opinion and advice.
* They are invited only once enough Donations have been received for funds to be genuinely distributed.
* At the beginning there would be one, two or three people; progressively, more members would join.
* Progressively, the Steering Committee would pass the baton to the thematic boards (technology, market, policy and the others), as they come into existence.

== Current situation ==

The Steering Committee is currently being constituted. Because this is the very beginning of the project, nothing is settled yet. For now, this role is in the hands of the Council of the Ynternet.org Foundation:

* The members of the Council are registered in the Swiss commercial register.
* The Council meets periodically, according to the progress of the various projects of the Foundation. WikiDeal is the main project, but not the only one: other projects can be seen on the [https://ynternet.org Ynternet.org Foundation website].
* The operational director of the Foundation is '''Athanasios Priftis'''. See his TEDxGeneva talk: [https://www.youtube.com/watch?v=nrdu7NMcOOY "Ever tried to open a government?"] (TEDxGeneva 2014).

== Meetings and decisions ==

To be defined: frequency of meetings, quorum, how decisions are made and recorded.

== Review and amendment ==

To be defined: how this charter is reviewed, amended and approved.

== See also ==

* [[Policies/en/Main|All policies (index)]]
* [[Gov/en/Portal:Institutions/Steering-Committee|Steering Committee (Gov portal page)]]
* [[Market/en/Portal:Soft-Transmission/Main|Soft transmission]]

Policies/en/Main

2026-07-06T20:10:53Z

Creativesoul4ever: clariefied that these policies are proposed for Wikideal, which is a project "managed by" Ynternet.org

''This is a draft version. Source: adapted notably from the Wikimedia Foundation Governance Wiki, https://foundation.wikimedia.org/wiki/Policy:Main (CC BY-SA 4.0), with changes. Status: proposal, to be adopted. See the [[Policies/en/Disclaimer|detailed disclaimer]].''

__TOC__

= WikiDeal policies =

These are all the policies proposed for the WikiDeal platform managed by the [https://www.ynternet.org Ynternet.org Foundation]. Each policy has the status: proposal, to be adopted. They are working drafts, offered as a first base position (initial hypothesis): each policy must be reviewed and validated before adoption.

== About this page ==

This set of policies was adapted from the encyclopedic world: it is based on the official policies of the Wikimedia Foundation, which have governed large collaborative projects for two decades. Three things were changed in the adaptation:

# '''The managing organization:''' these policies refer to the [https://www.ynternet.org Ynternet.org Foundation], which hosts and incubates WikiDeal, instead of the original encyclopedic foundation.
# '''The scope:''' references to encyclopedic projects were adapted to the WikiDeal platform, a marketplace of fair contracts.
# '''The status:''' every policy here is a proposal, not yet validated. Proposals are made by the WikiDeal founder ([[Gov/en/Portal:Meta/Licensing-and-Credits|see credits]]) as initial hypotheses, then discussed and first validated by the founding steering committee (hosting and incubation phase), then transmitted to the community of WikiDealers through a [[Market/en/Portal:Soft-Transmission/Main|soft transmission]]. The community organizes itself progressively, choosing by itself the members of its Board of Trustees, its Steering Committee and its other bodies.

See also: [[Policies/en/Key-Questions|Key questions on strategy and deployment]] · [[Policies/en/Non-Migrated-Pages|Pages that were not migrated, and why]].

== WikiDeal platform ==

These policies or legal guidelines apply to the whole WikiDeal platform.

* [[Policies/en/Access-to-Nonpublic-Personal-Data|Access to nonpublic personal data policy]] (proposal, to be adopted)
** [[Policies/en/Access-to-Nonpublic-Personal-Data/Underage-Exemptions|Underage exemptions]] (proposal, to be adopted)
** [[Policies/en/Access-to-Nonpublic-Personal-Data/Exceptions|Exceptions]] (proposal, to be adopted)
** [[Policies/en/Confidentiality-Agreement-for-Nonpublic-Information|Confidentiality agreement for nonpublic information]] (proposal, to be adopted)
* [[Policies/en/Access-to-Temporary-Account-IP-Addresses|Access to temporary account IP addresses]] (under construction)
* [[Policies/en/AI-Terms-of-Use|AI Terms of Use]] (initial hypothesis, under review)
* [[Policies/en/API-Usage-Guidelines|API usage guidelines]] (proposal, to be adopted)
* [[Policies/en/Code-of-Conduct-for-Technical-Spaces|Code of conduct for WikiDeal technical spaces, including events]] (proposal, to be adopted)
* [[Policies/en/Combating-Online-Child-Exploitation|Combating online child exploitation]] (proposal, to be adopted)
* [[Policies/en/Commercial-Sales-and-Contracts|Commercial sales and contracts]] (proposal, to be adopted)
* [[Policies/en/Cookie-Statement|Cookie statement]] (proposal, to be adopted)
* [[Policies/en/Data-Collection-Guidelines|Data collection guidelines]] (proposal, to be adopted)
* [[Policies/en/Data-Publication-Guidelines|Data publication guidelines]] (proposal, to be adopted)
* [[Policies/en/Data-Retention-Guidelines|Data retention guidelines]] (proposal, to be adopted)
* [[Policies/en/Copyright-Takedown-Policy|Copyright takedown policy (Swiss law)]] (first draft, under review)
* [[Policies/en/Donor-Privacy-Policy|Donor privacy policy]] (proposal, to be adopted)
* [[Policies/en/General-Disclaimer|General disclaimer]] (proposal, to be adopted)
* [[Policies/en/Human-Rights-Policy|Human rights policy]] (proposal, to be adopted)
* [[Policies/en/Licensing-Policy|Licensing policy]] (proposal, to be adopted)
* [[Policies/en/Modifying-CheckUser-Logs|Modifying CheckUser logs guidelines]] (under construction)
* [[Policies/en/Office-Actions-Policy|Office actions policy]] (proposal, to be adopted)
** [[Policies/en/Office-Actions-Policy/Procedures|Procedures]] (proposal, to be adopted)
* [[Policies/en/Privacy-Policy|Privacy policy]] (first draft, under review)
** [[Policies/en/Non-Wiki-Privacy-Policy|Non-wiki privacy policy]] (proposal, to be adopted)
* [[Policies/en/Terms-of-Use|Terms of use]] (proposal, to be adopted)
* [[Policies/en/Terrorist-and-Violent-Extremist-Content|Terrorist and violent extremist content procedures and guidelines]] (proposal, to be adopted)
* Trademark policy (under construction)
* [[Policies/en/Universal-Code-of-Conduct|Universal code of conduct]] (proposal, to be adopted)
** [[Policies/en/Universal-Code-of-Conduct/Enforcement-Guidelines|Enforcement guidelines]] (proposal, to be adopted)
* [[Policies/en/Use-of-the-Platform-for-Advocacy|Use of the Platform for advocacy purposes]] (proposal, to be adopted)

== Board and staff policies ==

The internal Board and staff policies of the source organization (codes of conduct, conflict of interest, travel and expenses, gifts, whistleblower protection and similar) are not copied as such: they regulate the internal life of another organization. The governance bodies of WikiDeal, and the policies that would regulate them, are intended to emerge through the [[Market/en/Portal:Soft-Transmission/Main|soft transmission]] process and the future steering committee. This remains an open question: see [[Policies/en/Key-Questions|Key questions]] and the [[Policies/en/Non-Migrated-Pages|list of non-migrated pages]].

== Other ==

Other documents provide more information on how some Ynternet.org Foundation activities are conducted and are usually maintained by the staff who conduct those activities.

* Expense reimbursement guidelines (proposal, to be adopted)
* [[Policies/en/Feedback-Privacy-Statement|Feedback privacy statement]] (proposal, to be adopted)
* [[Policies/en/Friendly-Space-Policy|Friendly space policy]] (proposal, to be adopted)
* Investment policy (proposal, to be adopted)
* Legal policies (proposal, to be adopted)
* Open access policy (proposal, to be adopted)
* Peering policy (proposal, to be adopted)
* Purchasing and disbursement process (proposal, to be adopted)
* [[Policies/en/Requests-for-User-Information|Requests for user information procedures and guidelines]] (proposal, to be adopted)
* Scholarship travel policy (proposal, to be adopted)
* Service provider travel guidance (proposal, to be adopted)
* [[Policies/en/Visual-Identity-Guidelines|Visual identity guidelines]] (under construction)

=== Charters ===
* Audit Committee (proposal, to be adopted)
* Executive Committee (proposal, to be adopted)
* Governance Committee (proposal, to be adopted)
* Market Committee (proposal, to be adopted)
* Technology Committee (proposal, to be adopted)
* Talent & Culture Committee (proposal, to be adopted)
* Societal Impact Committee (proposal, to be adopted)
* Creativity Committee (proposal, to be adopted)

== See also ==

* [[Policies/en/Non-Migrated-Pages#legal-documentation|Legal documentation of the source wiki: review and migration status]]
* [[Policies/en/Resolutions|Resolutions]]
* [[Policies/en/Disclaimer|Detailed disclaimer]]
* [[Policies/en/Adaptation-Conventions|Adaptation conventions]]
* [[Gov/en/Portal:Voting/Main|Voting methods and rules (Gov)]]

[[Category:Migration June 2026]]

Gov/en/Portal:R&D/Innovations:User Groups

2026-06-29T08:57:49Z

Creativesoul4ever:

{{KidsIntro|User groups are teams of people who use the platform for the same reason. They join together to share ideas, help each other, and have a stronger voice when making decisions. They are required to have a legal structure, maintain detailed records on activities, maintain an expertise in their focal area, and share that expertise with the Wikideal movement.

They include transversal groups serving all users (such as arbitration or market incubators), national chapters (adapted to each country's legislation) and thematic groups of diverse sizes, mostly geographic (such as babysitting in Geneva or federation of transportation users in europe). }}

✏️ '''User view:''' You are viewing a community, marketplace, or contract page.

== User Groups ==

User Group Model

{| class="wikitable"
|-
| Revenue
| Commission share + Reward
|-
| Governance
| Local autonomy + global rules
|-
| Incubation
| Foundation support available
|-
| Examples
| Babysitting, Tutoring, Pet Care
|-
| Scale
| Local, regional, or thematic
|}

'''User Groups''' are WikiDeal's primary organisational units below the platform level. A User Group is a community of WikiDeal members organised around a specific service category (babysitting), geographic region (babysitting in Spanish-speaking countries), or combination of both. User Groups operate with significant autonomy — setting their own Commission rates within WikiDeal's boundaries, managing their own arbitration systems, and organising their own community events — while respecting the core WikiDeal principles embedded in the model.

=== Revenue Model ===

User Groups generate income through three channels. First, a share of the Commission on every Transaction within their category/region flows to the User Group's operational fund. Second, User Groups can launch their own [[Gov/en/Portal:R&D/Innovations:Bonding Curve|bonding curve]] funding rounds — using the same mechanism as WikiDeal Core but for their specific context. A babysitting User Group in East Africa might raise CHF 200,000 through its own curve, using the funds to localise contracts, train arbitrators, and build community Infrastructure. Third, User Groups can apply to WikiDeal's [[Gov/en/Portal:R&D/Open-Call:Main|Open Call]] fund for specific project grants.

This revenue model is designed to align incentives: User Groups that grow the volume and quality of Transactions in their category earn more, reinvesting in further growth. User Groups that operate arbitration services professionally attract more Transactions, because users trust the dispute resolution. The result is a federated system where local expertise is rewarded and central overhead is minimised.

=== Incubation and Support ===

New User Groups can apply for incubation support from Ynternet.org Foundation, which provides: legal template adaptation for local jurisdictions; technical setup assistance for the WikiDeal platform; access to the foundation's network of advisors and partner organisations; and a small seed grant from the Open Call fund. Incubation is time-limited (typically 12 months) and requires the User Group to demonstrate genuine community need, governance capacity, and alignment with WikiDeal values.

Co-incubation is also supported: two or more User Groups working in complementary domains (e.g. babysitting and tutoring in the same city) can co-incubate, sharing Infrastructure costs and community events while maintaining separate governance. This reduces the overhead of launching multiple groups in the same geography and creates natural bridges between service categories — a family using WikiDeal for babysitting may discover tutoring services, and vice versa.

=== Examples of Planned User Groups ===

WikiDeal's roadmap includes User Groups for: babysitting (global launch, multiple regional groups); private tutoring (language-based and subject-based groups); pet care (sitting, walking, veterinary facilitation); bicycle and tool lending cooperatives; local food markets and community-supported agriculture; freelance creative services; and language learning exchanges. Each of these domains has an established informal economy that is (illustrative example) either unplatformed (and therefore lacks trust Infrastructure) or over-platformed (and therefore paying excessive Commissions to extractive intermediaries).

'''See also:'''
[[Category:Migration June 2026]]

Gov/en/Portal:R&D/Innovations:User Groups

2026-06-25T17:05:07Z

Creativesoul4ever: clarified the diverse type of user groups

{{KidsIntro|User groups are teams of people who use the platform for the same reason. They join together to share ideas, help each other, and have a stronger voice when making decisions. They are required to have a legal structure, maintain detailed records on activities, maintain an expertise in their focal area, and share that expertise with the Wikimedia movement.

They include transversal groups serving all users (such as arbitration or market incubators), national chapters (adapted to each country's legislation) and thematic groups of diverse sizes, mostly geographic (such as babysitting in Geneva or federation of transportation users in europe). }}

✏️ '''User view:''' You are viewing a community, marketplace, or contract page.

== User Groups ==

User Group Model

{| class="wikitable"
|-
| Revenue
| Commission share + Reward
|-
| Governance
| Local autonomy + global rules
|-
| Incubation
| Foundation support available
|-
| Examples
| Babysitting, Tutoring, Pet Care
|-
| Scale
| Local, regional, or thematic
|}

'''User Groups''' are WikiDeal's primary organisational units below the platform level. A User Group is a community of WikiDeal members organised around a specific service category (babysitting), geographic region (babysitting in Spanish-speaking countries), or combination of both. User Groups operate with significant autonomy — setting their own Commission rates within WikiDeal's boundaries, managing their own arbitration systems, and organising their own community events — while respecting the core WikiDeal principles embedded in the model.

=== Revenue Model ===

User Groups generate income through three channels. First, a share of the Commission on every Transaction within their category/region flows to the User Group's operational fund. Second, User Groups can launch their own [[Gov/en/Portal:R&D/Innovations:Bonding Curve|bonding curve]] funding rounds — using the same mechanism as WikiDeal Core but for their specific context. A babysitting User Group in East Africa might raise CHF 200,000 through its own curve, using the funds to localise contracts, train arbitrators, and build community Infrastructure. Third, User Groups can apply to WikiDeal's [[Gov/en/Portal:R&D/Open-Call:Main|Open Call]] fund for specific project grants.

This revenue model is designed to align incentives: User Groups that grow the volume and quality of Transactions in their category earn more, reinvesting in further growth. User Groups that operate arbitration services professionally attract more Transactions, because users trust the dispute resolution. The result is a federated system where local expertise is rewarded and central overhead is minimised.

=== Incubation and Support ===

New User Groups can apply for incubation support from Ynternet.org Foundation, which provides: legal template adaptation for local jurisdictions; technical setup assistance for the WikiDeal platform; access to the foundation's network of advisors and partner organisations; and a small seed grant from the Open Call fund. Incubation is time-limited (typically 12 months) and requires the User Group to demonstrate genuine community need, governance capacity, and alignment with WikiDeal values.

Co-incubation is also supported: two or more User Groups working in complementary domains (e.g. babysitting and tutoring in the same city) can co-incubate, sharing Infrastructure costs and community events while maintaining separate governance. This reduces the overhead of launching multiple groups in the same geography and creates natural bridges between service categories — a family using WikiDeal for babysitting may discover tutoring services, and vice versa.

=== Examples of Planned User Groups ===

WikiDeal's roadmap includes User Groups for: babysitting (global launch, multiple regional groups); private tutoring (language-based and subject-based groups); pet care (sitting, walking, veterinary facilitation); bicycle and tool lending cooperatives; local food markets and community-supported agriculture; freelance creative services; and language learning exchanges. Each of these domains has an established informal economy that is (illustrative example) either unplatformed (and therefore lacks trust Infrastructure) or over-platformed (and therefore paying excessive Commissions to extractive intermediaries).

'''See also:'''
[[Category:Migration June 2026]]

Gov/en/Portal:R&D/Innovations:Structured Data

2026-06-25T16:43:57Z

Creativesoul4ever: added "of charge" in "free"

{{KidsIntro|"Structured data" means organising information so computers can read it and connect it, like putting a clear label on every box so the right machine can find what is inside. On WikiDeal, some data is private (your identity, your bank details, photos of a flat you want to rent out) and some data is public on purpose (the content of contracts people choose to publish, whether a contract was signed or completed, and overall usage statistics). One idea guides the whole effort: your habits and your commercial behaviour are not for sale. It is a bit like nobody being allowed to walk into your head or your home: what you buy, how you behave, and your private practices stay yours. To picture it, think of a babysitter who keeps their own qualifications and references and can show them to a family when asked, without any platform storing or reselling them.}}

== Structured Data (Linked Data) ==
''Innovation: WikiDeal R&D''

{| class="wikitable"
|-
| Concept origin || Linked Data / Semantic Web, [https://www.w3.org/standards/semanticweb/ Tim Berners-Lee, W3C]
|-
| Status || Research, early prototype
|}

''This page describes a research direction, not a delivered feature. Everything below states what WikiDeal '''aims at''', '''intends to''' explore, or holds as an '''initial hypothesis'''. Nothing here is implemented yet.''

=== Aspects covered on this page ===

Structured Data is explored through several connected aspects, each a section below:

* [[#Why it matters|Why it matters]] (your habits are not for sale, user is not a product)
* [[#What data are we talking about|What data are we talking about]] (private vs published)
* [[#Three intended guarantees|Three intended guarantees]] (private by default, per-transaction control, trust circles)
* [[#Anonymized statistics for the common good|Anonymized statistics for the common good]]
* [[#Data minimisation and local-first|Data minimisation and local-first]]
* [[#Decentralised identity|Decentralised identity]] and the [[#Decentralized Web|Decentralized Web]]
* [[#Selective disclosure|Selective disclosure]]
* [[#Legal compliance: GDPR, eIDAS 2.0 and beyond|Legal compliance (GDPR, eIDAS 2.0)]]
* [[#Data governance: future hypotheses|Data governance: future hypotheses]]

=== Why it matters ===

On most platforms today, if a service is free of charge, the user tends to be the product: behaviour is collected, analysed, and resold (a pattern often described as [https://en.wikipedia.org/wiki/Surveillance_capitalism surveillance capitalism]). WikiDeal '''is guided by''' the opposite principle. The intention is that there is no resale of users' habits or commercial tendencies, because the data is meant to belong to the users themselves.

Put plainly, the goal is that nobody, no other [[Gov/en/Portal:R&D/Innovations:User Groups|User Group]], not the Ynternet.org Foundation, not the WikiDeal operator, gets to walk into your head or your home. Your buying patterns and private commercial practices are meant to stay yours.

A concrete illustration: a babysitter could hold their own qualifications, background-check results, and reputation history, present them to a family on request, and have them verified without the platform storing the underlying data. The same logic '''is intended to''' apply across the marketplace.

=== What data are we talking about ===

WikiDeal handles two distinct kinds of data, and the intended rules differ for each.

'''Private data.''' Identities, contact and bank details, personal photographs, the details of a dwelling someone wants to rent out, and the specific variables a user enters into a contract. The design '''is guided by''' a simple principle: private data stays private by default, and the user decides whether to share it, with a specific counterparty in a negotiation or with a chosen [[Gov/en/Portal:R&D/Innovations:Rings Of Trust|Ring of Trust]].

'''Published data.''' Some data is meant to be public on WikiDeal: the content of contracts the parties choose to publish, the state of a contract (signed, completed, or ended in a dispute), and aggregate usage statistics. This data is published on purpose, not collected and resold.

The structured-data work '''intends to''' cover both kinds (expressing them as [https://en.wikipedia.org/wiki/Resource_Description_Framework RDF], [https://en.wikipedia.org/wiki/JSON-LD JSON-LD], and [https://en.wikipedia.org/wiki/Wikidata Wikidata]-linked resources, in the spirit of [https://en.wikipedia.org/wiki/Linked_data Linked Data] and the [https://en.wikipedia.org/wiki/Semantic_Web Semantic Web]) so each piece of information carries the right status and is machine-readable and interoperable. Governance of all this '''is intended to''' be decided in a '''participative context''', not dictated from above.

=== Three intended guarantees ===

Structured Data '''aims at''' giving users the assurance that they sit inside trust networks ([[Gov/en/Portal:R&D/Innovations:Rings Of Trust|Rings of Trust]]) where they decide whether or not to share their data. Three guarantees sit at the heart of the design.

# '''Private by default.''' The intention is that your data would not be accessible, not by other [[Gov/en/Portal:R&D/Innovations:User Groups|User Groups]], not by the Ynternet.org Foundation, not by the WikiDeal operator. Nobody would see it unless you explicitly grant access. Access would be opt-in, scoped, and revocable.
# '''Per-transaction control.''' For each transaction, you would decide what to reveal and to whom: more for a high-stakes deal, less for a casual one, transaction by transaction.
# '''Choose your trust circles.''' You would affiliate with the [[Gov/en/Portal:R&D/Innovations:Rings Of Trust|Rings of Trust]] you actually trust for data sharing. For example, a User Group offering a hosting service for tenants and landlords could store a member's structured data (photos of dwellings to rent, plus account and bank details) on a third-party server, because the user chose to trust that Ring. Sharing would follow the trust relationship the user opted into, not a platform-wide default.

=== Anonymized statistics for the common good ===

Separately from personal data, WikiDeal '''intends to''' publish anonymized aggregate statistics. Personal data would stay private; only de-identified trends would be shared. The point is decision support: helping people and communities make informed decisions.

Today, this kind of trend data (which is highly valuable, because it reveals tendencies and reactions) is largely held by a few large private groups. WikiDeal '''aims at''' bringing this insight back under public, community control, so that trends can be understood and their impact studied rather than quietly monetised.

This '''is intended to''' open work with the academic world (for example doctoral research) on concrete questions, such as:

* how far certain usage ergonomics (UX patterns) are linked to compulsive buying;
* what real impact discounts and promotional offers have on users' finances.

The double goal '''is guided by''' two interests at once: supporting providers of goods and services, while protecting consumers from mechanics that push them to lose their commercial good sense, and, more broadly, strengthening trust in the system.

Aggregate figures would reveal broad trends and recurring conflict patterns, which in turn would let the community create alerts and improve contracts and safeguards before problems spread. In no case would specific user information be exposed, only listed aggregates such as: how many contracts of a given type were signed, how many were completed, how many ended in a dispute, what type of dispute, and how many disputes were solved.

=== Data minimisation and local-first ===

WikiDeal '''is designed to be guided by''' minimising the platform's access to user data. Where mainstream platforms treat user data as a primary asset, collecting, analysing, and monetising it, WikiDeal '''intends to''' treat data as belonging to users, held only in trust, for minimum periods, in minimum quantities.

The architecture WikiDeal '''is exploring''' is [https://en.wikipedia.org/wiki/Local-first_software local-first]: wherever possible, data would be stored on users' own devices, and only the minimum necessary information would be transmitted to shared Infrastructure. As an initial hypothesis, a babysitting agreement signed by both parties would live on the devices of the family and the babysitter, while the platform Infrastructure would hold only a cryptographic proof that the agreement was signed, not its content, unless both parties consent to shared storage.

This direction is technically challenging (it requires careful design of conflict resolution, backup, and recovery) but it '''aims at''' changing the data power relationship: a platform cannot sell data it does not have. The intention is that, even when WikiDeal eventually serves many babysitters, tutors, and freelancers, it would not have built a surveillance corpus of intimate human behaviour.

=== Decentralised identity ===

WikiDeal '''is evaluating''' decentralised identity approaches ([https://en.wikipedia.org/wiki/Decentralized_identifier decentralised identifiers, DIDs], [https://en.wikipedia.org/wiki/Verifiable_credentials verifiable credentials], part of the wider [https://en.wikipedia.org/wiki/Self-sovereign_identity self-sovereign identity] field) that '''aim at''' enabling trust between strangers without a central identity database. As above, a babysitter's qualifications and reputation could be held by the babysitter, presented on demand, and verified without the platform storing the underlying data. This research is ongoing through the WikiDeal [[Gov/en/Portal:R&D/Living-Labs|Living Labs]] programme.

=== Decentralized Web ===

WikiDeal '''is following''' the general development of the Decentralized Web closely, with or without blockchain. WikiDeal '''starts from''' a deliberately technology-neutral position: this is a starting point, not a settled stance. Positions on specific technologies '''are intended to''' be taken later, on the basis of exchanges, discussions, and position papers, some of which already exist and others still to be written. These '''are among the elements to be studied''', rather than decisions already made.

The goal being explored (user-owned, consent-based, portable data) could be approached through several paths, kept here as research references rather than adopted building blocks:

* '''[https://solidproject.org Solid]''' ([https://en.wikipedia.org/wiki/Solid_(web_decentralization_project) Wikipedia]), Tim Berners-Lee's model of personal data stores ("Pods"), where each user owns their data and grants applications scoped, revocable access.
* '''[https://holochain.org Holochain]''' ([https://en.wikipedia.org/wiki/Holochain Wikipedia]), an '''agent-centric''' [https://en.wikipedia.org/wiki/Peer-to-peer peer-to-peer] framework where each participant keeps their own validated data, with no global ledger. Note: Holochain is '''not [https://en.wikipedia.org/wiki/Blockchain blockchain]-based'''; instead of one shared ledger maintained by global consensus, each agent holds its own hash chain and data is shared over a [https://en.wikipedia.org/wiki/Distributed_hash_table distributed hash table].
* '''[https://ipfs.io IPFS]''' ([https://en.wikipedia.org/wiki/InterPlanetary_File_System Wikipedia]), content addressing, and, where genuinely useful, [https://en.wikipedia.org/wiki/Distributed_ledger distributed ledgers].
* '''Third-party / federated hosting''', where structured data could live on a trusted third-party server chosen by the user.

For an overview of this wider field, two external observatories are useful references:

* '''[https://github.com/gdamdam/awesome-decentralized-web Awesome Decentralized Web]''' (a curated list of decentralised protocols and tools, notably excluding crypto/blockchain/NFT projects).
* '''[https://www.decentralizedweb.net Decentralized Web Summit]''' (the Internet Archive gathering that has tracked this field since its early days).

This connects to WikiDeal's broader stance: see [[Gov/en/Portal:Data/Blockchains|Blockchains & Smart Contracts]] for where blockchain and smart contracts are (and are not) considered appropriate, and [[Gov/en/Portal:Data/Decentralized-Data|Decentralized Data]] for the data-minimisation principles that underpin the approach. By expressing data as open linked resources, WikiDeal '''aims at''' keeping the door open to interoperate with these infrastructures as they mature, so the platform's information could stay open, portable, and owned by its community rather than locked into a single provider.

=== Selective disclosure ===

For marketplace Transactions, WikiDeal '''is exploring''' a [https://en.wikipedia.org/wiki/Selective_disclosure selective disclosure] model: the intention is that parties would share only the data necessary to complete a Transaction, and that dispute resolution could proceed without exposing private communications to the operators unless legally required. How reputation could be presented while keeping the underlying ratings private is one of the open questions to be studied; no specific protocol is settled at this stage.

Funders' individual contribution data '''is intended to''' stay strictly confidential. Aggregate figures (total number of funders, total CHF raised, distribution of Community vs [[Gov/en/Portal:Economy/Cash-Rewards|Cash Rewards]] allocations) would be published transparently; individual allocations would never be disclosed without explicit consent.

=== Legal compliance: GDPR, eIDAS 2.0 and beyond ===

This research direction '''is intended to''' be developed in line with applicable data-protection and digital-identity law, not against it.

* '''[https://en.wikipedia.org/wiki/General_Data_Protection_Regulation GDPR]''' (EU General Data Protection Regulation). The principles described above (data minimisation, private-by-default, user consent, purpose limitation, the right to access and erase one's data) are meant to align with GDPR rather than merely tolerate it. Anonymized statistics '''are intended to''' rely on genuinely de-identified data so that they fall outside the scope of personal data.
* '''[https://en.wikipedia.org/wiki/EIDAS eIDAS 2.0]''' (the EU regulation framing digital identity, including the European Digital Identity Wallet). The decentralised-identity work '''aims at''' staying compatible with this emerging framework, so that verifiable credentials and self-presented qualifications could interoperate with officially recognised digital identity where relevant.

These are stated as '''design intentions and starting hypotheses''', to be confirmed with legal counsel as the project matures. Compatibility with other national and sector-specific legislation '''is intended to''' be assessed case by case.

=== Data governance: future hypotheses ===

The following is an '''initial hypothesis''', not a roadmap.

The guiding idea is simple: '''protection is complete by default''', and users could then choose, transaction by transaction, to share more in exchange for specific advantages, always under citizen supervision. The point is user choice, with no single data regime imposed on everyone. How this choice would be organised in practice is left open, to be defined later in a participative way as the project matures.

----
'''See also:''' [[Gov/en/Portal:R&D/Innovations:Main|All innovations]] · [[Gov/en/Portal:R&D/Main|R&D Portal]] · [[Gov/en/Portal:Data/Decentralized-Data|Decentralized Data]] · [[Gov/en/Portal:Data/Blockchains|Blockchains & Smart Contracts]] · [[Gov/en/Portal:R&D/Innovations:Rings Of Trust|Rings of Trust]]

[[Category:Migration June 2026]]

Gov/en/Portal:R&D/Innovations:Structured Data

2026-06-20T13:03:12Z

Creativesoul4ever: added "user is not a product" to make it clear

{{KidsIntro|"Structured data" means organising information so computers can read it and connect it, like putting a clear label on every box so the right machine can find what is inside. On WikiDeal, some data is private (your identity, your bank details, photos of a flat you want to rent out) and some data is public on purpose (the content of contracts people choose to publish, whether a contract was signed or completed, and overall usage statistics). One idea guides the whole effort: your habits and your commercial behaviour are not for sale. It is a bit like nobody being allowed to walk into your head or your home: what you buy, how you behave, and your private practices stay yours. To picture it, think of a babysitter who keeps their own qualifications and references and can show them to a family when asked, without any platform storing or reselling them.}}

{{NotApproved}}

== Structured Data (Linked Data) ==
''Innovation: WikiDeal R&D''

{| class="wikitable"
|-
| Concept origin || Linked Data / Semantic Web, [https://www.w3.org/standards/semanticweb/ Tim Berners-Lee, W3C]
|-
| Status || Research, early prototype
|}

''This page describes a research direction, not a delivered feature. Everything below states what WikiDeal '''aims at''', '''intends to''' explore, or holds as an '''initial hypothesis'''. Nothing here is implemented yet.''

=== Aspects covered on this page ===

Structured Data is explored through several connected aspects, each a section below:

* [[#Why it matters|Why it matters]] (your habits are not for sale, user is not a product)
* [[#What data are we talking about|What data are we talking about]] (private vs published)
* [[#Three intended guarantees|Three intended guarantees]] (private by default, per-transaction control, trust circles)
* [[#Anonymized statistics for the common good|Anonymized statistics for the common good]]
* [[#Data minimisation and local-first|Data minimisation and local-first]]
* [[#Decentralised identity|Decentralised identity]] and the [[#Decentralized Web|Decentralized Web]]
* [[#Selective disclosure|Selective disclosure]]
* [[#Legal compliance: GDPR, eIDAS 2.0 and beyond|Legal compliance (GDPR, eIDAS 2.0)]]
* [[#Data governance: future hypotheses|Data governance: future hypotheses]]

=== Why it matters ===

On most platforms today, if a service is free, the user tends to be the product: behaviour is collected, analysed, and resold (a pattern often described as [https://en.wikipedia.org/wiki/Surveillance_capitalism surveillance capitalism]). WikiDeal '''is guided by''' the opposite principle. The intention is that there is no resale of users' habits or commercial tendencies, because the data is meant to belong to the users themselves.

Put plainly, the goal is that nobody, no other [[Gov/en/Portal:R&D/Innovations:User Groups|User Group]], not the Ynternet.org Foundation, not the WikiDeal operator, gets to walk into your head or your home. Your buying patterns and private commercial practices are meant to stay yours.

A concrete illustration: a babysitter could hold their own qualifications, background-check results, and reputation history, present them to a family on request, and have them verified without the platform storing the underlying data. The same logic '''is intended to''' apply across the marketplace.

=== What data are we talking about ===

WikiDeal handles two distinct kinds of data, and the intended rules differ for each.

'''Private data.''' Identities, contact and bank details, personal photographs, the details of a dwelling someone wants to rent out, and the specific variables a user enters into a contract. The design '''is guided by''' a simple principle: private data stays private by default, and the user decides whether to share it, with a specific counterparty in a negotiation or with a chosen [[Gov/en/Portal:R&D/Innovations:Rings Of Trust|Ring of Trust]].

'''Published data.''' Some data is meant to be public on WikiDeal: the content of contracts the parties choose to publish, the state of a contract (signed, completed, or ended in a dispute), and aggregate usage statistics. This data is published on purpose, not collected and resold.

The structured-data work '''intends to''' cover both kinds (expressing them as [https://en.wikipedia.org/wiki/Resource_Description_Framework RDF], [https://en.wikipedia.org/wiki/JSON-LD JSON-LD], and [https://en.wikipedia.org/wiki/Wikidata Wikidata]-linked resources, in the spirit of [https://en.wikipedia.org/wiki/Linked_data Linked Data] and the [https://en.wikipedia.org/wiki/Semantic_Web Semantic Web]) so each piece of information carries the right status and is machine-readable and interoperable. Governance of all this '''is intended to''' be decided in a '''participative context''', not dictated from above.

=== Three intended guarantees ===

Structured Data '''aims at''' giving users the assurance that they sit inside trust networks ([[Gov/en/Portal:R&D/Innovations:Rings Of Trust|Rings of Trust]]) where they decide whether or not to share their data. Three guarantees sit at the heart of the design.

# '''Private by default.''' The intention is that your data would not be accessible, not by other [[Gov/en/Portal:R&D/Innovations:User Groups|User Groups]], not by the Ynternet.org Foundation, not by the WikiDeal operator. Nobody would see it unless you explicitly grant access. Access would be opt-in, scoped, and revocable.
# '''Per-transaction control.''' For each transaction, you would decide what to reveal and to whom: more for a high-stakes deal, less for a casual one, transaction by transaction.
# '''Choose your trust circles.''' You would affiliate with the [[Gov/en/Portal:R&D/Innovations:Rings Of Trust|Rings of Trust]] you actually trust for data sharing. For example, a User Group offering a hosting service for tenants and landlords could store a member's structured data (photos of dwellings to rent, plus account and bank details) on a third-party server, because the user chose to trust that Ring. Sharing would follow the trust relationship the user opted into, not a platform-wide default.

=== Anonymized statistics for the common good ===

Separately from personal data, WikiDeal '''intends to''' publish anonymized aggregate statistics. Personal data would stay private; only de-identified trends would be shared. The point is decision support: helping people and communities make informed decisions.

Today, this kind of trend data (which is highly valuable, because it reveals tendencies and reactions) is largely held by a few large private groups. WikiDeal '''aims at''' bringing this insight back under public, community control, so that trends can be understood and their impact studied rather than quietly monetised.

This '''is intended to''' open work with the academic world (for example doctoral research) on concrete questions, such as:

* how far certain usage ergonomics (UX patterns) are linked to compulsive buying;
* what real impact discounts and promotional offers have on users' finances.

The double goal '''is guided by''' two interests at once: supporting providers of goods and services, while protecting consumers from mechanics that push them to lose their commercial good sense, and, more broadly, strengthening trust in the system.

Aggregate figures would reveal broad trends and recurring conflict patterns, which in turn would let the community create alerts and improve contracts and safeguards before problems spread. In no case would specific user information be exposed, only listed aggregates such as: how many contracts of a given type were signed, how many were completed, how many ended in a dispute, what type of dispute, and how many disputes were solved.

=== Data minimisation and local-first ===

WikiDeal '''is designed to be guided by''' minimising the platform's access to user data. Where mainstream platforms treat user data as a primary asset, collecting, analysing, and monetising it, WikiDeal '''intends to''' treat data as belonging to users, held only in trust, for minimum periods, in minimum quantities.

The architecture WikiDeal '''is exploring''' is [https://en.wikipedia.org/wiki/Local-first_software local-first]: wherever possible, data would be stored on users' own devices, and only the minimum necessary information would be transmitted to shared Infrastructure. As an initial hypothesis, a babysitting agreement signed by both parties would live on the devices of the family and the babysitter, while the platform Infrastructure would hold only a cryptographic proof that the agreement was signed, not its content, unless both parties consent to shared storage.

This direction is technically challenging (it requires careful design of conflict resolution, backup, and recovery) but it '''aims at''' changing the data power relationship: a platform cannot sell data it does not have. The intention is that, even when WikiDeal eventually serves many babysitters, tutors, and freelancers, it would not have built a surveillance corpus of intimate human behaviour.

=== Decentralised identity ===

WikiDeal '''is evaluating''' decentralised identity approaches ([https://en.wikipedia.org/wiki/Decentralized_identifier decentralised identifiers, DIDs], [https://en.wikipedia.org/wiki/Verifiable_credentials verifiable credentials], part of the wider [https://en.wikipedia.org/wiki/Self-sovereign_identity self-sovereign identity] field) that '''aim at''' enabling trust between strangers without a central identity database. As above, a babysitter's qualifications and reputation could be held by the babysitter, presented on demand, and verified without the platform storing the underlying data. This research is ongoing through the WikiDeal [[Gov/en/Portal:R&D/Living-Labs|Living Labs]] programme.

=== Decentralized Web ===

WikiDeal '''is following''' the general development of the Decentralized Web closely, with or without blockchain. WikiDeal '''starts from''' a deliberately technology-neutral position: this is a starting point, not a settled stance. Positions on specific technologies '''are intended to''' be taken later, on the basis of exchanges, discussions, and position papers, some of which already exist and others still to be written. These '''are among the elements to be studied''', rather than decisions already made.

The goal being explored (user-owned, consent-based, portable data) could be approached through several paths, kept here as research references rather than adopted building blocks:

* '''[https://solidproject.org Solid]''' ([https://en.wikipedia.org/wiki/Solid_(web_decentralization_project) Wikipedia]), Tim Berners-Lee's model of personal data stores ("Pods"), where each user owns their data and grants applications scoped, revocable access.
* '''[https://holochain.org Holochain]''' ([https://en.wikipedia.org/wiki/Holochain Wikipedia]), an '''agent-centric''' [https://en.wikipedia.org/wiki/Peer-to-peer peer-to-peer] framework where each participant keeps their own validated data, with no global ledger. Note: Holochain is '''not [https://en.wikipedia.org/wiki/Blockchain blockchain]-based'''; instead of one shared ledger maintained by global consensus, each agent holds its own hash chain and data is shared over a [https://en.wikipedia.org/wiki/Distributed_hash_table distributed hash table].
* '''[https://ipfs.io IPFS]''' ([https://en.wikipedia.org/wiki/InterPlanetary_File_System Wikipedia]), content addressing, and, where genuinely useful, [https://en.wikipedia.org/wiki/Distributed_ledger distributed ledgers].
* '''Third-party / federated hosting''', where structured data could live on a trusted third-party server chosen by the user.

For an overview of this wider field, two external observatories are useful references:

* '''[https://github.com/gdamdam/awesome-decentralized-web Awesome Decentralized Web]''' (a curated list of decentralised protocols and tools, notably excluding crypto/blockchain/NFT projects).
* '''[https://www.decentralizedweb.net Decentralized Web Summit]''' (the Internet Archive gathering that has tracked this field since its early days).

This connects to WikiDeal's broader stance: see [[Gov/en/Portal:Data/Blockchains|Blockchains & Smart Contracts]] for where blockchain and smart contracts are (and are not) considered appropriate, and [[Gov/en/Portal:Data/Decentralized-Data|Decentralized Data]] for the data-minimisation principles that underpin the approach. By expressing data as open linked resources, WikiDeal '''aims at''' keeping the door open to interoperate with these infrastructures as they mature, so the platform's information could stay open, portable, and owned by its community rather than locked into a single provider.

=== Selective disclosure ===

For marketplace Transactions, WikiDeal '''is exploring''' a [https://en.wikipedia.org/wiki/Selective_disclosure selective disclosure] model: the intention is that parties would share only the data necessary to complete a Transaction, and that dispute resolution could proceed without exposing private communications to the operators unless legally required. How reputation could be presented while keeping the underlying ratings private is one of the open questions to be studied; no specific protocol is settled at this stage.

Funders' individual contribution data '''is intended to''' stay strictly confidential. Aggregate figures (total number of funders, total CHF raised, distribution of Community vs [[Gov/en/Portal:Economy/Cash-Rewards|Cash Rewards]] allocations) would be published transparently; individual allocations would never be disclosed without explicit consent.

=== Legal compliance: GDPR, eIDAS 2.0 and beyond ===

This research direction '''is intended to''' be developed in line with applicable data-protection and digital-identity law, not against it.

* '''[https://en.wikipedia.org/wiki/General_Data_Protection_Regulation GDPR]''' (EU General Data Protection Regulation). The principles described above (data minimisation, private-by-default, user consent, purpose limitation, the right to access and erase one's data) are meant to align with GDPR rather than merely tolerate it. Anonymized statistics '''are intended to''' rely on genuinely de-identified data so that they fall outside the scope of personal data.
* '''[https://en.wikipedia.org/wiki/EIDAS eIDAS 2.0]''' (the EU regulation framing digital identity, including the European Digital Identity Wallet). The decentralised-identity work '''aims at''' staying compatible with this emerging framework, so that verifiable credentials and self-presented qualifications could interoperate with officially recognised digital identity where relevant.

These are stated as '''design intentions and starting hypotheses''', to be confirmed with legal counsel as the project matures. Compatibility with other national and sector-specific legislation '''is intended to''' be assessed case by case.

=== Data governance: future hypotheses ===

The following is an '''initial hypothesis''', not a roadmap.

The guiding idea is simple: '''protection is complete by default''', and users could then choose, transaction by transaction, to share more in exchange for specific advantages, always under citizen supervision. The point is user choice, with no single data regime imposed on everyone. How this choice would be organised in practice is left open, to be defined later in a participative way as the project matures.

----
'''See also:''' [[Gov/en/Portal:R&D/Innovations:Main|All innovations]] · [[Gov/en/Portal:R&D/Main|R&D Portal]] · [[Gov/en/Portal:Data/Decentralized-Data|Decentralized Data]] · [[Gov/en/Portal:Data/Blockchains|Blockchains & Smart Contracts]] · [[Gov/en/Portal:R&D/Innovations:Rings Of Trust|Rings of Trust]]

[[Category:Migration June 2026]]

WikiDeal

2026-06-15T13:48:43Z

Creativesoul4ever: added June 2026 to make it clear

{{DISPLAYTITLE:Welcome to WikiDeal}}

<div style="background:#eef6ff; border:1px solid #9cc3e8; border-left:4px solid #4a90d9; border-radius:4px; padding:14px 18px; margin-bottom:20px;">
'''June 2026 - A new step begins : the pre-launch publication phase'''

WikiDeal is entering a new phase. The project stays exactly the same in its mission; what changes is that we are now '''publishing''' the governance, economy and research work that has been developed — so it can be read, discussed and improved.

This is a '''pre-community-opening publication''': the content below is shared ahead of the community opening. It is '''not yet open for participation''' — soon there will be news with concrete opportunities to take part. Everything published in this phase is documented openly and marked as ''not yet approved'' while it is under review.

''Follow the [[Special:RecentChanges|recent changes]] to see the migration happening live.''
</div>

== Our founding question ==
WikiDeal is, at its core, a research and development project that explores one question:

<blockquote style="font-size:1.15rem; font-style:italic; border-left:3px solid #4a90d9; padding-left:14px; color:#243b53;">
[[Gov/en/Portal:Onboarding/Glossary:Founding Question#CAN|Can]] [[Gov/en/Portal:Onboarding/Glossary:Founding Question#USERS|users]] [[Gov/en/Portal:Onboarding/Glossary:Founding Question#OWN|own]], [[Gov/en/Portal:Onboarding/Glossary:Founding Question#RUN|run]] [[Gov/en/Portal:Onboarding/Glossary:Founding Question#AND|and]] [[Gov/en/Portal:Onboarding/Glossary:Founding Question#SUSTAIN|sustain]] [[Gov/en/Portal:Onboarding/Glossary:Founding Question#A|a]] [[Gov/en/Portal:Onboarding/Glossary:Founding Question#GLOBAL|global]] [[Gov/en/Portal:Onboarding/Glossary:Founding Question#MARKETPLACE|marketplace]]?
</blockquote>

Our answer is: '''yes — but only if the governance model is radically different.''' This means combining the principles of digital commons (like Wikipedia), a cooperative commission model, and community-driven value distribution. The pages below document how we propose to make that work.

== Explore the work ==
* 🚀 [[Gov/en/Portal:Onboarding/Main|Get started]] — how to read and contribute (Onboarding)
* 🏛️ [[Gov/en/Portal:R&D/Main|Governance & R&D]] — the full governance and research program
* 💡 [[Gov/en/Portal:R&D/Innovations:Main|Innovations]] — the socio-economic innovations behind WikiDeal
* 💸 [[Gov/en/Portal:Economy/Main|Economy & funding]] — subscriptions, rewards, credits and the funding model
* 🛒 [[Market:Home|Markets]] — the marketplaces and contract models
* 👥 [[WikiDeal:Community portal|Community portal]] · 🔄 [[Special:RecentChanges|Recent changes]]

== What is WikiDeal? ==
WikiDeal is a community providing [[:Category:Contract Models|models of contracts]] and a marketplace to make deals using these contracts.

Like on Wikipedia, you can freely access, edit and adapt these contracts, for any context and needs. Each contract model is connected to a community of users dedicated to improving the contract model, and the marketplace associated with it.

== A common owned by its users ==
Users can contribute to developing the platform's technology, legal support and new marketplaces. Coaching to design and adapt deals, mediation & arbitration for fair compensation...

WikiDeal adopts the highest standards on ethics, privacy, customer support, free licensing, low costs and high efficiency, inspired by the participatory governance of Wikipedia and free software projects.

== Try our prototype ==
You can find our alpha-version proof of concept at https://app.wikideal.net, which is made of two parts:

# A "contract builder" which allows you to use one of the contract templates on our wiki, customize it with your own information, and export the result.
# A "contract uploader" which allows you to contribute contracts that you have used in the past, so that the WikiDeal community can use them as inspiration to build new contract models or improve existing ones.

== Learn more ==
* [[Market:Home|Markets]]
* [[User group:Home|User groups]]
* About the WikiDeal project
** [[WikiDeal:About|About]]
** [[WikiDeal:Development|Development]]
** [[WikiDeal:Key Features|Key Features]]
** [[WikiDeal:Minimum Viable Product|Minimum Viable Product]]
** [[WikiDeal:Principles|Principles]]
** [[WikiDeal:Services|Services]]
** [[WikiDeal:Copyrights|Copyrights and licensing]]
* [[:Category:Contract Models]]

== Stay up to date ==
Sign up to be informed about the latest developments of the WikiDeal project! You can also subscribe to our [https://t.me/wikideal_news Telegram Channel].

{{#widget:NewsletterSignup}}

----
<div style="text-align:center; font-style:italic; color:#555; margin-top:20px;">WikiDeal — Des Pactes Justes avec des gens bien.</div>
[[Category:Project info]]

WikiDeal

2026-06-13T18:57:56Z

Creativesoul4ever: Reverted edits by AI-Admin-Assistant (talk) to last revision by SpectrumMigou

{{DISPLAYTITLE:Welcome to WikiDeal}}
WikiDeal is a community providing [[:Category:Contract Models|models of contracts]] and a marketplace to make deals using these contracts.

Like on Wikipedia, you can freely access, edit and adapt these contracts, for any context and needs. Each contract model will be connected to a community of users dedicated to improving the contract model, and the marketplace associated with it.

== Contribute ==
You can contribute to the incubation of our different [[Market:Home|markets]] by creating an account on this wiki and editing the relevant pages.

You can join an existing [[User group:Home|user group]] or start your own to coordinate efforts contributing to specific parts of the WikiDeal ecosystem.

You can also send us examples of contracts you have used in the past through our [https://app.wikideal.net/uploader contract uploader], so that the community can use them as a source of inspiration for designing new contract models.

Please send us an email at team@wikideal.net if you’re interested in further contributing to the project, or in investing financially in WikiDeal!

== Try our prototype ==
You can find our alpha-version proof of concept at https://app.wikideal.net, which is made of two parts:

# A “contract builder” which allows you to use a one of the contract templates that are on our wiki, customize it with our own information, and export the result.
# A “contract uploader” which allows you to contribute the contracts that you have used in the past, so that the WikiDeal community can use them as inspiration to build new contract models or improve existing ones.

== A common owned by its users ==
Users can contribute to developing the platform's technology, legal support and new marketplaces. Coaching to design and adapt deals, mediation & arbitration for fair compensation...

WikiDeal adopts the highest standards on ethics, privacy, customer support, free licensing, low costs and high efficiency, inspired by the participatory governance of Wikipedia and free software projects.

== Learn more ==
* [[Market:Home|Markets]]
* [[User group:Home|User groups]]
* About the WikiDeal project
** [[WikiDeal:About|About]]
** [[WikiDeal:Development|Development]]
** [[WikiDeal:Key Features|Key Features]]
** [[WikiDeal:Minimum Viable Product|Minimum Viable Product]]
** [[WikiDeal:Principles|Principles]]
** [[WikiDeal:Services|Services]]
** [[WikiDeal:Copyrights|Copyrights and licensing]]
* [[:Category:Contract Models]]

== Stay up to date ==

Sign up to be informed about the latest developments of the WikiDeal project! You can also subscribe to our [https://t.me/wikideal_news Telegram Channel].

{{#widget:NewsletterSignup}}
[[Category:Project info]]

User:Creativesoul4ever

2026-03-23T02:48:13Z

Creativesoul4ever: added link to my personal website

creativesoul4ever is the pseudo I use to post in wikideal

More about me see [http://www.theobondolfi.net www.theobondolfi.net]

Portal:Demo Template

2026-03-21T19:45:25Z

Creativesoul4ever: just changed any deal by (wiki) deal

{{AI Disclaimer}}
__TOC__

== Demo Template Portal ==

This is the '''demonstration template''' for WikiDeal thematic portals. It illustrates the standard structure that every real portal will follow.

We chose '''Venus Bicycle Lending''' as our example — a deliberately surreal scenario to make it clear this is a template, not a real portal. If the structure works for lending bicycles on Venus, it works for any (wiki) deal on Earth.

''Every new thematic portal (Lending, Rental, Employment, Freelance, etc.) will be created by replicating this template and adapting the content.''

== Quick Links ==

* 📄 [[Portal:Demo_Template/Base_Contract|Base Contract]] — The standard Venus Bicycle Lending Agreement
* ⚖️ [[Portal:Demo_Template/Legal_References|Legal References]] — Applicable Venus Colony Regulations
* 📋 [[Portal:Demo_Template/Terms_of_Use|Terms of Use]] — General conditions
* ✏️ [[Portal:Demo_Template/Amendments|Amendments]] — Known modifications
* ➕ [[Portal:Demo_Template/Addenda|Addenda]] — Supplementary clauses
* 🔚 [[Portal:Demo_Template/Closing_Contracts|Closing Contracts]] — Termination templates
* ⚖️ [[Portal:Demo_Template/Arbitration|Arbitration]] — Content coming soon
* 💰 [[Portal:Demo_Template/Compensatory_Measures|Compensatory Measures]] — What happens if the bicycle falls off a cloud platform
* 🔔 [[Portal:Demo_Template/Alerts|Alerts]] — Reminders (acid rain warnings, return deadlines)
* 📝 [[Portal:Demo_Template/Summary|Summary]] — Plain-language overview
* 💡 [[Portal:Demo_Template/Usage_Advice|Usage Advice]] — Tips from experienced Venus cyclists

== About This Template ==

On Venus, where the cloud cities offer surprisingly smooth surfaces, bicycles and roller skates are the preferred modes of transport. This portal demonstrates every component a real thematic portal would contain: base contracts, legal references, compensatory measures, alerts, summaries, and usage advice — all linked and interdependent.

''→ See also: [[Portal:AI_Assistance]] | [[Portal:Validation]]''

Basic Example Contract

2024-10-29T13:35:36Z

Creativesoul4ever: /* Basic Contract Agreement */ interverted clause 1 and 2 to test

[[index.php?title=Category:Contract Models]]
== Basic Contract Agreement ==

This Contract ("Agreement") is made and entered into on {{{ WD_contract_date }}} by and between {{{ WD_party_one_name }}}, located at {{{ WD_party_one_address }}}, and {{{ WD_party_two_name }}}, located at {{{ WD_party_two_address }}}.

'''This Agreement is for testing purposes only and does not constitute a legally binding contract.'''

=== 2. Payment ===

{{{ WD_party_two_name }}} agrees to pay {{{ WD_payment_amount }}} to {{{ WD_party_one_name }}} for the services described above. Payment shall be made within {{{ WD_payment_due_days }}} days of the completion of services.

=== 1. Services ===

{{{ WD_party_one_name }}} agrees to provide the following services to {{{ WD_party_two_name }}}:
{{{ WD_services_description }}}.

{{{ WD_party_two_name }}} agrees to pay {{{ WD_payment_amount }}} to {{{ WD_party_one_name }}} for the services described above. Payment shall be made within {{{ WD_payment_due_days }}} days of the completion of services.

=== 3. Term ===

This Agreement shall commence on {{{ WD_start_date }}} and shall continue until {{{ WD_end_date }}}, unless terminated earlier in accordance with the terms of this Agreement.

=== 4. Termination ===

Either party may terminate this Agreement with {{{ WD_termination_notice_days }}} days' written notice to the other party.

=== 5. Governing Law ===

This Agreement shall be governed by the laws of {{{ WD_governing_law_state }}}.

----

== Signatures ==

_____________________________
{{{ WD_party_one_name }}}

_____________________________
{{{ WD_party_two_name }}}

WikiDeal:Key Features

2024-04-15T14:09:56Z

Creativesoul4ever: embettered the text

'''WikiDeal in a nutshell? The Wikipedia of deals.'''

WikiDeal aims at offering better deals at lower prices (reducing fees) for transportation (like Uber and Blablacar), hosting (like Airbnb & Booking) and more (see below "Wikideal services - usecases").

The core services are contracts and online support to sell, rent, employ, share ...

Like on Wikipedia, you can freely access, edit and adapt the contracts for your specific contexts and needs.

Lawyers and assistants propose you optional hotline & coaching services to design and manage your deals, including bench marking (for pricing, parametering...), externalizing operational tasks ...

For instance, you can ask them "please manage my empty apartment, put it on rent, and take a fair commission fee on each deal".

If you contribute as volunteer, like on wikipedia, you get rewards (bonus) to use as voucher for transportation, hosting etc. Like on wikipedia, you have dozens of volunteering options to make empower Wikideal community.

'''Who owns WikiDeal? It's a common, owned by its users.'''

Each user has to buy one share (costs CHF 10.- plus 5% increase/year), in one or many microparts (for instance CHF 1.- on each wikideal transaction).

Users can also contribute in developing the platform’s technology, legal support, marketplaces and governance, like on wikipedia.

User's groups gathers to create poles of activities (geographical such as Polandarbitration chamber) and on

'''How is it governed?'''

WikiDeal gathers the highest standards on ethics, privacy, customer support, free licensing, low costs and high efficiency, inspired by the Wikimedia foundation participative governance (who's operating Wikipedia and 13 related projects such as wikispecies, wiktionary...).

'''WIKIDEAL SERVICES (USECASES)'''

The '''Minimum Viable Product''' (MVP) is planned to provide the following wiki-managed features:

* Models of ''ready to use and customizable'' '''contracts (“deals”)''', agreements and rules of functioning.
** Each contract includes optional '''clauses''' to help make fair deals, such as adapted conditions of payment, simplified arbitration for conflicts and easy authentication of signatures.
** Each clause of each contract is easy to adapt, '''edit''', comment, explain and refer to laws and stats.
* Automated scenarios helping dealers '''select and respect each clause of their deals,''' raising awareness with ''tutorials'', ''reminders'', ''amendments'', ''alerts'', stats, ''use cases and terms of interpretation'' …
* Conflict prevention and resolution between WikiDealers using '''coaching, mediation''' and '''arbitration.'''
* Anonymized big data for '''risk management, including ''incentives'' & ''compensation'' tools''' such as benchmarks on pricing and fines, reputation and karma management, social and ecological impact.
* Fair deal '''enclosure options''' (executing, canceling & resiliating with compensations, transfer).

'''Which deals are we talking about?'''

First, ''peer-to-peer'' deals for everyday life, including:

* Services such as transportation, freelance, internship…
* Renting goods (functional economy) including hosting, vehicles, clothes…
* Buying and selling (ticketing for shows, real estate, food, machines…).
* Loans of goods without middle men (from loaning funds to books or bikes).
* Partnership (employment, pre-nuptial/marriage/divorce, co-owning goods…)
* Most types of deals humans can imagine and need to agree upon.

Then, deals with multiple stakeholders, such as:

* Leasing including three parts: buyers, sellers and loaners (banks, insurance, funds…).
* Social contracts and rules for shared real estate, such as condominiums and communities.
* Private-public partnership, such as those to protect forests or assess quality of products.
* Franchising agreement (such as those between TED Foundation and TEDx event licensees).
* Joint ventures (from co-working to buying shares of a company).
* Pedagogical signage to respect deals, such as waste management rules on a public toilet.

== Components ==

=== Contract models ===
Contract models are predefined models (or templates) of contracts for various agreements or deals. Contract models are provided, edited and discussed by the community just like Wikipedia articles, to make sure the best possible contract model is always provided for a specific purpose.

A contract model is simply comprised of a document title and collection of appropriate clauses that defines the agreement.

A contract model may also contain notes, warnings or other to be decided optional fields that will help users when using the contract model to generate real contracts.

To be decided:

* Architectural implementation of contract models.

=== Clauses ===
A contract model will mostly be just a collection of legal clauses, conditions or provisions. Clauses will be blocks of text that can contain variables. An example of a clause would look like:

“<nowiki>{{ signatory }}</nowiki> agrees to pay <nowiki>{{ offerer }}</nowiki> the amount of <nowiki>{{ fee }}</nowiki> before the <nowiki>{{ day }}</nowiki> of the month for the period <nowiki>{{ start_date }}</nowiki> until <nowiki>{{ end_date }}</nowiki>”

Clauses could have meta information assigned to them based on community feedback. Examples include things like “popularity” or “legal expert verified”. It could also include references or citations to various types of laws that the clause adheres to.

If a clause is verified by a legal expert it should of course not be directly editable, because it will have to reverified after each edit. This means that instead of editing a clause it will create a new clause, keeping the original. The new clause will then become an optional suggestion for creating a contract.

To be decided:

* Should clauses contain the information on which models they belong to (i.e. using [https://www.semantic-mediawiki.org/wiki/Semantic_MediaWiki Semantic MediaWiki])? Or should the contract models contain this information?

=== Creating a contract ===
Using the contract models and clauses users would be able to generate customized contracts for their own purposes.

Envisioned workflow:

# Select an existing contract model.
# Input all the variables that the contract model requires and additional details such as a preamble.
# Fill in all the conditions of the contracts, which decides which clauses will be included in the contract.
# [Optional] Edit the clauses of the contract. This may consist of:
#* Removing clauses.
#* Reordering clauses.
#* Replacing clauses with different clauses in the database of approved alternative clauses.
#* Adding custom clauses.
# Save the contract (for example as PDF) and send it to the stakeholders of this contract.

=== Signing contracts ===
Once a contract has been created and sent to its stakeholders it will have to be signed to conclude a deal.

The signing phase of a contract should ideally not only be a “sign” or “decline” button. In this phase there should also be the possibility for all parties involved to discuss and negotiate on the contract.

In this phase a contract could have statuses, such as:

* Draft
* Conflict
* Being discussed
* Signed
* Denied
* Closed

When this stage is done successfully a deal has been made.

=== Post deal ===
When the deal has been made WikiDeal could provider additional features that make the execution of the deal easier. Examples of features in this stage could include, but are not limited to:

* If a contract contains dates or deadlines WikiDeal could send reminders to the parties involved. This would also apply to monthly repeating clauses.
* If a contract contains a monetary transaction WikiDeal could provide payment links that already includes the monetary amounts as stated within the contract.
* If a contract is related to a service it could be programmatically linked to automatic activation/cancellation of said service when signed.

=== Decentralization ===
Because contracts contain private information they should not be stored on the main centralized main WikiDeal server. Creating a contract on the site should only allow the user to save the contract to their local computer, but not on the main WikiDeal server.

Contracts might temporarily be saved on the WikiDeal server during the Minimum Viable Product stage of development for convenience.

Instead ideally we would develop an external tool to generate contracts using the centralized community driven data of WikiDeal, but without storing any personal data. This will make users fully in charge of their own personal data while still using the crowd-sourced data that WikiDeal provides.

For organizations using WikiDeal we envision a decentralized system where the organization hosts their own WikiDeal instance. The organization instance will use the data provided by WikiDeal for contract models and clauses, but it will store all personal data of its organization only on their own WikiDeal instance.

For contracts between individuals we envision a decentralized system using instances (similar to the fediverse or email). This allows users to be in control of their data by either signing up to an instance that they trust or choosing to host their own.

Alternatively we could also consider some sort of fully peer to peer approach to making deals but details of this have not been thought out.

== Proof of concept ==
Before making a Minimum Viable Product (MVP) it might be a good idea to make a proof concept first.

The proof of concept will likely just include:

* Contract models.
* Clauses.
* Creating contracts (very basic implementation).

This is to focus on establishing WikiDeal as a really useful public repository for clauses and contract models and so we can see if the envisioned architecture we end up choosing works as expected.

A proof of concept will give us a good place to interature further upon and this also gives us more time to work out the details of what a MVP should contain.

== Minimum Viable Product ==
See: [[Minimum Viable Product]]

== Outdated feature matrix information that might be used for future reference: ==
{| class="wikitable"
|'''Contract Models'''
|Prio
|Hours
|-
|Base model type which can contain a collection of clauses
|1
|
|-
|Conditional clauses and options to customize the clauses
|2
|
|-
|Notes and help texts
|3
|
|-
|'''Clauses'''
|
|
|-
|Base clause type
|1
|
|-
|Clause variables
|1
|
|-
|Citations in clauses
|2
|
|-
|Statistics (maturity, references, etc.)
|2
|
|-
|Notes and help texts
|3
|
|-
|'''Creating a contract'''
|
|
|-
|Entering basic variables (names, date, preamble, etc.)
|1
|
|-
|Enabling conditional clauses
|2
|
|-
|Visual contract editor
|1
|
|-
|Save as PDF or other formats
|2
|
|-
|Send to stakeholders
|3
|
|-
|Annex and attachments to contracts
|3
|
|-
|'''Signing contracts'''
|
|
|-
|Basic signing of contracts
|1
|
|-
|Discussion and negotiation
|2
|
|-
|Various states (draft, conflict, denied, signed, etc.)
|1
|
|-
|'''Post deal'''
|
|
|-
|Sending reminders
|2
|
|-
|Automation API
|3
|
|}

=== Additional features (likely not in MVP) ===
{| class="wikitable"
|'''Creating a contract'''
|Hours
|-
|Personalized contract styling (typography, etc.)
|
|-
|'''Decentralization'''
|
|-
|External contract creation tool (desktop or phone app)
|
|-
|Self hosted instances (with federation)
|
|-
|True peer to peer contract creation
|
|-
|'''Funding'''
|
|-
|Bounding curve software
|
|}

WikiDeal:Key Features

2024-04-15T09:08:15Z

Creativesoul4ever: formal updated

'''WikiDeal in a nutshell? The Wikipedia of deals.'''

WikiDeal aims at offering better deals at lower prices (reducing fees) for transportation (like Uber and Blablacar), hosting (like Airbnb & Booking) and may more (see below "Wikideal services - usecases").

The core services are contracts to sell, rent, employ, share and coach users...

Like on Wikipedia, you can freely access, edit and adapt the contracts for your specific contexts and needs.

Lawyers and assistants propose you optional hotline & coaching services to design and manage your deals, including bench marking (for pricing, parametering...), externalizing operational tasks ...

For instance, you can ask them "please manage my empty apartment, put it on rent, and take a fair commission fee on each deal".

'''Who owns WikiDeal? It's a common owned by its users.'''

Each user has to buy one share (costs CHF 10.- plus 5% increase/year), in one or many microparts (for instance CHF 1.- on each wikideal transaction).

Users can also contribute in developing the platform’s technology, legal support, marketplaces and governance, like on wikipedia.

User's groups gathers to create poles of activities (geographical such as Polandarbitration chamber) and on

'''How is it governed?'''

WikiDeal gathers the highest standards on ethics, privacy, customer support, free licensing, low costs and high efficiency, inspired by the Wikimedia foundation participative governance (who's operating Wikipedia and 13 related projects such as wikispecies, wiktionary...).

'''WIKIDEAL SERVICES (USECASES)'''

The '''Minimum Viable Product''' (MVP) is planned to provide the following wiki-managed features:

* Models of ''ready to use and customizable'' '''contracts (“deals”)''', agreements and rules of functioning.
** Each contract includes optional '''clauses''' to help make fair deals, such as adapted conditions of payment, simplified arbitration for conflicts and easy authentication of signatures.
** Each clause of each contract is easy to adapt, '''edit''', comment, explain and refer to laws and stats.
* Automated scenarios helping dealers '''select and respect each clause of their deals,''' raising awareness with ''tutorials'', ''reminders'', ''amendments'', ''alerts'', stats, ''use cases and terms of interpretation'' …
* Conflict prevention and resolution between WikiDealers using '''coaching, mediation''' and '''arbitration.'''
* Anonymized big data for '''risk management, including ''incentives'' & ''compensation'' tools''' such as benchmarks on pricing and fines, reputation and karma management, social and ecological impact.
* Fair deal '''enclosure options''' (executing, canceling & resiliating with compensations, transfer).

'''Which deals are we talking about?'''

First, ''peer-to-peer'' deals for everyday life, including:

* Services such as transportation, freelance, internship…
* Renting goods (functional economy) including hosting, vehicles, clothes…
* Buying and selling (ticketing for shows, real estate, food, machines…).
* Loans of goods without middle men (from loaning funds to books or bikes).
* Partnership (employment, pre-nuptial/marriage/divorce, co-owning goods…)
* Most types of deals humans can imagine and need to agree upon.

Then, deals with multiple stakeholders, such as:

* Leasing including three parts: buyers, sellers and loaners (banks, insurance, funds…).
* Social contracts and rules for shared real estate, such as condominiums and communities.
* Private-public partnership, such as those to protect forests or assess quality of products.
* Franchising agreement (such as those between TED Foundation and TEDx event licensees).
* Joint ventures (from co-working to buying shares of a company).
* Pedagogical signage to respect deals, such as waste management rules on a public toilet.

== Components ==

=== Contract models ===
Contract models are predefined models (or templates) of contracts for various agreements or deals. Contract models are provided, edited and discussed by the community just like Wikipedia articles, to make sure the best possible contract model is always provided for a specific purpose.

A contract model is simply comprised of a document title and collection of appropriate clauses that defines the agreement.

A contract model may also contain notes, warnings or other to be decided optional fields that will help users when using the contract model to generate real contracts.

To be decided:

* Architectural implementation of contract models.

=== Clauses ===
A contract model will mostly be just a collection of legal clauses, conditions or provisions. Clauses will be blocks of text that can contain variables. An example of a clause would look like:

“<nowiki>{{ signatory }}</nowiki> agrees to pay <nowiki>{{ offerer }}</nowiki> the amount of <nowiki>{{ fee }}</nowiki> before the <nowiki>{{ day }}</nowiki> of the month for the period <nowiki>{{ start_date }}</nowiki> until <nowiki>{{ end_date }}</nowiki>”

Clauses could have meta information assigned to them based on community feedback. Examples include things like “popularity” or “legal expert verified”. It could also include references or citations to various types of laws that the clause adheres to.

If a clause is verified by a legal expert it should of course not be directly editable, because it will have to reverified after each edit. This means that instead of editing a clause it will create a new clause, keeping the original. The new clause will then become an optional suggestion for creating a contract.

To be decided:

* Should clauses contain the information on which models they belong to (i.e. using [https://www.semantic-mediawiki.org/wiki/Semantic_MediaWiki Semantic MediaWiki])? Or should the contract models contain this information?

=== Creating a contract ===
Using the contract models and clauses users would be able to generate customized contracts for their own purposes.

Envisioned workflow:

# Select an existing contract model.
# Input all the variables that the contract model requires and additional details such as a preamble.
# Fill in all the conditions of the contracts, which decides which clauses will be included in the contract.
# [Optional] Edit the clauses of the contract. This may consist of:
#* Removing clauses.
#* Reordering clauses.
#* Replacing clauses with different clauses in the database of approved alternative clauses.
#* Adding custom clauses.
# Save the contract (for example as PDF) and send it to the stakeholders of this contract.

=== Signing contracts ===
Once a contract has been created and sent to its stakeholders it will have to be signed to conclude a deal.

The signing phase of a contract should ideally not only be a “sign” or “decline” button. In this phase there should also be the possibility for all parties involved to discuss and negotiate on the contract.

In this phase a contract could have statuses, such as:

* Draft
* Conflict
* Being discussed
* Signed
* Denied
* Closed

When this stage is done successfully a deal has been made.

=== Post deal ===
When the deal has been made WikiDeal could provider additional features that make the execution of the deal easier. Examples of features in this stage could include, but are not limited to:

* If a contract contains dates or deadlines WikiDeal could send reminders to the parties involved. This would also apply to monthly repeating clauses.
* If a contract contains a monetary transaction WikiDeal could provide payment links that already includes the monetary amounts as stated within the contract.
* If a contract is related to a service it could be programmatically linked to automatic activation/cancellation of said service when signed.

=== Decentralization ===
Because contracts contain private information they should not be stored on the main centralized main WikiDeal server. Creating a contract on the site should only allow the user to save the contract to their local computer, but not on the main WikiDeal server.

Contracts might temporarily be saved on the WikiDeal server during the Minimum Viable Product stage of development for convenience.

Instead ideally we would develop an external tool to generate contracts using the centralized community driven data of WikiDeal, but without storing any personal data. This will make users fully in charge of their own personal data while still using the crowd-sourced data that WikiDeal provides.

For organizations using WikiDeal we envision a decentralized system where the organization hosts their own WikiDeal instance. The organization instance will use the data provided by WikiDeal for contract models and clauses, but it will store all personal data of its organization only on their own WikiDeal instance.

For contracts between individuals we envision a decentralized system using instances (similar to the fediverse or email). This allows users to be in control of their data by either signing up to an instance that they trust or choosing to host their own.

Alternatively we could also consider some sort of fully peer to peer approach to making deals but details of this have not been thought out.

== Proof of concept ==
Before making a Minimum Viable Product (MVP) it might be a good idea to make a proof concept first.

The proof of concept will likely just include:

* Contract models.
* Clauses.
* Creating contracts (very basic implementation).

This is to focus on establishing WikiDeal as a really useful public repository for clauses and contract models and so we can see if the envisioned architecture we end up choosing works as expected.

A proof of concept will give us a good place to interature further upon and this also gives us more time to work out the details of what a MVP should contain.

== Minimum Viable Product ==
See: [[Minimum Viable Product]]

== Outdated feature matrix information that might be used for future reference: ==
{| class="wikitable"
|'''Contract Models'''
|Prio
|Hours
|-
|Base model type which can contain a collection of clauses
|1
|
|-
|Conditional clauses and options to customize the clauses
|2
|
|-
|Notes and help texts
|3
|
|-
|'''Clauses'''
|
|
|-
|Base clause type
|1
|
|-
|Clause variables
|1
|
|-
|Citations in clauses
|2
|
|-
|Statistics (maturity, references, etc.)
|2
|
|-
|Notes and help texts
|3
|
|-
|'''Creating a contract'''
|
|
|-
|Entering basic variables (names, date, preamble, etc.)
|1
|
|-
|Enabling conditional clauses
|2
|
|-
|Visual contract editor
|1
|
|-
|Save as PDF or other formats
|2
|
|-
|Send to stakeholders
|3
|
|-
|Annex and attachments to contracts
|3
|
|-
|'''Signing contracts'''
|
|
|-
|Basic signing of contracts
|1
|
|-
|Discussion and negotiation
|2
|
|-
|Various states (draft, conflict, denied, signed, etc.)
|1
|
|-
|'''Post deal'''
|
|
|-
|Sending reminders
|2
|
|-
|Automation API
|3
|
|}

=== Additional features (likely not in MVP) ===
{| class="wikitable"
|'''Creating a contract'''
|Hours
|-
|Personalized contract styling (typography, etc.)
|
|-
|'''Decentralization'''
|
|-
|External contract creation tool (desktop or phone app)
|
|-
|Self hosted instances (with federation)
|
|-
|True peer to peer contract creation
|
|-
|'''Funding'''
|
|-
|Bounding curve software
|
|}

WikiDeal:Services

2023-12-17T01:57:06Z

Creativesoul4ever:

The '''Minimum Viable Product''' (MVP) is planned to provide the following wiki-managed features:

* Models of ''ready to use and customizable'' '''contracts (“deals”)''', agreements and rules of functioning.
** Each contract includes optional '''clauses''' to help make fair deals, such as adapted conditions of payment, cancellation terms, easy authentication of signatures...
** Each clause of each contract is easy to adapt, edit, comment, explain and refer to laws and stats.
* Automated scenarios helping dealers '''select and respect each clause of their deals,''' raising awareness with ''tutorials'', ''reminders'', ''amendments'', ''alerts'', ''stats''…
* Conflict prevention and resolution between WikiDealers using '''coaching, mediation''' and '''arbitration.'''
* Fair deal '''enclosure options''' (executing, cancelling and settlement with compensation or transfer).

== '''Which deals are we talking about?''' ==
First, ''peer-to-peer'' deals for everyday life, including:

* Services such as transportation, freelance, internship…
* Renting goods (functional economy) including hosting, vehicles, clothes…
* Buying and selling (ticketing for shows, real estate, food, machines…).
* Loans of goods without middle men (from loaning funds to books or bikes).
* Partnership (employment, pre-nuptial/marriage/divorce, co-owning goods…)
* All other types of deals humans can imagine.

Then, deals with multiple stakeholders, such as:

* Leasing including three parts: buyers, sellers and loaners (banks, insurance, funds…).
* Social contracts and rules for shared real estate, such as condominiums and communities.
* Private-public partnership, such as those to protect forests or assess quality of products.
* Franchising agreement (such as those between TED Foundation and TEDx event licensees).
* Joint ventures (from co-working to buying shares of a company).
* Pedagogical signage to respect deals, such as waste management rules on a public toilet.

== '''Why do we need WikiDeal?''' ==
See [[principles]].

=== '''How does it work?''' ===
Clauses of deals are published by users under the [https://creativecommons.org/licenses/by-sa/4.0/ CC BY-SA 4.0], just like Wikipedia articles. So you can use, adapt and redistribute your models freely.

Customized services are provided by freelancers and small companies, including coaching to design a fair deal, mediation and simplified arbitration to solve conflicts, adapting models to diverse contexts and gathering new markets.

=== '''For who?''' ===
For everyone! You can freely use the models of deals for any bilateral or multilateral deals.
[[Category:Website]]

WikiDeal:Services

2023-12-17T01:52:07Z

Creativesoul4ever:

The '''Minimum Viable Product''' (MVP) is planned to provide the following wiki-managed features:

* Models of ''ready to use and customizable'' '''contracts (“deals”)''', agreements and rules of functioning.
** Each contract includes optional '''clauses''' to help make fair deals, such as adapted conditions of payment, cancellation terms, and easy authentication of signatures.
** Each clause of each contract is easy to adapt, edit, comment, explain and refer to laws and stats.
* Automated scenarios helping dealers '''select and respect each clause of their deals,''' raising awareness with ''tutorials'', ''reminders'', ''amendments'', ''alerts'', ''stats''…
* Conflict prevention and resolution between WikiDealers using '''coaching, mediation''' and '''arbitration.'''
* Fair deal '''enclosure options''' (executing, cancelling and settlement with compensation or transfer).

== '''Which deals are we talking about?''' ==
First, ''peer-to-peer'' deals for everyday life, including:

* Services such as transportation, freelance, internship…
* Renting goods (functional economy) including hosting, vehicles, clothes…
* Buying and selling (ticketing for shows, real estate, food, machines…).
* Loans of goods without middle men (from loaning funds to books or bikes).
* Partnership (employment, pre-nuptial/marriage/divorce, co-owning goods…)
* All other types of deals humans can imagine.

Then, deals with multiple stakeholders, such as:

* Leasing including three parts: buyers, sellers and loaners (banks, insurance, funds…).
* Social contracts and rules for shared real estate, such as condominiums and communities.
* Private-public partnership, such as those to protect forests or assess quality of products.
* Franchising agreement (such as those between TED Foundation and TEDx event licensees).
* Joint ventures (from co-working to buying shares of a company).
* Pedagogical signage to respect deals, such as waste management rules on a public toilet.

== '''Why do we need WikiDeal?''' ==
See [[principles]].

=== '''How does it work?''' ===
Clauses of deals are published by users under the [https://creativecommons.org/licenses/by-sa/4.0/ CC BY-SA 4.0], just like Wikipedia articles. So you can use, adapt and redistribute your models freely.

Customized services are provided by freelancers and small companies, including coaching to design a fair deal, mediation and simplified arbitration to solve conflicts, adapting models to diverse contexts and gathering new markets.

=== '''For who?''' ===
For everyone! You can freely use the models of deals for any bilateral or multilateral deals.
[[Category:Website]]

WikiDeal:Principles

2023-12-17T01:43:22Z

Creativesoul4ever:

Most of WikiDeal’s principles are based on:

* '''[[wikimedia:Policy:Terms_of_Use/en|Wikimedia Foundation Terms of Use]] and related governance rules on edition conflict, portals management, etc.'''
* '''[https://www.debian.org/social_contract Debian Social Contract] for licensing and developer’s governance.'''
* '''[https://taler.net/en/principles.html GNU Taler] principles for privacy, easy usability & competition.'''
* [https://e2c.how/ Exit To Community] (E2C), ownership transitions from founders to community.
* [https://www.ripess.org/quest-ce-que-less-2/?lang=en Social Solidarity Economy principles] (SSE), such as those from [https://www.ripess.org/?lang=en RIPESS].
All models of deals are licensed under the [https://creativecommons.org/licenses/by-sa/4.0/ CC BY-SA 4.0], while user’s own their personal data.

''Most users don’t care nor want to know about the details behind an online service. They know the big tech companies are a problem, but they just follow the best offers and their friends’ digital habits. We believe in a world where fair deals should be the standard, and we are building it. ''
[[Category:Website]]

WikiDeal

2023-12-01T11:01:25Z

Creativesoul4ever:

Welcome to WikiDeal!

KICK-OFF : this mediawiki was initially designed in November 2023 by Ricardo Prudon, after 2 years of a large Research study by [http://www.theobondolfi.net Théo Bondolfi], thanks also to strategic support of his fellows & friends of the [http://www.Ynternet.org Ynternet.org] Foundation for [[wikipedia:Netizen|netizenship]] (Geneva Switzerland), specially Florence Devouard and Thanasis Priftis

ENJOY your visit in the pioneering age of this wikideal emerging community.

TIME will speak.

CONTRIBUTE : if you're passionate and experienced on wiki-based philosophy, feel free to register and contribute based on our core [[principles]].

CONTACT : say hi team@wikideal.net to scheduled a personalized or group welcome online session.

== Links ==

* [[Key Features]]
* [[Minimum Viable Product]]
* [[:Category:Website|All pages of the WikiDeal.net website]]

WikiDeal

2023-12-01T11:01:04Z

Creativesoul4ever:

Welcome to WikiDeal!

KICK-OFF : this mediawiki was initially designed in November 2023 by Ricardo Prudon, after 2 years of a large Research study by [http://www.theobondolfi.net Théo Bondolfi], thanks also to strategic support of his fellows & friends of the [http://www.Ynternet.org Ynternet.org] Foundation for [[wikipedia:Netizen|netizenship]] (Geneva Switzerland), specially Florence Devouard and Thanasis Priftis

ENJOY your visit in the pioneering age of this wikideal emerging community.

TIME will speak.

CONTRIBUTE : if you're passionate and experienced on wiki-based philosophy, feel free to register and contribute based on our core [principles].

CONTACT : say hi team@wikideal.net to scheduled a personalized or group welcome online session.

== Links ==

* [[Key Features]]
* [[Minimum Viable Product]]
* [[:Category:Website|All pages of the WikiDeal.net website]]

WikiDeal:Minimum Viable Product

2023-12-01T10:08:33Z

Creativesoul4ever: /* Key features */

== Abstract ==
WikiDeal is a collaborative platform, much like Wikipedia, aiming to revolutionize contract management. Users can access, modify, and personalize contract models and clauses for a variety of agreements. The platform emphasizes decentralized ownership, allowing users to collectively govern and contribute to its evolution.

== The software development challenge for a Minimum Viable Product (MVP) ==
The proposed project scope cannot be solely implemented on the MediaWiki platform.

While MediaWiki excels in collaborative text editing and knowledge creation, its design, geared towards openness, proves inadequate for handling electronic signatures, private data, and sensitive or confidential content. The platform lacks official support for splitting access to content on a per-page basis, making it insufficiently secure for documents of a legal nature, such as contracts. Storing personalized clauses globally in the central database would significantly escalate the requirements for the database server. It is imperative not to store personal data on the wiki, including actual values of sensitive contract variables or real contracts. The above factors render the signing workflow on the wiki side unattainable.

What we can do, however, '''is utilize MediaWiki as a repository for clauses and contract models, with an integrated interactive contract prototype builder.''' This tool should enable users to pass variables, configure options, preload predefined sections and clauses, and select additional clauses from a designated "bank." Users should also be able to adjust the ordering of these components. The system will generate a dynamic preview of the contract, incorporating the selected clauses aligned with the contract model and substituting dynamic variables with values provided. It can be printed as is on the fly. The resulting text will not be stored or edited on the wiki.

Users can then request the resulting text in an editable format. This can be achieved by programmatically facilitating wiki markup as, for example, HTML via the MediaWiki API and sending it to a separate instance application. Further processing and import format will depend on the instance application specifics. The primary role of the instance application is to work as an interface to the contract prototype builder and import the resulting text into the application, where users can freely edit and securely store the document, which is accessible only to them.

WikiDeal caters to two primary user groups: those involved in creation (contract and clause models) and those utilizing the platform for building actual contracts. Exactly like on Wikipedia (editors vs readers). It remains open since anyone can become an editor. Established workflows for content discussion, consensus achievements, legal verification, and approval will probably allow us to keep the wiki open for anonymous editing, with the appropriate spam-combatting workflow.

Due to MediaWiki software specifics, the data not to be shared, such as personalized variables, adapted drafts, actual contracts, etc., shall be stored on the external instance application side.

So, the whole project can consist of two main parts:

# '''The wiki'''. Open to the community. Focused on creating contract model collections for different deals, countries, and use cases (and in multiple languages, maybe). Allows standard contract construction and printing. Even anonymously. It is already a considerable project.
# '''The instance application'''. Self hosted, personal or shared (like within an organisation). Allows editing, storing, signing and handling personalized copies of contracts generated using the wiki. Can implement the peer-to-peer signing workflow. Not MediaWiki. Independent, no MediaWiki account is required. Can connect to different WikiDeal instances (federated, decentralized).

== Key features ==
Also see: [[Key Features]]

* '''Contract Models''': Templates for agreements open for community editing and discussion.
* '''Clauses Customization''': Users can manipulate legal clauses to ensure adaptability and compliance.
* '''Contract Creation''': Users select models, input variables, and personalize contracts, saving them in different formats.
* '''Negotiation & Signing''': Contracts go through negotiation phases with different statuses (e.g., draft, signed).
* '''Post-Deal Support''': Reminders, automated payments, and service activation/cancellation based on contract terms. With plans for a proof of concept and MVP, WikiDeal envisions a community-driven space fostering innovation in contract management. Feature nice to have on the MVP, or will be done in a second phase :
* '''Decentralization''': Contracts are stored locally for privacy; proposals for decentralized solutions for organizations and individuals are in place.

Additional features in the pipeline include personalized contract styling, external contract creation tools, and true peer-to-peer contract creation, aiming for a transformative impact on how contracts are created, managed, and executed.

== Planing ==
# Preparing and submit the MVP proposal to NLnet (done, not to be funded) NB : all key-features for the Wikideal Minimum Viable product being interdependant, they will be developed in paralel, together, following the same planing.
# '''Users Needs analysis with experts.'''
#: '''a) Design activities:''' developing basic wireframes to visualize the layout and flow of the MVP and defining user stories to outline the expected user interactions. Including meeting to design and adapt:
#:* usecase scenarios
#:* mockups
#:* workflows
#:* development rules/structure (such as metatada/ontology principles)
#: '''b) Studying the code of existing mediawiki extensions before developing''', about 10-20 extensions out of the 1'447 existing ones, such as:
#:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:Approved_Revs Approved Revs],
#:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:Cite Cite],
#:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:CommentStreams CommentStreams],
#:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:Data_Transfer Data Transfer],
#:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:Expiry Expiry],
#:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:External_Data External Data],
#:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:OAuth OAuth],
#:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:Mpdf Mpdf],
#:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:Page_Forms Page Forms],
#:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:PageOwnership PageOwnership],
#:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:PageProperties PageProperties],
#:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:ParserFunctions ParserFunctions],
#:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:PerPageLanguage PerPageLanguage],
#:* [https://www.semantic-mediawiki.org/wiki/Semantic_MediaWiki SemanticMediaWiki],
#:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:TemplateData TemplateData],
#:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:VisualEditor VisualEditor],
#:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:TemplateData TemplateData],
#:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Wikibase Wikibase] (Wikidata client),
#:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:WikiSEO WikiSEO]
#:and perhaps some others.
# '''Ontology planning:''' defining metadata scheme for clauses, contract models, and helper data objects like user manuals, guided tours, etc.
# '''Development activities:''' implementing the core features identified in the earlier stages.
# '''Testing''' individual components.
# '''Release the MVP''' to a limited audience or beta testers to collect feedback and monitor its performance in a real-world environment.
# '''Iterate Based on Feedback:''' Analyze the feedback received and make necessary improvements.
# '''Track key performance indicators (KPIs)''' to assess the success of the MVP and guide further iterations.

WikiDeal:Minimum Viable Product

2023-12-01T09:26:17Z

Creativesoul4ever: /* Key features */

== Abstract ==
WikiDeal is a collaborative platform, much like Wikipedia, aiming to revolutionize contract management. Users can access, modify, and personalize contract models and clauses for a variety of agreements. The platform emphasizes decentralized ownership, allowing users to collectively govern and contribute to its evolution.

== The software development challenge for a Minimum Viable Product (MVP) ==
The proposed project scope cannot be solely implemented on the MediaWiki platform.

While MediaWiki excels in collaborative text editing and knowledge creation, its design, geared towards openness, proves inadequate for handling electronic signatures, private data, and sensitive or confidential content. The platform lacks official support for splitting access to content on a per-page basis, making it insufficiently secure for documents of a legal nature, such as contracts. Storing personalized clauses globally in the central database would significantly escalate the requirements for the database server. It is imperative not to store personal data on the wiki, including actual values of sensitive contract variables or real contracts. The above factors render the signing workflow on the wiki side unattainable.

What we can do, however, '''is utilize MediaWiki as a repository for clauses and contract models, with an integrated interactive contract prototype builder.''' This tool should enable users to pass variables, configure options, preload predefined sections and clauses, and select additional clauses from a designated "bank." Users should also be able to adjust the ordering of these components. The system will generate a dynamic preview of the contract, incorporating the selected clauses aligned with the contract model and substituting dynamic variables with values provided. It can be printed as is on the fly. The resulting text will not be stored or edited on the wiki.

Users can then request the resulting text in an editable format. This can be achieved by programmatically facilitating wiki markup as, for example, HTML via the MediaWiki API and sending it to a separate instance application. Further processing and import format will depend on the instance application specifics. The primary role of the instance application is to work as an interface to the contract prototype builder and import the resulting text into the application, where users can freely edit and securely store the document, which is accessible only to them.

WikiDeal caters to two primary user groups: those involved in creation (contract and clause models) and those utilizing the platform for building actual contracts. Exactly like on Wikipedia (editors vs readers). It remains open since anyone can become an editor. Established workflows for content discussion, consensus achievements, legal verification, and approval will probably allow us to keep the wiki open for anonymous editing, with the appropriate spam-combatting workflow.

Due to MediaWiki software specifics, the data not to be shared, such as personalized variables, adapted drafts, actual contracts, etc., shall be stored on the external instance application side.

So, the whole project can consist of two main parts:

# '''The wiki'''. Open to the community. Focused on creating contract model collections for different deals, countries, and use cases (and in multiple languages, maybe). Allows standard contract construction and printing. Even anonymously. It is already a considerable project.
# '''The instance application'''. Self hosted, personal or shared (like within an organisation). Allows editing, storing, signing and handling personalized copies of contracts generated using the wiki. Can implement the peer-to-peer signing workflow. Not MediaWiki. Independent, no MediaWiki account is required. Can connect to different WikiDeal instances (federated, decentralized).

== Key features ==
Also see: [[Key Features]]

* '''Contract Models''': Templates for agreements open for community editing and discussion.
* '''Clauses Customization''': Users can manipulate legal clauses to ensure adaptability and compliance.
* '''Contract Creation''': Users select models, input variables, and personalize contracts, saving them in different formats.
* '''Negotiation & Signing''': Contracts go through negotiation phases with different statuses (e.g., draft, signed).
* '''Post-Deal Support''': Reminders, automated payments, and service activation/cancellation based on contract terms.
* '''Decentralization''': Contracts are stored locally for privacy; proposals for decentralized solutions for organizations and individuals are in place.

With plans for a proof of concept and MVP, WikiDeal envisions a community-driven space fostering innovation in contract management.

Additional features in the pipeline include personalized contract styling, external contract creation tools, and true peer-to-peer contract creation, aiming for a transformative impact on how contracts are created, managed, and executed.

== Planing ==
# Preparing and submit the MVP proposal to NLnet (done, not to be funded) NB : all key-features for the Wikideal Minimum Viable product being interdependant, they will be developed in paralel, together, following the same planing.
# '''Users Needs analysis with experts.'''
#: '''a) Design activities:''' developing basic wireframes to visualize the layout and flow of the MVP and defining user stories to outline the expected user interactions. Including meeting to design and adapt:
#:* usecase scenarios
#:* mockups
#:* workflows
#:* development rules/structure (such as metatada/ontology principles)
#: '''b) Studying the code of existing mediawiki extensions before developing''', about 10-20 extensions out of the 1'447 existing ones, such as:
#:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:Approved_Revs Approved Revs],
#:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:Cite Cite],
#:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:CommentStreams CommentStreams],
#:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:Data_Transfer Data Transfer],
#:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:Expiry Expiry],
#:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:External_Data External Data],
#:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:OAuth OAuth],
#:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:Mpdf Mpdf],
#:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:Page_Forms Page Forms],
#:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:PageOwnership PageOwnership],
#:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:PageProperties PageProperties],
#:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:ParserFunctions ParserFunctions],
#:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:PerPageLanguage PerPageLanguage],
#:* [https://www.semantic-mediawiki.org/wiki/Semantic_MediaWiki SemanticMediaWiki],
#:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:TemplateData TemplateData],
#:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:VisualEditor VisualEditor],
#:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:TemplateData TemplateData],
#:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Wikibase Wikibase] (Wikidata client),
#:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:WikiSEO WikiSEO]
#:and perhaps some others.
# '''Ontology planning:''' defining metadata scheme for clauses, contract models, and helper data objects like user manuals, guided tours, etc.
# '''Development activities:''' implementing the core features identified in the earlier stages.
# '''Testing''' individual components.
# '''Release the MVP''' to a limited audience or beta testers to collect feedback and monitor its performance in a real-world environment.
# '''Iterate Based on Feedback:''' Analyze the feedback received and make necessary improvements.
# '''Track key performance indicators (KPIs)''' to assess the success of the MVP and guide further iterations.

WikiDeal:Minimum Viable Product

2023-12-01T09:02:51Z

Creativesoul4ever: /* Rough time estimates (for MVP development) */

== Abstract ==
WikiDeal is a collaborative platform, much like Wikipedia, aiming to revolutionize contract management. Users can access, modify, and personalize contract models and clauses for a variety of agreements. The platform emphasizes decentralized ownership, allowing users to collectively govern and contribute to its evolution.

== The software development challenge for a Minimum Viable Product (MVP) ==
The proposed project scope cannot be solely implemented on the MediaWiki platform.

While MediaWiki excels in collaborative text editing and knowledge creation, its design, geared towards openness, proves inadequate for handling electronic signatures, private data, and sensitive or confidential content. The platform lacks official support for splitting access to content on a per-page basis, making it insufficiently secure for documents of a legal nature, such as contracts. Storing personalized clauses globally in the central database would significantly escalate the requirements for the database server. It is imperative not to store personal data on the wiki, including actual values of sensitive contract variables or real contracts. The above factors render the signing workflow on the wiki side unattainable.

What we can do, however, '''is utilize MediaWiki as a repository for clauses and contract models, with an integrated interactive contract prototype builder.''' This tool should enable users to pass variables, configure options, preload predefined sections and clauses, and select additional clauses from a designated "bank." Users should also be able to adjust the ordering of these components. The system will generate a dynamic preview of the contract, incorporating the selected clauses aligned with the contract model and substituting dynamic variables with values provided. It can be printed as is on the fly. The resulting text will not be stored or edited on the wiki.

Users can then request the resulting text in an editable format. This can be achieved by programmatically facilitating wiki markup as, for example, HTML via the MediaWiki API and sending it to a separate instance application. Further processing and import format will depend on the instance application specifics. The primary role of the instance application is to work as an interface to the contract prototype builder and import the resulting text into the application, where users can freely edit and securely store the document, which is accessible only to them.

WikiDeal caters to two primary user groups: those involved in creation (contract and clause models) and those utilizing the platform for building actual contracts. Exactly like on Wikipedia (editors vs readers). It remains open since anyone can become an editor. Established workflows for content discussion, consensus achievements, legal verification, and approval will probably allow us to keep the wiki open for anonymous editing, with the appropriate spam-combatting workflow.

Due to MediaWiki software specifics, the data not to be shared, such as personalized variables, adapted drafts, actual contracts, etc., shall be stored on the external instance application side.

So, the whole project can consist of two main parts:

# '''The wiki'''. Open to the community. Focused on creating contract model collections for different deals, countries, and use cases (and in multiple languages, maybe). Allows standard contract construction and printing. Even anonymously. It is already a considerable project.
# '''The instance application'''. Self hosted, personal or shared (like within an organisation). Allows editing, storing, signing and handling personalized copies of contracts generated using the wiki. Can implement the peer-to-peer signing workflow. Not MediaWiki. Independent, no MediaWiki account is required. Can connect to different WikiDeal instances (federated, decentralized).

== Key features ==
Also see: [[Key Features]]

* '''Contract Models''': Templates for agreements open for community editing and discussion.
* '''Clauses Customization''': Users can manipulate legal clauses to ensure adaptability and compliance.
* '''Contract Creation''': Users select models, input variables, and personalize contracts, saving them in different formats.
* '''Negotiation & Signing''': Contracts go through negotiation phases with different statuses (e.g., draft, signed).
* '''Post-Deal Support''': Reminders, automated payments, and service activation/cancellation based on contract terms.
* '''Decentralization''': Contracts are stored locally for privacy; proposals for decentralized solutions for organizations and individuals are in place.

With plans for a proof of concept and MVP, WikiDeal envisions a community-driven space fostering innovation in contract management.

Additional features in the pipeline include personalized contract styling, external contract creation tools, and true peer-to-peer contract creation, aiming for a transformative impact on how contracts are created, managed, and executed.

== Planing ==
# Preparing and submit the MVP proposal to NLnet (done, not to be funded) INTRODUCTION : all key-features for the Wikideal Minimum Viable product being interdependant, they will be developed in paralel, together, following the same planing.
# '''Users Needs analysis with experts.'''
#: '''a) Design activities:''' developing basic wireframes to visualize the layout and flow of the MVP and defining user stories to outline the expected user interactions. Including meeting to design and adapt:
#:* usecase scenarios
#:* mockups
#:* workflows
#:* development rules/structure (such as metatada/ontology principles)
#: '''b) Studying the code of existing mediawiki extensions before developing''', about 10-20 extensions out of the 1'447 existing ones, such as:
#:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:Approved_Revs Approved Revs],
#:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:Cite Cite],
#:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:CommentStreams CommentStreams],
#:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:Data_Transfer Data Transfer],
#:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:Expiry Expiry],
#:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:External_Data External Data],
#:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:OAuth OAuth],
#:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:Mpdf Mpdf],
#:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:Page_Forms Page Forms],
#:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:PageOwnership PageOwnership],
#:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:PageProperties PageProperties],
#:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:ParserFunctions ParserFunctions],
#:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:PerPageLanguage PerPageLanguage],
#:* [https://www.semantic-mediawiki.org/wiki/Semantic_MediaWiki SemanticMediaWiki],
#:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:TemplateData TemplateData],
#:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:VisualEditor VisualEditor],
#:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:TemplateData TemplateData],
#:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Wikibase Wikibase] (Wikidata client),
#:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:WikiSEO WikiSEO]
#:and perhaps some others.
# '''Ontology planning:''' defining metadata scheme for clauses, contract models, and helper data objects like user manuals, guided tours, etc.
# '''Development activities:''' implementing the core features identified in the earlier stages.
# '''Testing''' individual components.
# '''Release the MVP''' to a limited audience or beta testers to collect feedback and monitor its performance in a real-world environment.
# '''Iterate Based on Feedback:''' Analyze the feedback received and make necessary improvements.
# '''Track key performance indicators (KPIs)''' to assess the success of the MVP and guide further iterations.

WikiDeal:Minimum Viable Product

2023-12-01T05:53:23Z

Creativesoul4ever:

== Abstract ==
WikiDeal is a collaborative platform, much like Wikipedia, aiming to revolutionize contract management. Users can access, modify, and personalize contract models and clauses for a variety of agreements. The platform emphasizes decentralized ownership, allowing users to collectively govern and contribute to its evolution.

== The software development challenge for a Minimum Viable Product (MVP) ==
The proposed project scope cannot be solely implemented on the MediaWiki platform.

While MediaWiki excels in collaborative text editing and knowledge creation, its design, geared towards openness, proves inadequate for handling electronic signatures, private data, and sensitive or confidential content. The platform lacks official support for splitting access to content on a per-page basis, making it insufficiently secure for documents of a legal nature, such as contracts. Storing personalized clauses globally in the central database would significantly escalate the requirements for the database server. It is imperative not to store personal data on the wiki, including actual values of sensitive contract variables or real contracts. The above factors render the signing workflow on the wiki side unattainable.

What we can do, however, '''is utilize MediaWiki as a repository for clauses and contract models, with an integrated interactive contract prototype builder.''' This tool should enable users to pass variables, configure options, preload predefined sections and clauses, and select additional clauses from a designated "bank." Users should also be able to adjust the ordering of these components. The system will generate a dynamic preview of the contract, incorporating the selected clauses aligned with the contract model and substituting dynamic variables with values provided. It can be printed as is on the fly. The resulting text will not be stored or edited on the wiki.

Users can then request the resulting text in an editable format. This can be achieved by programmatically facilitating wiki markup as, for example, HTML via the MediaWiki API and sending it to a separate instance application. Further processing and import format will depend on the instance application specifics. The primary role of the instance application is to work as an interface to the contract prototype builder and import the resulting text into the application, where users can freely edit and securely store the document, which is accessible only to them.

WikiDeal caters to two primary user groups: those involved in creation (contract and clause models) and those utilizing the platform for building actual contracts. Exactly like on Wikipedia (editors vs readers). It remains open since anyone can become an editor. Established workflows for content discussion, consensus achievements, legal verification, and approval will probably allow us to keep the wiki open for anonymous editing, with the appropriate spam-combatting workflow.

Due to MediaWiki software specifics, the data not to be shared, such as personalized variables, adapted drafts, actual contracts, etc., shall be stored on the external instance application side.

So, the whole project can consist of two main parts:

# '''The wiki'''. Open to the community. Focused on creating contract model collections for different deals, countries, and use cases (and in multiple languages, maybe). Allows standard contract construction and printing. Even anonymously. It is already a considerable project.
# '''The instance application'''. Self hosted, personal or shared (like within an organisation). Allows editing, storing, signing and handling personalized copies of contracts generated using the wiki. Can implement the peer-to-peer signing workflow. Not MediaWiki. Independent, no MediaWiki account is required. Can connect to different WikiDeal instances (federated, decentralized).

== Key features ==
Also see: [[Key Features]]

* '''Contract Models''': Templates for agreements open for community editing and discussion.
* '''Clauses Customization''': Users can manipulate legal clauses to ensure adaptability and compliance.
* '''Contract Creation''': Users select models, input variables, and personalize contracts, saving them in different formats.
* '''Negotiation & Signing''': Contracts go through negotiation phases with different statuses (e.g., draft, signed).
* '''Post-Deal Support''': Reminders, automated payments, and service activation/cancellation based on contract terms.
* '''Decentralization''': Contracts are stored locally for privacy; proposals for decentralized solutions for organizations and individuals are in place.

With plans for a proof of concept and MVP, WikiDeal envisions a community-driven space fostering innovation in contract management.

Additional features in the pipeline include personalized contract styling, external contract creation tools, and true peer-to-peer contract creation, aiming for a transformative impact on how contracts are created, managed, and executed.

== Planing ==
# Preparing and submit the MVP proposal to NLnet (done, not to be funded) INTRODUCTION : all key-features for the Wikideal Minimum Viable product being interdependant, they will be developed in paralel, together, following the same planing.
# '''Users Needs analysis with experts.'''
#: '''a) Design activities:''' developing basic wireframes to visualize the layout and flow of the MVP and defining user stories to outline the expected user interactions. Including meeting to design and adapt:
#:* usecase scenarios
#:* mockups
#:* workflows
#:* development rules/structure (such as metatada/ontology principles)
#: '''b) Studying the code of existing mediawiki extensions before developing''', about 10-20 extensions out of the 1'447 existing ones, such as:
#:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:Approved_Revs Approved Revs],
#:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:Cite Cite],
#:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:CommentStreams CommentStreams],
#:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:Data_Transfer Data Transfer],
#:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:Expiry Expiry],
#:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:External_Data External Data],
#:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:OAuth OAuth],
#:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:Mpdf Mpdf],
#:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:Page_Forms Page Forms],
#:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:PageOwnership PageOwnership],
#:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:PageProperties PageProperties],
#:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:ParserFunctions ParserFunctions],
#:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:PerPageLanguage PerPageLanguage],
#:* [https://www.semantic-mediawiki.org/wiki/Semantic_MediaWiki SemanticMediaWiki],
#:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:TemplateData TemplateData],
#:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:VisualEditor VisualEditor],
#:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:TemplateData TemplateData],
#:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Wikibase Wikibase] (Wikidata client),
#:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:WikiSEO WikiSEO]
#:and perhaps some others.
# '''Ontology planning:''' defining metadata scheme for clauses, contract models, and helper data objects like user manuals, guided tours, etc.
# '''Development activities:''' implementing the core features identified in the earlier stages.
# '''Testing''' individual components.
# '''Release the MVP''' to a limited audience or beta testers to collect feedback and monitor its performance in a real-world environment.
# '''Iterate Based on Feedback:''' Analyze the feedback received and make necessary improvements.
# '''Track key performance indicators (KPIs)''' to assess the success of the MVP and guide further iterations.

== Rough time estimates (for MVP development) ==
Estimated time required for experienced developers proficient in PHP and JavaScript to use MediaWiki and develop MediaWiki extensions.

==== Customization of contract templates and clauses (MediaWiki) ====
PHP & MediaWiki extension development: approximately 120-140 hours.

JavaScript for frontend: estimated 80-100 hours.

==== Basic contract creation (MediaWiki) ====
PHP & MediaWiki extension development: approximately 120-140 hours.

JavaScript for frontend: estimated 80-100 hours.

==== Advanced contract creation & Post-Deal support (instance application) ====
Development: estimated at 140-160 hours.

==== Negotiation & Signing (instance application) ====
Development: approximately 160-180 hours.

=== Totals ===
''These estimates are subject to variation based on the familiarity with developing MediaWiki extensions, specific requirements that are to be decided, and other factors.''

Total estimated: 700-820 hours (includes hours of coaching, coordination, and documentation)

WikiDeal:Minimum Viable Product

2023-12-01T03:46:43Z

Creativesoul4ever: /* Planing */

== Abstract ==
WikiDeal is a collaborative platform, much like Wikipedia, aiming to revolutionize contract management. Users can access, modify, and personalize contract models and clauses for a variety of agreements. The platform emphasizes decentralized ownership, allowing users to collectively govern and contribute to its evolution.

== The software development challenge for a Minimum Viable Product (MVP) ==
The proposed project scope cannot be solely implemented on the MediaWiki platform.

While MediaWiki excels in collaborative text editing and knowledge creation, its design, geared towards openness, proves inadequate for handling electronic signatures, private data, and sensitive or confidential content. The platform lacks official support for splitting access to content on a per-page basis, making it insufficiently secure for documents of a legal nature, such as contracts. Storing personalized clauses globally in the central database would significantly escalate the requirements for the database server. It is imperative not to store personal data on the wiki, including actual values of sensitive contract variables or real contracts. The above factors render the signing workflow on the wiki side unattainable.

What we can do, however, '''is utilize MediaWiki as a repository for clauses and contract models, with an integrated interactive contract prototype builder.''' This tool should enable users to pass variables, configure options, preload predefined sections and clauses, and select additional clauses from a designated "bank." Users should also be able to adjust the ordering of these components. The system will generate a dynamic preview of the contract, incorporating the selected clauses aligned with the contract model and substituting dynamic variables with values provided. It can be printed as is on the fly. The resulting text will not be stored or edited on the wiki.

Users can then request the resulting text in an editable format. This can be achieved by programmatically facilitating wiki markup as, for example, HTML via the MediaWiki API and sending it to a separate instance application. Further processing and import format will depend on the instance application specifics. The primary role of the instance application is to work as an interface to the contract prototype builder and import the resulting text into the application, where users can freely edit and securely store the document, which is accessible only to them.

WikiDeal caters to two primary user groups: those involved in creation (contract and clause models) and those utilizing the platform for building actual contracts. Exactly like on Wikipedia (editors vs readers). It remains open since anyone can become an editor. Established workflows for content discussion, consensus achievements, legal verification, and approval will probably allow us to keep the wiki open for anonymous editing, with the appropriate spam-combatting workflow.

Due to MediaWiki software specifics, the data not to be shared, such as personalized variables, adapted drafts, actual contracts, etc., shall be stored on the external instance application side.

So, the whole project can consist of two main parts:

# '''The wiki'''. Open to the community. Focused on creating contract model collections for different deals, countries, and use cases (and in multiple languages, maybe). Allows standard contract construction and printing. Even anonymously. It is already a considerable project.
# '''The instance application'''. Self hosted, personal or shared (like within an organisation). Allows editing, storing, signing and handling personalized copies of contracts generated using the wiki. Can implement the peer-to-peer signing workflow. Not MediaWiki. Independent, no MediaWiki account is required. Can connect to different WikiDeal instances (federated, decentralized).

== Key features ==
Also see: [[Key Features]]

* '''Contract Models''': Templates for agreements open for community editing and discussion.
* '''Clauses Customization''': Users can manipulate legal clauses to ensure adaptability and compliance.
* '''Contract Creation''': Users select models, input variables, and personalize contracts, saving them in different formats.
* '''Negotiation & Signing''': Contracts go through negotiation phases with different statuses (e.g., draft, signed).
* '''Post-Deal Support''': Reminders, automated payments, and service activation/cancellation based on contract terms.
* '''Decentralization''': Contracts are stored locally for privacy; proposals for decentralized solutions for organizations and individuals are in place.

With plans for a proof of concept and MVP, WikiDeal envisions a community-driven space fostering innovation in contract management.

Additional features in the pipeline include personalized contract styling, external contract creation tools, and true peer-to-peer contract creation, aiming for a transformative impact on how contracts are created, managed, and executed.

== Planing ==

INTRODUCTION : all key-features for the Wikideal Minimum Viable product being interdependant, they will be developed in paralel, together, following the same planing.

# '''Users Needs analysis with experts.'''
#: '''a) Design activities:''' developing basic wireframes to visualize the layout and flow of the MVP and defining user stories to outline the expected user interactions. Including meeting to design and adapt:
#:* usecase scenarios
#:* mockups
#:* workflows
#:* development rules/structure (such as metatada/ontology principles)
#: '''b) Studying the code of existing mediawiki extensions before developing''', about 10-20 extensions out of the 1'447 existing ones, such as:
#:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:Approved_Revs Approved Revs],
#:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:Cite Cite],
#:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:CommentStreams CommentStreams],
#:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:Data_Transfer Data Transfer],
#:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:Expiry Expiry],
#:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:External_Data External Data],
#:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:OAuth OAuth],
#:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:Mpdf Mpdf],
#:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:Page_Forms Page Forms],
#:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:PageOwnership PageOwnership],
#:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:PageProperties PageProperties],
#:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:ParserFunctions ParserFunctions],
#:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:PerPageLanguage PerPageLanguage],
#:* [https://www.semantic-mediawiki.org/wiki/Semantic_MediaWiki SemanticMediaWiki],
#:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:TemplateData TemplateData],
#:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:VisualEditor VisualEditor],
#:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:TemplateData TemplateData],
#:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Wikibase Wikibase] (Wikidata client),
#:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:WikiSEO WikiSEO]
#:and perhaps some others.
# '''Ontology planning:''' defining metadata scheme for clauses and contract models used by the interactive contract builder, data exchange, and the user workflows automation. Our effort will be aimed at providing a detailed breakdown of the yet rough data objects, to make them usable so by humans as by machines:
#:; Contract Model
#:* Metadata
#::* Options
#::* Variables
#:* Outline
#::* Sections
#:::* Metadata
#:::* Predefined Clauses (ordered)
#:::* Available Clauses (dynamic)
#:; Clause
#:* Metadata
#::* Options
#::* Variables
#::* Contract metadata
#:* Text
#:; Interactive contract builder
#:* Contract model
#::* Options
#::* Variables
#:* Outline
#::* Predefined Sections
#:::* Predefined Clauses (ordered)
#:::* Available Clauses (dynamic)
#::* Custom Sections
#:::* Metadata
#:::* Available Clauses (dynamic) Smaller ontologies will be needed for helper data objects like user manuals, guided tours, etc
# '''Development activities:''' implementing the core features specified in the earlier stages.
# '''Testing''' '''& documenting''' individual components and their integration.
# '''Release the MVP''' to a limited audience or beta testers to collect feedback and monitor its performance in a real-world environment. Including presenting the wikideal beta MVP to an event such as wikimania or FOSS event and inviting beta users to test and give feedbacks.
# '''Iterate based on feedbacks:''' Analyze the feedback received and make necessary improvements.
# '''Track key performance indicators (KPIs)''' to assess the success of the MVP and guide further iterations.

WikiDeal

2023-12-01T03:38:41Z

Creativesoul4ever:

Welcome to WikiDeal!

KICK-OFF : this mediawiki was initially designed in November 2023 by Ricardo Prudon, after 2 years of a large Research study by [http://www.theobondolfi.net Théo Bondolfi], thanks also to strategic support of his fellows & friends of the [http://www.Ynternet.org Ynternet.org] Foundation for [[wikipedia:Netizen|netizenship]] (Geneva Switzerland), specially Florence Devouard and Thanasis Priftis

ENJOY your visit in the pioneering age of this wikideal emerging community.

TIME will speak.

CONTRIBUTE : if you're passionate and experienced on wiki-based philosophy, feel free to register and contribute based on our core <nowiki>[[principles]]</nowiki>.

CONTACT : say hi team@wikideal.net to scheduled a personalized or group welcome online session.

== Links ==

* [[Key Features]]
* [[Minimum Viable Product]]
* [[:Category:Website|All pages of the WikiDeal.net website]]

WikiDeal

2023-12-01T03:12:28Z

Creativesoul4ever:

Welcome to WikiDeal!

KICK-OFF : this mediawiki was initially designed in November 2023 by Ricardo Prudon, after 2 years of a specific Research study by Théo Bondolfi, thanks also to strategic support of his fellows & friends of the [http://www.Ynternet.org Ynternet.org] Foundation for [[wikipedia:Netizen|netizenship]] (Geneva Switzerland)

ENJOY your visit in the pioneering age of this wikideal emerging community.

TIME will speak.

CONTRIBUTE : if you're passionate and experienced on wiki-based philosophy, feel free to register and contribute based on our core <nowiki>[[principles]]</nowiki>.

CONTACT : say hi team@wikideal.net to scheduled a personalized or group welcome online session.

== Links ==

* [[Key Features]]
* [[Minimum Viable Product]]
* [[:Category:Website|All pages of the WikiDeal.net website]]

WikiDeal

2023-12-01T03:07:51Z

Creativesoul4ever: inserted some basic guidance for newcomers and a call to action

Welcome to WikiDeal!

KICK-OFF : This mediawiki was installed in November 2023.

ENJOY your visit in the pioneering age of this wikideal emerging community.

TIME will speak.

CONTRIBUTE : if you're passionate and experienced on wiki-based philosophy, feel free to register and contribute based on our core <nowiki>[[principles]]</nowiki>.

CONTACT : say hi team@wikideal.net to scheduled a personalized or group welcome online session.

== Links ==

* [[Key Features]]
* [[Minimum Viable Product]]
* [[:Category:Website|All pages of the WikiDeal.net website]]

WikiDeal:Development

2023-12-01T02:50:32Z

Creativesoul4ever: added smart contracts and AI

In 2024, WikiDeal is launching the vision and gathering contributions to make it happen: operational developers (tech/legal/markets), a steering committee, donors & investors.

WIkiDeal plans to facilitate the participative development of the following services:

# Technology : a '''Minimum Viable Product (MVP)''' based on [[mediawikiwiki:MediaWiki|MediaWiki]], see on wikideal mediawiki [[Minimum Viable Product|key features for a Minimum Viable Product]] (MVP)
# Policies : fundamental rules and legal issues, adapted from [[wikimedia:Policy:Terms_of_Use/en|Wikimedia Foundation Terms of Use]] and related principles.
# Legal : Models of legal contracts helping you create deals. First ossible examples of deals validated by lawyers (proofs of concept) :
## ''Grant management'' deal models to monitor donations & subventions for NGOs.
## Guidelines for creation and management of local ''Simplified Chamber of Arbitration for small causes,'' resolving conflicts between wikidealers.
# Market : first communities of practices adopting the tool (such as decentralized bike rental system, cohousing rules of functioning), law student adopting wikideal as special project for remote intership
# A bounding curve machine to manage initial loans/investments boosting wikideal markets and portals to be efficiently structured and developed.
# Tech & market support : AI bot supporting volunteers helping newcomers integrate in wikideal ecosystem (customer support).
# Technology & market : ethereum-based Smart contract for a wikideal portal services providers (legal, market, technologies)
# And many more, depending on your ideas and the incubators team (steering committee) ...

[[Category:Website]]

WikiDeal:Copyrights

2023-12-01T02:41:45Z

Creativesoul4ever:

The following copyrights policies are applied :

Content : using CC-BY-SA licence

User's private data (name, address, private data inside contracts) : owned exclusively by each user, independently from wikideal platform.

Original Wikideal idea/concept : Théo Bondolfi, inspired by Florence Devouard on Wikimedia Governance and by Richard M. Stallman on free software philosophy and his GNUPedia initial vision.

Wikideal Trademark & domain name : owned by Théo Bondolfi, to be transferred to the community of users (using the e2c.how model where users "buy back" the company to it's founder-s) as soon as a first set of formal contracts are launch.

Auditing (irrelevant in this copyright page, but useful to give a global vision of the fair wikideal governance under construction) : www.ynternet.org foundation members for global governance, and its independent accounting auditing organ (in 20023 : fiduciaire Fidassist SA), under surveillance of Swiss Federal authority.

Also see : [[principles]]

WikiDeal:Copyrights

2023-12-01T02:40:24Z

Creativesoul4ever:

WikiDeal:Copyrights

2023-12-01T02:39:49Z

Creativesoul4ever:

The following copyrights policies are applied :

Content : using CC-BY-SA licence

User's private data (name, address, private data inside contracts) : owned exclusively by each user, independently from wikideal platform.

Original Wikideal idea/concept : Théo Bondolfi, inspired by Florence Devouard on Wikimedia Governance and by Richard M. Stallman on free software philosophy and his GNUPedia initial vision.

Wikideal Trademark & domain name : owned by Théo Bondolfi, to be transferred to the community of users (using the e2c.how model where users "buy back" the company to it's founder-s) as soon as a first set of formal contracts are launch.

Auditing (irrelevant in this copyright page, but useful to give a global vision of the fair wikideal governance under construction) : www.ynternet.org foundation members for and its independent accounting auditing organ (in 20023 : fiduciaire Fidassist SA), under surveillance of Swiss Federal authority.

WikiDeal:Copyrights

2023-12-01T02:19:46Z

Creativesoul4ever: frst draft

The following copyrights policies are applied :

Content : using CC-BY-SA
User's private data : owned exclusively by each user, independently from wikideal platform

Original idea : Théo Bondolfi, inspired by Florence Devouard for Wikideal Governance and by Richard M. Stallman for ethics of the digital architecture

Trademark : owned by Théo Bondolfi, to be transferred to the community of users (using the e2c.how model) as soon as a first set of formal contracts are agreed between regarding copyright

WikiDeal:Development

2023-12-01T02:14:41Z

Creativesoul4ever:

In 2024, WikiDeal is launching the vision and gathering contributions to make it happen: operational developers (tech/legal/markets), a steering committee, donors & investors.

WIkiDeal plans to facilitate the participative development of the following services:

# Technology : a '''Minimum Viable Product (MVP)''' based on [[mediawikiwiki:MediaWiki|MediaWiki]], see on wikideal mediawiki [[Minimum Viable Product|key features for a Minimum Viable Product]] (MVP)
# Policies : fundamental rules and legal issues, adapted from [[wikimedia:Policy:Terms_of_Use/en|Wikimedia Foundation Terms of Use]] and related principles.
# Legal : Models of legal contracts helping you create deals. First ossible examples of deals validated by lawyers (proofs of concept) :
## ''Grant management'' deal models to monitor donations & subventions for NGOs.
## Guidelines for creation and management of local ''Simplified Chamber of Arbitration for small causes,'' resolving conflicts between wikidealers.
# Market : first communities of practices adopting the tool (such as decentralized bike rental system, cohousing rules of functioning), law student adopting wikideal as special project for remote intership
# A bounding curve machine to manage initial loans/investments for wikideal test market to be rapidly penetrated
# And many more depending on your ideas and the incubators team (steering committee) ...

[[Category:Website]]

WikiDeal:Development

2023-12-01T02:01:21Z

Creativesoul4ever:

WikiDeal:Minimum Viable Product

2023-12-01T01:16:51Z

Creativesoul4ever: /* Rough time estimates (for MVP development) */ deleted, to avoid fork, since we well reformulate it in a table

== Abstract ==
WikiDeal is a collaborative platform, much like Wikipedia, aiming to revolutionize contract management. Users can access, modify, and personalize contract models and clauses for a variety of agreements. The platform emphasizes decentralized ownership, allowing users to collectively govern and contribute to its evolution.

== The software development challenge for a Minimum Viable Product (MVP) ==
The proposed project scope cannot be solely implemented on the MediaWiki platform.

While MediaWiki excels in collaborative text editing and knowledge creation, its design, geared towards openness, proves inadequate for handling electronic signatures, private data, and sensitive or confidential content. The platform lacks official support for splitting access to content on a per-page basis, making it insufficiently secure for documents of a legal nature, such as contracts. Storing personalized clauses globally in the central database would significantly escalate the requirements for the database server. It is imperative not to store personal data on the wiki, including actual values of sensitive contract variables or real contracts. The above factors render the signing workflow on the wiki side unattainable.

What we can do, however, '''is utilize MediaWiki as a repository for clauses and contract models, with an integrated interactive contract prototype builder.''' This tool should enable users to pass variables, configure options, preload predefined sections and clauses, and select additional clauses from a designated "bank." Users should also be able to adjust the ordering of these components. The system will generate a dynamic preview of the contract, incorporating the selected clauses aligned with the contract model and substituting dynamic variables with values provided. It can be printed as is on the fly. The resulting text will not be stored or edited on the wiki.

Users can then request the resulting text in an editable format. This can be achieved by programmatically facilitating wiki markup as, for example, HTML via the MediaWiki API and sending it to a separate instance application. Further processing and import format will depend on the instance application specifics. The primary role of the instance application is to work as an interface to the contract prototype builder and import the resulting text into the application, where users can freely edit and securely store the document, which is accessible only to them.

WikiDeal caters to two primary user groups: those involved in creation (contract and clause models) and those utilizing the platform for building actual contracts. Exactly like on Wikipedia (editors vs readers). It remains open since anyone can become an editor. Established workflows for content discussion, consensus achievements, legal verification, and approval will probably allow us to keep the wiki open for anonymous editing, with the appropriate spam-combatting workflow.

Due to MediaWiki software specifics, the data not to be shared, such as personalized variables, adapted drafts, actual contracts, etc., shall be stored on the external instance application side.

So, the whole project can consist of two main parts:

# '''The wiki'''. Open to the community. Focused on creating contract model collections for different deals, countries, and use cases (and in multiple languages, maybe). Allows standard contract construction and printing. Even anonymously. It is already a considerable project.
# '''The instance application'''. Self hosted, personal or shared (like within an organisation). Allows editing, storing, signing and handling personalized copies of contracts generated using the wiki. Can implement the peer-to-peer signing workflow. Not MediaWiki. Independent, no MediaWiki account is required. Can connect to different WikiDeal instances (federated, decentralized).

== Key features ==
Also see: [[Key Features]]

* '''Contract Models''': Templates for agreements open for community editing and discussion.
* '''Clauses Customization''': Users can manipulate legal clauses to ensure adaptability and compliance.
* '''Contract Creation''': Users select models, input variables, and personalize contracts, saving them in different formats.
* '''Negotiation & Signing''': Contracts go through negotiation phases with different statuses (e.g., draft, signed).
* '''Post-Deal Support''': Reminders, automated payments, and service activation/cancellation based on contract terms.
* '''Decentralization''': Contracts are stored locally for privacy; proposals for decentralized solutions for organizations and individuals are in place.

With plans for a proof of concept and MVP, WikiDeal envisions a community-driven space fostering innovation in contract management.

Additional features in the pipeline include personalized contract styling, external contract creation tools, and true peer-to-peer contract creation, aiming for a transformative impact on how contracts are created, managed, and executed.

== Planing ==

INTRODUCTION : all key-features for the Wikideal Minimum Viable product being interdependant, they will be developed in paralel, together, following the same planing.

# '''Users Needs analysis with experts.'''
#: '''a) Design activities:''' developing basic wireframes to visualize the layout and flow of the MVP and defining user stories to outline the expected user interactions. Including meeting to design and adapt:
#:* usecase scenarios
#:* mockups
#:* workflows
#:* development rules/structure (such as metatada/ontology principles)
#: '''b) Studying the code of existing mediawiki extensions before developing''', about 10-20 extensions out of the 1'447 existing ones, such as:
#:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:Approved_Revs Approved Revs],
#:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:Cite Cite],
#:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:CommentStreams CommentStreams],
#:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:Data_Transfer Data Transfer],
#:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:Expiry Expiry],
#:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:External_Data External Data],
#:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:OAuth OAuth],
#:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:Mpdf Mpdf],
#:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:Page_Forms Page Forms],
#:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:PageOwnership PageOwnership],
#:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:PageProperties PageProperties],
#:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:ParserFunctions ParserFunctions],
#:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:PerPageLanguage PerPageLanguage],
#:* [https://www.semantic-mediawiki.org/wiki/Semantic_MediaWiki SemanticMediaWiki],
#:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:TemplateData TemplateData],
#:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:VisualEditor VisualEditor],
#:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:TemplateData TemplateData],
#:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Wikibase Wikibase] (Wikidata client),
#:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:WikiSEO WikiSEO]
#:and perhaps some others.
# '''Ontology planning:''' defining metadata scheme for clauses and contract models used by the interactive contract builder, data exchange, and the user workflows automation. Our effort will be aimed at providing a detailed breakdown of the yet rough data objects, to make them usable so by humans as by machines:
#:; Contract Model
#:* Metadata
#::* Options
#::* Variables
#:* Outline
#::* Sections
#:::* Metadata
#:::* Predefined Clauses (ordered)
#:::* Available Clauses (dynamic)
#:; Clause
#:* Metadata
#::* Options
#::* Variables
#::* Contract metadata
#:* Text
#:; Interactive contract builder
#:* Contract model
#::* Options
#::* Variables
#:* Outline
#::* Predefined Sections
#:::* Predefined Clauses (ordered)
#:::* Available Clauses (dynamic)
#::* Custom Sections
#:::* Metadata
#:::* Available Clauses (dynamic) Smaller ontologies will be needed for helper data objects like user manuals, guided tours, etc
# '''Development activities:''' implementing the core features identified in the earlier stages.
# '''Testing''' individual components.
# '''Release the MVP''' to a limited audience or beta testers to collect feedback and monitor its performance in a real-world environment.
# '''Iterate Based on Feedback:''' Analyze the feedback received and make necessary improvements.
# '''Track key performance indicators (KPIs)''' to assess the success of the MVP and guide further iterations.

WikiDeal:Key Features

2023-12-01T00:32:00Z

Creativesoul4ever:

'''WikiDeal in a nutshell? The Wikipedia of deals.'''

WikiDeal is a community & platform providing models of contracts to sell, rent, employ, share...

Like on Wikipedia, you can freely access, edit and adapt these contracts, for any context and needs. Each model is connected to a community of users, providing comments and feedback.

'''Who owns WikiDeal? It's a common owned by its users.'''

Users can contribute in developing the platform’s technology, legal support and new marketplaces. Coaching to design and adapt deals, mediation & arbitration for fair compensation…

'''How is it governed?'''

WikiDeal gathers the highest standards on ethics, privacy, customer support, free licensing, low costs and high efficiency, inspired by the Wikipedia participative governance.

'''WIKIDEAL SERVICES (USECASES)'''

The '''Minimum Viable Product''' (MVP) is planned to provide the following wiki-managed features:

* Models of ''ready to use and customizable'' '''contracts (“deals”)''', agreements and rules of functioning.
** Each contract includes optional '''clauses''' to help make fair deals, such as adapted conditions of payment, simplified arbitration for conflicts and easy authentication of signatures.
** Each clause of each contract is easy to adapt, '''edit''', comment, explain and refer to laws and stats.
* Automated scenarios helping dealers '''select and respect each clause of their deals,''' raising awareness with ''tutorials'', ''reminders'', ''amendments'', ''alerts'', stats, ''use cases and terms of interpretation'' …
* Conflict prevention and resolution between WikiDealers using '''coaching, mediation''' and '''arbitration.'''
* Anonymized big data for '''risk management, including ''incentives'' & ''compensation'' tools''' such as benchmarks on pricing and fines, reputation and karma management, social and ecological impact.
* Fair deal '''enclosure options''' (executing, canceling & resiliating with compensations, transfer).

'''Which deals are we talking about?'''

First, ''peer-to-peer'' deals for everyday life, including:

* Services such as transportation, freelance, internship…
* Renting goods (functional economy) including hosting, vehicles, clothes…
* Buying and selling (ticketing for shows, real estate, food, machines…).
* Loans of goods without middle men (from loaning funds to books or bikes).
* Partnership (employment, pre-nuptial/marriage/divorce, co-owning goods…)
* Most types of deals humans can imagine and need to agree upon.

Then, deals with multiple stakeholders, such as:

* Leasing including three parts: buyers, sellers and loaners (banks, insurance, funds…).
* Social contracts and rules for shared real estate, such as condominiums and communities.
* Private-public partnership, such as those to protect forests or assess quality of products.
* Franchising agreement (such as those between TED Foundation and TEDx event licensees).
* Joint ventures (from co-working to buying shares of a company).
* Pedagogical signage to respect deals, such as waste management rules on a public toilet.

== Components ==

=== Contract models ===
Contract models are predefined models (or templates) of contracts for various agreements or deals. Contract models are provided, edited and discussed by the community just like Wikipedia articles, to make sure the best possible contract model is always provided for a specific purpose.

A contract model is simply comprised of a document title and collection of appropriate clauses that defines the agreement.

A contract model may also contain notes, warnings or other to be decided optional fields that will help users when using the contract model to generate real contracts.

To be decided:

* Architectural implementation of contract models.

=== Clauses ===
A contract model will mostly be just a collection of legal clauses, conditions or provisions. Clauses will be blocks of text that can contain variables. An example of a clause would look like:

“<nowiki>{{ signatory }}</nowiki> agrees to pay <nowiki>{{ offerer }}</nowiki> the amount of <nowiki>{{ fee }}</nowiki> before the <nowiki>{{ day }}</nowiki> of the month for the period <nowiki>{{ start_date }}</nowiki> until <nowiki>{{ end_date }}</nowiki>”

Clauses could have meta information assigned to them based on community feedback. Examples include things like “popularity” or “legal expert verified”. It could also include references or citations to various types of laws that the clause adheres to.

If a clause is verified by a legal expert it should of course not be directly editable, because it will have to reverified after each edit. This means that instead of editing a clause it will create a new clause, keeping the original. The new clause will then become an optional suggestion for creating a contract.

To be decided:

* Should clauses contain the information on which models they belong to (i.e. using [https://www.semantic-mediawiki.org/wiki/Semantic_MediaWiki Semantic MediaWiki])? Or should the contract models contain this information?

=== Creating a contract ===
Using the contract models and clauses users would be able to generate customized contracts for their own purposes.

Envisioned workflow:

# Select an existing contract model.
# Input all the variables that the contract model requires and additional details such as a preamble.
# Fill in all the conditions of the contracts, which decides which clauses will be included in the contract.
# [Optional] Edit the clauses of the contract. This may consist of:
#* Removing clauses.
#* Reordering clauses.
#* Replacing clauses with different clauses in the database of approved alternative clauses.
#* Adding custom clauses.
# Save the contract (for example as PDF) and send it to the stakeholders of this contract.

=== Signing contracts ===
Once a contract has been created and sent to its stakeholders it will have to be signed to conclude a deal.

The signing phase of a contract should ideally not only be a “sign” or “decline” button. In this phase there should also be the possibility for all parties involved to discuss and negotiate on the contract.

In this phase a contract could have statuses, such as:

* Draft
* Conflict
* Being discussed
* Signed
* Denied
* Closed

When this stage is done successfully a deal has been made.

=== Post deal ===
When the deal has been made WikiDeal could provider additional features that make the execution of the deal easier. Examples of features in this stage could include, but are not limited to:

* If a contract contains dates or deadlines WikiDeal could send reminders to the parties involved. This would also apply to monthly repeating clauses.
* If a contract contains a monetary transaction WikiDeal could provide payment links that already includes the monetary amounts as stated within the contract.
* If a contract is related to a service it could be programmatically linked to automatic activation/cancellation of said service when signed.

=== Decentralization ===
Because contracts contain private information they should not be stored on the main centralized main WikiDeal server. Creating a contract on the site should only allow the user to save the contract to their local computer, but not on the main WikiDeal server.

Contracts might temporarily be saved on the WikiDeal server during the Minimum Viable Product stage of development for convenience.

Instead ideally we would develop an external tool to generate contracts using the centralized community driven data of WikiDeal, but without storing any personal data. This will make users fully in charge of their own personal data while still using the crowd-sourced data that WikiDeal provides.

For organizations using WikiDeal we envision a decentralized system where the organization hosts their own WikiDeal instance. The organization instance will use the data provided by WikiDeal for contract models and clauses, but it will store all personal data of its organization only on their own WikiDeal instance.

For contracts between individuals we envision a decentralized system using instances (similar to the fediverse or email). This allows users to be in control of their data by either signing up to an instance that they trust or choosing to host their own.

Alternatively we could also consider some sort of fully peer to peer approach to making deals but details of this have not been thought out.

== Proof of concept ==
Before making a Minimum Viable Product (MVP) it might be a good idea to make a proof concept first.

The proof of concept will likely just include:

* Contract models.
* Clauses.
* Creating contracts (very basic implementation).

This is to focus on establishing WikiDeal as a really useful public repository for clauses and contract models and so we can see if the envisioned architecture we end up choosing works as expected.

A proof of concept will give us a good place to interature further upon and this also gives us more time to work out the details of what a MVP should contain.

== Minimum Viable Product ==
See: [[Minimum Viable Product]]

== Outdated feature matrix information that might be used for future reference: ==
{| class="wikitable"
|'''Contract Models'''
|Prio
|Hours
|-
|Base model type which can contain a collection of clauses
|1
|
|-
|Conditional clauses and options to customize the clauses
|2
|
|-
|Notes and help texts
|3
|
|-
|'''Clauses'''
|
|
|-
|Base clause type
|1
|
|-
|Clause variables
|1
|
|-
|Citations in clauses
|2
|
|-
|Statistics (maturity, references, etc.)
|2
|
|-
|Notes and help texts
|3
|
|-
|'''Creating a contract'''
|
|
|-
|Entering basic variables (names, date, preamble, etc.)
|1
|
|-
|Enabling conditional clauses
|2
|
|-
|Visual contract editor
|1
|
|-
|Save as PDF or other formats
|2
|
|-
|Send to stakeholders
|3
|
|-
|Annex and attachments to contracts
|3
|
|-
|'''Signing contracts'''
|
|
|-
|Basic signing of contracts
|1
|
|-
|Discussion and negotiation
|2
|
|-
|Various states (draft, conflict, denied, signed, etc.)
|1
|
|-
|'''Post deal'''
|
|
|-
|Sending reminders
|2
|
|-
|Automation API
|3
|
|}

=== Additional features (likely not in MVP) ===
{| class="wikitable"
|'''Creating a contract'''
|Hours
|-
|Personalized contract styling (typography, etc.)
|
|-
|'''Decentralization'''
|
|-
|External contract creation tool (desktop or phone app)
|
|-
|Self hosted instances (with federation)
|
|-
|True peer to peer contract creation
|
|-
|'''Funding'''
|
|-
|Bounding curve software
|
|}

WikiDeal:Key Features

2023-12-01T00:31:20Z

Creativesoul4ever:

'''WikiDeal in a nutshell? The Wikipedia of deals.'''

WikiDeal is a community & platform providing models of contracts to sell, rent, employ, share...

Like on Wikipedia, you can freely access, edit and adapt these contracts, for any context and needs. Each model is connected to a community of users, providing comments and feedback.

'''Who owns WikiDeal? It's a common owned by its users.'''

Users can contribute in developing the platform’s technology, legal support and new marketplaces. Coaching to design and adapt deals, mediation & arbitration for fair compensation…

'''How is it governed?'''

WikiDeal gathers the highest standards on ethics, privacy, customer support, free licensing, low costs and high efficiency, inspired by the Wikipedia participative governance.

'''WIKIDEAL SERVICES (USECASES)'''

The '''Minimum Viable Product''' (MVP) is planned to provide the following wiki-managed features:

* Models of ''ready to use and customizable'' '''contracts (“deals”)''', agreements and rules of functioning.
** Each contract includes optional '''clauses''' to help make fair deals, such as adapted conditions of payment, simplified arbitration for conflicts and easy authentication of signatures.
** Each clause of each contract is easy to adapt, '''edit''', comment, explain and refer to laws and stats.
* Automated scenarios helping dealers '''select and respect each clause of their deals,''' raising awareness with ''tutorials'', ''reminders'', ''amendments'', ''alerts'', stats, ''use cases and modalities of interpretation'' …
* Conflict prevention and resolution between WikiDealers using '''coaching, mediation''' and '''arbitration.'''
* Anonymized big data for '''risk management, including ''incentives'' & ''compensation'' tools''' such as benchmarks on pricing and fines, reputation and karma management, social and ecological impact.
* Fair deal '''enclosure options''' (executing, canceling & resiliating with compensations, transfer).

'''Which deals are we talking about?'''

First, ''peer-to-peer'' deals for everyday life, including:

* Services such as transportation, freelance, internship…
* Renting goods (functional economy) including hosting, vehicles, clothes…
* Buying and selling (ticketing for shows, real estate, food, machines…).
* Loans of goods without middle men (from loaning funds to books or bikes).
* Partnership (employment, pre-nuptial/marriage/divorce, co-owning goods…)
* Most types of deals humans can imagine and need to agree upon.

Then, deals with multiple stakeholders, such as:

* Leasing including three parts: buyers, sellers and loaners (banks, insurance, funds…).
* Social contracts and rules for shared real estate, such as condominiums and communities.
* Private-public partnership, such as those to protect forests or assess quality of products.
* Franchising agreement (such as those between TED Foundation and TEDx event licensees).
* Joint ventures (from co-working to buying shares of a company).
* Pedagogical signage to respect deals, such as waste management rules on a public toilet.

== Components ==

=== Contract models ===
Contract models are predefined models (or templates) of contracts for various agreements or deals. Contract models are provided, edited and discussed by the community just like Wikipedia articles, to make sure the best possible contract model is always provided for a specific purpose.

A contract model is simply comprised of a document title and collection of appropriate clauses that defines the agreement.

A contract model may also contain notes, warnings or other to be decided optional fields that will help users when using the contract model to generate real contracts.

To be decided:

* Architectural implementation of contract models.

=== Clauses ===
A contract model will mostly be just a collection of legal clauses, conditions or provisions. Clauses will be blocks of text that can contain variables. An example of a clause would look like:

“<nowiki>{{ signatory }}</nowiki> agrees to pay <nowiki>{{ offerer }}</nowiki> the amount of <nowiki>{{ fee }}</nowiki> before the <nowiki>{{ day }}</nowiki> of the month for the period <nowiki>{{ start_date }}</nowiki> until <nowiki>{{ end_date }}</nowiki>”

Clauses could have meta information assigned to them based on community feedback. Examples include things like “popularity” or “legal expert verified”. It could also include references or citations to various types of laws that the clause adheres to.

If a clause is verified by a legal expert it should of course not be directly editable, because it will have to reverified after each edit. This means that instead of editing a clause it will create a new clause, keeping the original. The new clause will then become an optional suggestion for creating a contract.

To be decided:

* Should clauses contain the information on which models they belong to (i.e. using [https://www.semantic-mediawiki.org/wiki/Semantic_MediaWiki Semantic MediaWiki])? Or should the contract models contain this information?

=== Creating a contract ===
Using the contract models and clauses users would be able to generate customized contracts for their own purposes.

Envisioned workflow:

# Select an existing contract model.
# Input all the variables that the contract model requires and additional details such as a preamble.
# Fill in all the conditions of the contracts, which decides which clauses will be included in the contract.
# [Optional] Edit the clauses of the contract. This may consist of:
#* Removing clauses.
#* Reordering clauses.
#* Replacing clauses with different clauses in the database of approved alternative clauses.
#* Adding custom clauses.
# Save the contract (for example as PDF) and send it to the stakeholders of this contract.

=== Signing contracts ===
Once a contract has been created and sent to its stakeholders it will have to be signed to conclude a deal.

The signing phase of a contract should ideally not only be a “sign” or “decline” button. In this phase there should also be the possibility for all parties involved to discuss and negotiate on the contract.

In this phase a contract could have statuses, such as:

* Draft
* Conflict
* Being discussed
* Signed
* Denied
* Closed

When this stage is done successfully a deal has been made.

=== Post deal ===
When the deal has been made WikiDeal could provider additional features that make the execution of the deal easier. Examples of features in this stage could include, but are not limited to:

* If a contract contains dates or deadlines WikiDeal could send reminders to the parties involved. This would also apply to monthly repeating clauses.
* If a contract contains a monetary transaction WikiDeal could provide payment links that already includes the monetary amounts as stated within the contract.
* If a contract is related to a service it could be programmatically linked to automatic activation/cancellation of said service when signed.

=== Decentralization ===
Because contracts contain private information they should not be stored on the main centralized main WikiDeal server. Creating a contract on the site should only allow the user to save the contract to their local computer, but not on the main WikiDeal server.

Contracts might temporarily be saved on the WikiDeal server during the Minimum Viable Product stage of development for convenience.

Instead ideally we would develop an external tool to generate contracts using the centralized community driven data of WikiDeal, but without storing any personal data. This will make users fully in charge of their own personal data while still using the crowd-sourced data that WikiDeal provides.

For organizations using WikiDeal we envision a decentralized system where the organization hosts their own WikiDeal instance. The organization instance will use the data provided by WikiDeal for contract models and clauses, but it will store all personal data of its organization only on their own WikiDeal instance.

For contracts between individuals we envision a decentralized system using instances (similar to the fediverse or email). This allows users to be in control of their data by either signing up to an instance that they trust or choosing to host their own.

Alternatively we could also consider some sort of fully peer to peer approach to making deals but details of this have not been thought out.

== Proof of concept ==
Before making a Minimum Viable Product (MVP) it might be a good idea to make a proof concept first.

The proof of concept will likely just include:

* Contract models.
* Clauses.
* Creating contracts (very basic implementation).

This is to focus on establishing WikiDeal as a really useful public repository for clauses and contract models and so we can see if the envisioned architecture we end up choosing works as expected.

A proof of concept will give us a good place to interature further upon and this also gives us more time to work out the details of what a MVP should contain.

== Minimum Viable Product ==
See: [[Minimum Viable Product]]

== Outdated feature matrix information that might be used for future reference: ==
{| class="wikitable"
|'''Contract Models'''
|Prio
|Hours
|-
|Base model type which can contain a collection of clauses
|1
|
|-
|Conditional clauses and options to customize the clauses
|2
|
|-
|Notes and help texts
|3
|
|-
|'''Clauses'''
|
|
|-
|Base clause type
|1
|
|-
|Clause variables
|1
|
|-
|Citations in clauses
|2
|
|-
|Statistics (maturity, references, etc.)
|2
|
|-
|Notes and help texts
|3
|
|-
|'''Creating a contract'''
|
|
|-
|Entering basic variables (names, date, preamble, etc.)
|1
|
|-
|Enabling conditional clauses
|2
|
|-
|Visual contract editor
|1
|
|-
|Save as PDF or other formats
|2
|
|-
|Send to stakeholders
|3
|
|-
|Annex and attachments to contracts
|3
|
|-
|'''Signing contracts'''
|
|
|-
|Basic signing of contracts
|1
|
|-
|Discussion and negotiation
|2
|
|-
|Various states (draft, conflict, denied, signed, etc.)
|1
|
|-
|'''Post deal'''
|
|
|-
|Sending reminders
|2
|
|-
|Automation API
|3
|
|}

=== Additional features (likely not in MVP) ===
{| class="wikitable"
|'''Creating a contract'''
|Hours
|-
|Personalized contract styling (typography, etc.)
|
|-
|'''Decentralization'''
|
|-
|External contract creation tool (desktop or phone app)
|
|-
|Self hosted instances (with federation)
|
|-
|True peer to peer contract creation
|
|-
|'''Funding'''
|
|-
|Bounding curve software
|
|}

WikiDeal:Key Features

2023-12-01T00:27:35Z

Creativesoul4ever:

'''WikiDeal in a nutshell? The Wikipedia of deals.'''

WikiDeal is a community & platform providing models of contracts to sell, rent, employ, share...

Like on Wikipedia, you can freely access, edit and adapt these contracts, for any context and needs. Each model is connected to a community of users, providing comments and feedback.

'''Who owns WikiDeal? It's a common owned by its users.'''

Users can contribute in developing the platform’s technology, legal support and new marketplaces. Coaching to design and adapt deals, mediation & arbitration for fair compensation…

'''How is it governed?'''

WikiDeal gathers the highest standards on ethics, privacy, customer support, free licensing, low costs and high efficiency, inspired by the Wikipedia participative governance.

'''WIKIDEAL SERVICES (USECASES)'''

The '''Minimum Viable Product''' (MVP) is planned to provide the following wiki-managed features:

* Models of ''ready to use and customizable'' '''contracts (“deals”)''', agreements and rules of functioning.
** Each contract includes optional '''clauses''' to help make fair deals, such as adapted conditions of payment, simplified arbitration for conflicts and easy authentication of signatures.
** Each clause of each contract is easy to adapt, '''edit''', comment, explain and refer to laws and stats.
* Automated scenarios helping dealers '''select and respect each clause of their deals,''' raising awareness with ''tutorials'', ''reminders'', ''amendments'', ''alerts'', ''stats''…
* Conflict prevention and resolution between WikiDealers using '''coaching, mediation''' and '''arbitration.'''
* Anonymized big data for '''risk management, including ''incentives'' & ''compensation'' tools''' such as benchmarks on pricing and fines, reputation and karma management, social and ecological impact.
* Fair deal '''enclosure options''' (executing, canceling & resiliating with compensations, transfer).

'''Which deals are we talking about?'''

First, ''peer-to-peer'' deals for everyday life, including:

* Services such as transportation, freelance, internship…
* Renting goods (functional economy) including hosting, vehicles, clothes…
* Buying and selling (ticketing for shows, real estate, food, machines…).
* Loans of goods without middle men (from loaning funds to books or bikes).
* Partnership (employment, pre-nuptial/marriage/divorce, co-owning goods…)
* Most types of deals humans can imagine and need to agree upon.

Then, deals with multiple stakeholders, such as:

* Leasing including three parts: buyers, sellers and loaners (banks, insurance, funds…).
* Social contracts and rules for shared real estate, such as condominiums and communities.
* Private-public partnership, such as those to protect forests or assess quality of products.
* Franchising agreement (such as those between TED Foundation and TEDx event licensees).
* Joint ventures (from co-working to buying shares of a company).
* Pedagogical signage to respect deals, such as waste management rules on a public toilet.

== Components ==

=== Contract models ===
Contract models are predefined models (or templates) of contracts for various agreements or deals. Contract models are provided, edited and discussed by the community just like Wikipedia articles, to make sure the best possible contract model is always provided for a specific purpose.

A contract model is simply comprised of a document title and collection of appropriate clauses that defines the agreement.

A contract model may also contain notes, warnings or other to be decided optional fields that will help users when using the contract model to generate real contracts.

To be decided:

* Architectural implementation of contract models.

=== Clauses ===
A contract model will mostly be just a collection of legal clauses, conditions or provisions. Clauses will be blocks of text that can contain variables. An example of a clause would look like:

“<nowiki>{{ signatory }}</nowiki> agrees to pay <nowiki>{{ offerer }}</nowiki> the amount of <nowiki>{{ fee }}</nowiki> before the <nowiki>{{ day }}</nowiki> of the month for the period <nowiki>{{ start_date }}</nowiki> until <nowiki>{{ end_date }}</nowiki>”

Clauses could have meta information assigned to them based on community feedback. Examples include things like “popularity” or “legal expert verified”. It could also include references or citations to various types of laws that the clause adheres to.

If a clause is verified by a legal expert it should of course not be directly editable, because it will have to reverified after each edit. This means that instead of editing a clause it will create a new clause, keeping the original. The new clause will then become an optional suggestion for creating a contract.

To be decided:

* Should clauses contain the information on which models they belong to (i.e. using [https://www.semantic-mediawiki.org/wiki/Semantic_MediaWiki Semantic MediaWiki])? Or should the contract models contain this information?

=== Creating a contract ===
Using the contract models and clauses users would be able to generate customized contracts for their own purposes.

Envisioned workflow:

# Select an existing contract model.
# Input all the variables that the contract model requires and additional details such as a preamble.
# Fill in all the conditions of the contracts, which decides which clauses will be included in the contract.
# [Optional] Edit the clauses of the contract. This may consist of:
#* Removing clauses.
#* Reordering clauses.
#* Replacing clauses with different clauses in the database of approved alternative clauses.
#* Adding custom clauses.
# Save the contract (for example as PDF) and send it to the stakeholders of this contract.

=== Signing contracts ===
Once a contract has been created and sent to its stakeholders it will have to be signed to conclude a deal.

The signing phase of a contract should ideally not only be a “sign” or “decline” button. In this phase there should also be the possibility for all parties involved to discuss and negotiate on the contract.

In this phase a contract could have statuses, such as:

* Draft
* Conflict
* Being discussed
* Signed
* Denied
* Closed

When this stage is done successfully a deal has been made.

=== Post deal ===
When the deal has been made WikiDeal could provider additional features that make the execution of the deal easier. Examples of features in this stage could include, but are not limited to:

* If a contract contains dates or deadlines WikiDeal could send reminders to the parties involved. This would also apply to monthly repeating clauses.
* If a contract contains a monetary transaction WikiDeal could provide payment links that already includes the monetary amounts as stated within the contract.
* If a contract is related to a service it could be programmatically linked to automatic activation/cancellation of said service when signed.

=== Decentralization ===
Because contracts contain private information they should not be stored on the main centralized main WikiDeal server. Creating a contract on the site should only allow the user to save the contract to their local computer, but not on the main WikiDeal server.

Contracts might temporarily be saved on the WikiDeal server during the Minimum Viable Product stage of development for convenience.

Instead ideally we would develop an external tool to generate contracts using the centralized community driven data of WikiDeal, but without storing any personal data. This will make users fully in charge of their own personal data while still using the crowd-sourced data that WikiDeal provides.

For organizations using WikiDeal we envision a decentralized system where the organization hosts their own WikiDeal instance. The organization instance will use the data provided by WikiDeal for contract models and clauses, but it will store all personal data of its organization only on their own WikiDeal instance.

For contracts between individuals we envision a decentralized system using instances (similar to the fediverse or email). This allows users to be in control of their data by either signing up to an instance that they trust or choosing to host their own.

Alternatively we could also consider some sort of fully peer to peer approach to making deals but details of this have not been thought out.

== Proof of concept ==
Before making a Minimum Viable Product (MVP) it might be a good idea to make a proof concept first.

The proof of concept will likely just include:

* Contract models.
* Clauses.
* Creating contracts (very basic implementation).

This is to focus on establishing WikiDeal as a really useful public repository for clauses and contract models and so we can see if the envisioned architecture we end up choosing works as expected.

A proof of concept will give us a good place to interature further upon and this also gives us more time to work out the details of what a MVP should contain.

== Minimum Viable Product ==
See: [[Minimum Viable Product]]

== Outdated feature matrix information that might be used for future reference: ==
{| class="wikitable"
|'''Contract Models'''
|Prio
|Hours
|-
|Base model type which can contain a collection of clauses
|1
|
|-
|Conditional clauses and options to customize the clauses
|2
|
|-
|Notes and help texts
|3
|
|-
|'''Clauses'''
|
|
|-
|Base clause type
|1
|
|-
|Clause variables
|1
|
|-
|Citations in clauses
|2
|
|-
|Statistics (maturity, references, etc.)
|2
|
|-
|Notes and help texts
|3
|
|-
|'''Creating a contract'''
|
|
|-
|Entering basic variables (names, date, preamble, etc.)
|1
|
|-
|Enabling conditional clauses
|2
|
|-
|Visual contract editor
|1
|
|-
|Save as PDF or other formats
|2
|
|-
|Send to stakeholders
|3
|
|-
|Annex and attachments to contracts
|3
|
|-
|'''Signing contracts'''
|
|
|-
|Basic signing of contracts
|1
|
|-
|Discussion and negotiation
|2
|
|-
|Various states (draft, conflict, denied, signed, etc.)
|1
|
|-
|'''Post deal'''
|
|
|-
|Sending reminders
|2
|
|-
|Automation API
|3
|
|}

=== Additional features (likely not in MVP) ===
{| class="wikitable"
|'''Creating a contract'''
|Hours
|-
|Personalized contract styling (typography, etc.)
|
|-
|'''Decentralization'''
|
|-
|External contract creation tool (desktop or phone app)
|
|-
|Self hosted instances (with federation)
|
|-
|True peer to peer contract creation
|
|-
|'''Funding'''
|
|-
|Bounding curve software
|
|}

WikiDeal:Minimum Viable Product

2023-11-30T13:50:47Z

Creativesoul4ever: /* Planing */

== Abstract ==
WikiDeal is a collaborative platform, much like Wikipedia, aiming to revolutionize contract management. Users can access, modify, and personalize contract models and clauses for a variety of agreements. The platform emphasizes decentralized ownership, allowing users to collectively govern and contribute to its evolution.

== The software development challenge for a Minimum Viable Product (MVP) ==
The proposed project scope cannot be solely implemented on the MediaWiki platform.

While MediaWiki excels in collaborative text editing and knowledge creation, its design, geared towards openness, proves inadequate for handling electronic signatures, private data, and sensitive or confidential content. The platform lacks official support for splitting access to content on a per-page basis, making it insufficiently secure for documents of a legal nature, such as contracts. Storing personalized clauses globally in the central database would significantly escalate the requirements for the database server. It is imperative not to store personal data on the wiki, including actual values of sensitive contract variables or real contracts. The above factors render the signing workflow on the wiki side unattainable.

What we can do, however, '''is utilize MediaWiki as a repository for clauses and contract models, with an integrated interactive contract prototype builder.''' This tool should enable users to pass variables, configure options, preload predefined sections and clauses, and select additional clauses from a designated "bank." Users should also be able to adjust the ordering of these components. The system will generate a dynamic preview of the contract, incorporating the selected clauses aligned with the contract model and substituting dynamic variables with values provided. It can be printed as is on the fly. The resulting text will not be stored or edited on the wiki.

Users can then request the resulting text in an editable format. This can be achieved by programmatically facilitating wiki markup as, for example, HTML via the MediaWiki API and sending it to a separate instance application. Further processing and import format will depend on the instance application specifics. The primary role of the instance application is to work as an interface to the contract prototype builder and import the resulting text into the application, where users can freely edit and securely store the document, which is accessible only to them.

WikiDeal caters to two primary user groups: those involved in creation (contract and clause models) and those utilizing the platform for building actual contracts. Exactly like on Wikipedia (editors vs readers). It remains open since anyone can become an editor. Established workflows for content discussion, consensus achievements, legal verification, and approval will probably allow us to keep the wiki open for anonymous editing, with the appropriate spam-combatting workflow.

Due to MediaWiki software specifics, the data not to be shared, such as personalized variables, adapted drafts, actual contracts, etc., shall be stored on the external instance application side.

So, the whole project can consist of two main parts:

# '''The wiki'''. Open to the community. Focused on creating contract model collections for different deals, countries, and use cases (and in multiple languages, maybe). Allows standard contract construction and printing. Even anonymously. It is already a considerable project.
# '''The instance application'''. Self hosted, personal or shared (like within an organisation). Allows editing, storing, signing and handling personalized copies of contracts generated using the wiki. Can implement the peer-to-peer signing workflow. Not MediaWiki. Independent, no MediaWiki account is required. Can connect to different WikiDeal instances (federated, decentralized).

== Key features ==
Also see: [[Key Features]]

* '''Contract Models''': Templates for agreements open for community editing and discussion.
* '''Clauses Customization''': Users can manipulate legal clauses to ensure adaptability and compliance.
* '''Contract Creation''': Users select models, input variables, and personalize contracts, saving them in different formats.
* '''Negotiation & Signing''': Contracts go through negotiation phases with different statuses (e.g., draft, signed).
* '''Post-Deal Support''': Reminders, automated payments, and service activation/cancellation based on contract terms.
* '''Decentralization''': Contracts are stored locally for privacy; proposals for decentralized solutions for organizations and individuals are in place.

With plans for a proof of concept and MVP, WikiDeal envisions a community-driven space fostering innovation in contract management.

Additional features in the pipeline include personalized contract styling, external contract creation tools, and true peer-to-peer contract creation, aiming for a transformative impact on how contracts are created, managed, and executed.

== Planing ==

INTRODUCTION : all key-features for the Wikideal Minimum Viable product being interdependant, they will be developed in paralel, together, following the same planing.

# '''Users Needs analysis with experts.'''
#: '''a) Design activities:''' developing basic wireframes to visualize the layout and flow of the MVP and defining user stories to outline the expected user interactions. Including meeting to design and adapt:
#:* usecase scenarios
#:* mockups
#:* workflows
#:* development rules/structure (such as metatada/ontology principles)
#: '''b) Studying the code of existing mediawiki extensions before developing''', about 10-20 extensions out of the 1'447 existing ones, such as:
#:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:Approved_Revs Approved Revs],
#:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:Cite Cite],
#:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:CommentStreams CommentStreams],
#:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:Data_Transfer Data Transfer],
#:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:Expiry Expiry],
#:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:External_Data External Data],
#:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:OAuth OAuth],
#:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:Mpdf Mpdf],
#:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:Page_Forms Page Forms],
#:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:PageOwnership PageOwnership],
#:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:PageProperties PageProperties],
#:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:ParserFunctions ParserFunctions],
#:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:PerPageLanguage PerPageLanguage],
#:* [https://www.semantic-mediawiki.org/wiki/Semantic_MediaWiki SemanticMediaWiki],
#:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:TemplateData TemplateData],
#:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:VisualEditor VisualEditor],
#:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:TemplateData TemplateData],
#:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Wikibase Wikibase] (Wikidata client),
#:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:WikiSEO WikiSEO]
#:and perhaps some others.
# '''Ontology planning:''' defining metadata scheme for clauses and contract models used by the interactive contract builder, data exchange, and the user workflows automation. Our effort will be aimed at providing a detailed breakdown of the yet rough data objects, to make them usable so by humans as by machines:
#:; Contract Model
#:* Metadata
#::* Options
#::* Variables
#:* Outline
#::* Sections
#:::* Metadata
#:::* Predefined Clauses (ordered)
#:::* Available Clauses (dynamic)
#:; Clause
#:* Metadata
#::* Options
#::* Variables
#::* Contract metadata
#:* Text
#:; Interactive contract builder
#:* Contract model
#::* Options
#::* Variables
#:* Outline
#::* Predefined Sections
#:::* Predefined Clauses (ordered)
#:::* Available Clauses (dynamic)
#::* Custom Sections
#:::* Metadata
#:::* Available Clauses (dynamic)
#:Smaller ontologies will be needed for helper data objects like user manuals, guided tours, etc
# '''Development activities:''' implementing the core features identified in the earlier stages.
# '''Testing''' individual components.
# '''Release the MVP''' to a limited audience or beta testers to collect feedback and monitor its performance in a real-world environment.
# '''Iterate Based on Feedback:''' Analyze the feedback received and make necessary improvements.
# '''Track key performance indicators (KPIs)''' to assess the success of the MVP and guide further iterations.

== Rough time estimates (for MVP development) ==
Estimated time required for experienced developers proficient in PHP and JavaScript to use MediaWiki and develop MediaWiki extensions.

==== Customization of contract templates and clauses (MediaWiki) ====
PHP & MediaWiki extension development: approximately 120-140 hours.

JavaScript for frontend: estimated 80-100 hours.

==== Basic contract creation (MediaWiki) ====
PHP & MediaWiki extension development: approximately 120-140 hours.

JavaScript for frontend: estimated 80-100 hours.

==== Advanced contract creation & Post-Deal support (instance application) ====
Development: estimated at 140-160 hours.

==== Negotiation & Signing (instance application) ====
Development: approximately 160-180 hours.

=== Totals ===
''These estimates are subject to variation based on the familiarity with developing MediaWiki extensions, specific requirements that are to be decided, and other factors.''

Total estimated: 700-820 hours (includes hours of coaching, coordination, and documentation)

WikiDeal:Minimum Viable Product

2023-11-30T13:50:01Z

Creativesoul4ever: /* Planing */

== Abstract ==
WikiDeal is a collaborative platform, much like Wikipedia, aiming to revolutionize contract management. Users can access, modify, and personalize contract models and clauses for a variety of agreements. The platform emphasizes decentralized ownership, allowing users to collectively govern and contribute to its evolution.

== The software development challenge for a Minimum Viable Product (MVP) ==
The proposed project scope cannot be solely implemented on the MediaWiki platform.

While MediaWiki excels in collaborative text editing and knowledge creation, its design, geared towards openness, proves inadequate for handling electronic signatures, private data, and sensitive or confidential content. The platform lacks official support for splitting access to content on a per-page basis, making it insufficiently secure for documents of a legal nature, such as contracts. Storing personalized clauses globally in the central database would significantly escalate the requirements for the database server. It is imperative not to store personal data on the wiki, including actual values of sensitive contract variables or real contracts. The above factors render the signing workflow on the wiki side unattainable.

What we can do, however, '''is utilize MediaWiki as a repository for clauses and contract models, with an integrated interactive contract prototype builder.''' This tool should enable users to pass variables, configure options, preload predefined sections and clauses, and select additional clauses from a designated "bank." Users should also be able to adjust the ordering of these components. The system will generate a dynamic preview of the contract, incorporating the selected clauses aligned with the contract model and substituting dynamic variables with values provided. It can be printed as is on the fly. The resulting text will not be stored or edited on the wiki.

Users can then request the resulting text in an editable format. This can be achieved by programmatically facilitating wiki markup as, for example, HTML via the MediaWiki API and sending it to a separate instance application. Further processing and import format will depend on the instance application specifics. The primary role of the instance application is to work as an interface to the contract prototype builder and import the resulting text into the application, where users can freely edit and securely store the document, which is accessible only to them.

WikiDeal caters to two primary user groups: those involved in creation (contract and clause models) and those utilizing the platform for building actual contracts. Exactly like on Wikipedia (editors vs readers). It remains open since anyone can become an editor. Established workflows for content discussion, consensus achievements, legal verification, and approval will probably allow us to keep the wiki open for anonymous editing, with the appropriate spam-combatting workflow.

Due to MediaWiki software specifics, the data not to be shared, such as personalized variables, adapted drafts, actual contracts, etc., shall be stored on the external instance application side.

So, the whole project can consist of two main parts:

# '''The wiki'''. Open to the community. Focused on creating contract model collections for different deals, countries, and use cases (and in multiple languages, maybe). Allows standard contract construction and printing. Even anonymously. It is already a considerable project.
# '''The instance application'''. Self hosted, personal or shared (like within an organisation). Allows editing, storing, signing and handling personalized copies of contracts generated using the wiki. Can implement the peer-to-peer signing workflow. Not MediaWiki. Independent, no MediaWiki account is required. Can connect to different WikiDeal instances (federated, decentralized).

== Key features ==
Also see: [[Key Features]]

* '''Contract Models''': Templates for agreements open for community editing and discussion.
* '''Clauses Customization''': Users can manipulate legal clauses to ensure adaptability and compliance.
* '''Contract Creation''': Users select models, input variables, and personalize contracts, saving them in different formats.
* '''Negotiation & Signing''': Contracts go through negotiation phases with different statuses (e.g., draft, signed).
* '''Post-Deal Support''': Reminders, automated payments, and service activation/cancellation based on contract terms.
* '''Decentralization''': Contracts are stored locally for privacy; proposals for decentralized solutions for organizations and individuals are in place.

With plans for a proof of concept and MVP, WikiDeal envisions a community-driven space fostering innovation in contract management.

Additional features in the pipeline include personalized contract styling, external contract creation tools, and true peer-to-peer contract creation, aiming for a transformative impact on how contracts are created, managed, and executed.

== Planing ==
# INTRODUCTION : all key-features for the Wikideal Minimum Viable product being interdependant, they will be developed in paralel, together, following the same planing.
# '''Users Needs analysis with experts.'''
#: '''a) Design activities:''' developing basic wireframes to visualize the layout and flow of the MVP and defining user stories to outline the expected user interactions. Including meeting to design and adapt:
#:* usecase scenarios
#:* mockups
#:* workflows
#:* development rules/structure (such as metatada/ontology principles)
#: '''b) Studying the code of existing mediawiki extensions before developing''', about 10-20 extensions out of the 1'447 existing ones, such as:
#:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:Approved_Revs Approved Revs],
#:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:Cite Cite],
#:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:CommentStreams CommentStreams],
#:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:Data_Transfer Data Transfer],
#:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:Expiry Expiry],
#:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:External_Data External Data],
#:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:OAuth OAuth],
#:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:Mpdf Mpdf],
#:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:Page_Forms Page Forms],
#:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:PageOwnership PageOwnership],
#:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:PageProperties PageProperties],
#:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:ParserFunctions ParserFunctions],
#:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:PerPageLanguage PerPageLanguage],
#:* [https://www.semantic-mediawiki.org/wiki/Semantic_MediaWiki SemanticMediaWiki],
#:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:TemplateData TemplateData],
#:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:VisualEditor VisualEditor],
#:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:TemplateData TemplateData],
#:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Wikibase Wikibase] (Wikidata client),
#:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:WikiSEO WikiSEO]
#:and perhaps some others.
# '''Ontology planning:''' defining metadata scheme for clauses and contract models used by the interactive contract builder, data exchange, and the user workflows automation. Our effort will be aimed at providing a detailed breakdown of the yet rough data objects, to make them usable so by humans as by machines:
#:; Contract Model
#:* Metadata
#::* Options
#::* Variables
#:* Outline
#::* Sections
#:::* Metadata
#:::* Predefined Clauses (ordered)
#:::* Available Clauses (dynamic)
#:; Clause
#:* Metadata
#::* Options
#::* Variables
#::* Contract metadata
#:* Text
#:; Interactive contract builder
#:* Contract model
#::* Options
#::* Variables
#:* Outline
#::* Predefined Sections
#:::* Predefined Clauses (ordered)
#:::* Available Clauses (dynamic)
#::* Custom Sections
#:::* Metadata
#:::* Available Clauses (dynamic)
#:Smaller ontologies will be needed for helper data objects like user manuals, guided tours, etc
# '''Development activities:''' implementing the core features identified in the earlier stages.
# '''Testing''' individual components.
# '''Release the MVP''' to a limited audience or beta testers to collect feedback and monitor its performance in a real-world environment.
# '''Iterate Based on Feedback:''' Analyze the feedback received and make necessary improvements.
# '''Track key performance indicators (KPIs)''' to assess the success of the MVP and guide further iterations.

== Rough time estimates (for MVP development) ==
Estimated time required for experienced developers proficient in PHP and JavaScript to use MediaWiki and develop MediaWiki extensions.

==== Customization of contract templates and clauses (MediaWiki) ====
PHP & MediaWiki extension development: approximately 120-140 hours.

JavaScript for frontend: estimated 80-100 hours.

==== Basic contract creation (MediaWiki) ====
PHP & MediaWiki extension development: approximately 120-140 hours.

JavaScript for frontend: estimated 80-100 hours.

==== Advanced contract creation & Post-Deal support (instance application) ====
Development: estimated at 140-160 hours.

==== Negotiation & Signing (instance application) ====
Development: approximately 160-180 hours.

=== Totals ===
''These estimates are subject to variation based on the familiarity with developing MediaWiki extensions, specific requirements that are to be decided, and other factors.''

Total estimated: 700-820 hours (includes hours of coaching, coordination, and documentation)

WikiDeal:Minimum Viable Product

2023-11-29T15:07:57Z

Creativesoul4ever: /* Planing */

== Abstract ==
WikiDeal is a collaborative platform, much like Wikipedia, aiming to revolutionize contract management. Users can access, modify, and personalize contract models and clauses for a variety of agreements. The platform emphasizes decentralized ownership, allowing users to collectively govern and contribute to its evolution.

== The software development challenge for a Minimum Viable Product (MVP) ==
The proposed project scope cannot be solely implemented on the MediaWiki platform.

While MediaWiki excels in collaborative text editing and knowledge creation, its design, geared towards openness, proves inadequate for handling electronic signatures, private data, and sensitive or confidential content. The platform lacks official support for splitting access to content on a per-page basis, making it insufficiently secure for documents of a legal nature, such as contracts. Storing personalized clauses globally in the central database would significantly escalate the requirements for the database server. It is imperative not to store personal data on the wiki, including actual values of sensitive contract variables or real contracts. The above factors render the signing workflow on the wiki side unattainable.

What we can do, however, '''is utilize MediaWiki as a repository for clauses and contract models, with an integrated interactive contract prototype builder.''' This tool should enable users to pass variables, configure options, preload predefined sections and clauses, and select additional clauses from a designated "bank." Users should also be able to adjust the ordering of these components. The system will generate a dynamic preview of the contract, incorporating the selected clauses aligned with the contract model and substituting dynamic variables with values provided. It can be printed as is on the fly. The resulting text will not be stored or edited on the wiki.

Users can then request the resulting text in an editable format. This can be achieved by programmatically facilitating wiki markup as, for example, HTML via the MediaWiki API and sending it to a separate instance application. Further processing and import format will depend on the instance application specifics. The primary role of the instance application is to work as an interface to the contract prototype builder and import the resulting text into the application, where users can freely edit and securely store the document, which is accessible only to them.

WikiDeal caters to two primary user groups: those involved in creation (contract and clause models) and those utilizing the platform for building actual contracts. Exactly like on Wikipedia (editors vs readers). It remains open since anyone can become an editor. Established workflows for content discussion, consensus achievements, legal verification, and approval will probably allow us to keep the wiki open for anonymous editing, with the appropriate spam-combatting workflow.

Due to MediaWiki software specifics, the data not to be shared, such as personalized variables, adapted drafts, actual contracts, etc., shall be stored on the external instance application side.

So, the whole project can consist of two main parts:

# '''The wiki'''. Open to the community. Focused on creating contract model collections for different deals, countries, and use cases (and in multiple languages, maybe). Allows standard contract construction and printing. Even anonymously. It is already a considerable project.
# '''The instance application'''. Self hosted, personal or shared (like within an organisation). Allows editing, storing, signing and handling personalized copies of contracts generated using the wiki. Can implement the peer-to-peer signing workflow. Not MediaWiki. Independent, no MediaWiki account is required. Can connect to different WikiDeal instances (federated, decentralized).

== Key features ==
Also see: [[Key Features]]

* '''Contract Models''': Templates for agreements open for community editing and discussion.
* '''Clauses Customization''': Users can manipulate legal clauses to ensure adaptability and compliance.
* '''Contract Creation''': Users select models, input variables, and personalize contracts, saving them in different formats.
* '''Negotiation & Signing''': Contracts go through negotiation phases with different statuses (e.g., draft, signed).
* '''Post-Deal Support''': Reminders, automated payments, and service activation/cancellation based on contract terms.
* '''Decentralization''': Contracts are stored locally for privacy; proposals for decentralized solutions for organizations and individuals are in place.

With plans for a proof of concept and MVP, WikiDeal envisions a community-driven space fostering innovation in contract management.

Additional features in the pipeline include personalized contract styling, external contract creation tools, and true peer-to-peer contract creation, aiming for a transformative impact on how contracts are created, managed, and executed.

== Planing ==
# INTRODUCTION : all key-features for the Wikideal Minimum Viable product being interdependant, they will be developed in paralel, together, following the same planing.
# '''Users Needs analysis with experts.'''
#: '''a) Design activities:''' developing basic wireframes to visualize the layout and flow of the MVP and defining user stories to outline the expected user interactions. Including meeting to design and adapt:
#:* usecase scenarios
#:* mockups
#:* workflows
#:* development rules/structure (such as metatada/ontology principles)
#: '''b) Studying the code of existing mediawiki extensions before developing''', about 10-20 extensions out of the 1'447 existing ones, such as:
#:* PageForms,
#:* SemanticMediaWiki,
#:* Cite,
#:* Wikibase (Wikidata client),
#:and perhaps some others.
# '''Ontology planning:''' defining metadata scheme for clauses, contract models, and helper data objects like user manuals, guided tours, etc.
# '''Development activities:''' implementing the core features identified in the earlier stages.
# '''Testing''' individual components.
# '''Release the MVP''' to a limited audience or beta testers to collect feedback and monitor its performance in a real-world environment.
# '''Iterate Based on Feedback:''' Analyze the feedback received and make necessary improvements.
# '''Track key performance indicators (KPIs)''' to assess the success of the MVP and guide further iterations.

== Rough time estimates (for MVP development) ==
Estimated time required for experienced developers proficient in PHP and JavaScript to use MediaWiki and develop MediaWiki extensions.

==== Customization of contract templates and clauses (MediaWiki) ====
PHP & MediaWiki extension development: approximately 120-140 hours.

JavaScript for frontend: estimated 80-100 hours.

==== Basic contract creation (MediaWiki) ====
PHP & MediaWiki extension development: approximately 120-140 hours.

JavaScript for frontend: estimated 80-100 hours.

==== Advanced contract creation & Post-Deal support (instance application) ====
Development: estimated at 140-160 hours.

==== Negotiation & Signing (instance application) ====
Development: approximately 160-180 hours.

=== Totals ===
''These estimates are subject to variation based on the familiarity with developing MediaWiki extensions, specific requirements that are to be decided, and other factors.''

Total estimated: 700-820 hours (includes hours of coaching, coordination, and documentation)

WikiDeal:Minimum Viable Product

2023-11-29T14:52:38Z

Creativesoul4ever: /* Planing */

== Abstract ==
WikiDeal is a collaborative platform, much like Wikipedia, aiming to revolutionize contract management. Users can access, modify, and personalize contract models and clauses for a variety of agreements. The platform emphasizes decentralized ownership, allowing users to collectively govern and contribute to its evolution.

== The software development challenge for a Minimum Viable Product (MVP) ==
The proposed project scope cannot be solely implemented on the MediaWiki platform.

While MediaWiki excels in collaborative text editing and knowledge creation, its design, geared towards openness, proves inadequate for handling electronic signatures, private data, and sensitive or confidential content. The platform lacks official support for splitting access to content on a per-page basis, making it insufficiently secure for documents of a legal nature, such as contracts. Storing personalized clauses globally in the central database would significantly escalate the requirements for the database server. It is imperative not to store personal data on the wiki, including actual values of sensitive contract variables or real contracts. The above factors render the signing workflow on the wiki side unattainable.

What we can do, however, '''is utilize MediaWiki as a repository for clauses and contract models, with an integrated interactive contract prototype builder.''' This tool should enable users to pass variables, configure options, preload predefined sections and clauses, and select additional clauses from a designated "bank." Users should also be able to adjust the ordering of these components. The system will generate a dynamic preview of the contract, incorporating the selected clauses aligned with the contract model and substituting dynamic variables with values provided. It can be printed as is on the fly. The resulting text will not be stored or edited on the wiki.

Users can then request the resulting text in an editable format. This can be achieved by programmatically facilitating wiki markup as, for example, HTML via the MediaWiki API and sending it to a separate instance application. Further processing and import format will depend on the instance application specifics. The primary role of the instance application is to work as an interface to the contract prototype builder and import the resulting text into the application, where users can freely edit and securely store the document, which is accessible only to them.

WikiDeal caters to two primary user groups: those involved in creation (contract and clause models) and those utilizing the platform for building actual contracts. Exactly like on Wikipedia (editors vs readers). It remains open since anyone can become an editor. Established workflows for content discussion, consensus achievements, legal verification, and approval will probably allow us to keep the wiki open for anonymous editing, with the appropriate spam-combatting workflow.

Due to MediaWiki software specifics, the data not to be shared, such as personalized variables, adapted drafts, actual contracts, etc., shall be stored on the external instance application side.

So, the whole project can consist of two main parts:

# '''The wiki'''. Open to the community. Focused on creating contract model collections for different deals, countries, and use cases (and in multiple languages, maybe). Allows standard contract construction and printing. Even anonymously. It is already a considerable project.
# '''The instance application'''. Self hosted, personal or shared (like within an organisation). Allows editing, storing, signing and handling personalized copies of contracts generated using the wiki. Can implement the peer-to-peer signing workflow. Not MediaWiki. Independent, no MediaWiki account is required. Can connect to different WikiDeal instances (federated, decentralized).

== Key features ==
Also see: [[Key Features]]

* '''Contract Models''': Templates for agreements open for community editing and discussion.
* '''Clauses Customization''': Users can manipulate legal clauses to ensure adaptability and compliance.
* '''Contract Creation''': Users select models, input variables, and personalize contracts, saving them in different formats.
* '''Negotiation & Signing''': Contracts go through negotiation phases with different statuses (e.g., draft, signed).
* '''Post-Deal Support''': Reminders, automated payments, and service activation/cancellation based on contract terms.
* '''Decentralization''': Contracts are stored locally for privacy; proposals for decentralized solutions for organizations and individuals are in place.

With plans for a proof of concept and MVP, WikiDeal envisions a community-driven space fostering innovation in contract management.

Additional features in the pipeline include personalized contract styling, external contract creation tools, and true peer-to-peer contract creation, aiming for a transformative impact on how contracts are created, managed, and executed.

== Planing ==
# INTRODUCTION : all key-features for the Wikideal Minimum Viable product being interdependant, they will be developed in paralel, together, following the same planing.
# '''Users Needs analysis with experts.'''
#: '''a) Design activities:''' developing basic wireframes to visualize the layout and flow of the MVP and defining user stories to outline the expected user interactions. Including meeting to design and adapt:
#:* usecase scenarios
#:* mockups
#:* workflows
#:* development rules/structure (such as metatada/ontology principles)
#: '''b) Studying the code of existing mediawiki extensions before developing''', out of the 1'447 existing ones, such as:
#:* PageForms,
#:* SemanticMediaWiki,
#:* Cite,
#:* Wikibase (Wikidata client),
#:and perhaps some others.
# '''Ontology planning:''' defining metadata scheme for clauses, contract models, and helper data objects like user manuals, guided tours, etc.
# '''Development activities:''' implementing the core features identified in the earlier stages.
# '''Testing''' individual components.
# '''Release the MVP''' to a limited audience or beta testers to collect feedback and monitor its performance in a real-world environment.
# '''Iterate Based on Feedback:''' Analyze the feedback received and make necessary improvements.
# '''Track key performance indicators (KPIs)''' to assess the success of the MVP and guide further iterations.

== Rough time estimates (for MVP development) ==
Estimated time required for experienced developers proficient in PHP and JavaScript to use MediaWiki and develop MediaWiki extensions.

==== Customization of contract templates and clauses (MediaWiki) ====
PHP & MediaWiki extension development: approximately 120-140 hours.

JavaScript for frontend: estimated 80-100 hours.

==== Basic contract creation (MediaWiki) ====
PHP & MediaWiki extension development: approximately 120-140 hours.

JavaScript for frontend: estimated 80-100 hours.

==== Advanced contract creation & Post-Deal support (instance application) ====
Development: estimated at 140-160 hours.

==== Negotiation & Signing (instance application) ====
Development: approximately 160-180 hours.

=== Totals ===
''These estimates are subject to variation based on the familiarity with developing MediaWiki extensions, specific requirements that are to be decided, and other factors.''

Total estimated: 700-820 hours (includes hours of coaching, coordination, and documentation)

WikiDeal:Minimum Viable Product

2023-11-29T14:50:13Z

Creativesoul4ever: /* Rough time estimates */

== Abstract ==
WikiDeal is a collaborative platform, much like Wikipedia, aiming to revolutionize contract management. Users can access, modify, and personalize contract models and clauses for a variety of agreements. The platform emphasizes decentralized ownership, allowing users to collectively govern and contribute to its evolution.

== The software development challenge for a Minimum Viable Product (MVP) ==
The proposed project scope cannot be solely implemented on the MediaWiki platform.

While MediaWiki excels in collaborative text editing and knowledge creation, its design, geared towards openness, proves inadequate for handling electronic signatures, private data, and sensitive or confidential content. The platform lacks official support for splitting access to content on a per-page basis, making it insufficiently secure for documents of a legal nature, such as contracts. Storing personalized clauses globally in the central database would significantly escalate the requirements for the database server. It is imperative not to store personal data on the wiki, including actual values of sensitive contract variables or real contracts. The above factors render the signing workflow on the wiki side unattainable.

What we can do, however, '''is utilize MediaWiki as a repository for clauses and contract models, with an integrated interactive contract prototype builder.''' This tool should enable users to pass variables, configure options, preload predefined sections and clauses, and select additional clauses from a designated "bank." Users should also be able to adjust the ordering of these components. The system will generate a dynamic preview of the contract, incorporating the selected clauses aligned with the contract model and substituting dynamic variables with values provided. It can be printed as is on the fly. The resulting text will not be stored or edited on the wiki.

Users can then request the resulting text in an editable format. This can be achieved by programmatically facilitating wiki markup as, for example, HTML via the MediaWiki API and sending it to a separate instance application. Further processing and import format will depend on the instance application specifics. The primary role of the instance application is to work as an interface to the contract prototype builder and import the resulting text into the application, where users can freely edit and securely store the document, which is accessible only to them.

WikiDeal caters to two primary user groups: those involved in creation (contract and clause models) and those utilizing the platform for building actual contracts. Exactly like on Wikipedia (editors vs readers). It remains open since anyone can become an editor. Established workflows for content discussion, consensus achievements, legal verification, and approval will probably allow us to keep the wiki open for anonymous editing, with the appropriate spam-combatting workflow.

Due to MediaWiki software specifics, the data not to be shared, such as personalized variables, adapted drafts, actual contracts, etc., shall be stored on the external instance application side.

So, the whole project can consist of two main parts:

# '''The wiki'''. Open to the community. Focused on creating contract model collections for different deals, countries, and use cases (and in multiple languages, maybe). Allows standard contract construction and printing. Even anonymously. It is already a considerable project.
# '''The instance application'''. Self hosted, personal or shared (like within an organisation). Allows editing, storing, signing and handling personalized copies of contracts generated using the wiki. Can implement the peer-to-peer signing workflow. Not MediaWiki. Independent, no MediaWiki account is required. Can connect to different WikiDeal instances (federated, decentralized).

== Key features ==
Also see: [[Key Features]]

* '''Contract Models''': Templates for agreements open for community editing and discussion.
* '''Clauses Customization''': Users can manipulate legal clauses to ensure adaptability and compliance.
* '''Contract Creation''': Users select models, input variables, and personalize contracts, saving them in different formats.
* '''Negotiation & Signing''': Contracts go through negotiation phases with different statuses (e.g., draft, signed).
* '''Post-Deal Support''': Reminders, automated payments, and service activation/cancellation based on contract terms.
* '''Decentralization''': Contracts are stored locally for privacy; proposals for decentralized solutions for organizations and individuals are in place.

With plans for a proof of concept and MVP, WikiDeal envisions a community-driven space fostering innovation in contract management.

Additional features in the pipeline include personalized contract styling, external contract creation tools, and true peer-to-peer contract creation, aiming for a transformative impact on how contracts are created, managed, and executed.

== Planing ==
# INTRODUCTION : all key-features for the Wikideal Minimum Viable product being interdependant, they will be developed in paralel, together, following the same planing.
# '''Users Needs analysis with experts.'''
#: '''a) Design activities:''' developing basic wireframes to visualize the layout and flow of the MVP and defining user stories to outline the expected user interactions. Including meeting to design and adapt:
#:* usecase scenarios
#:* mockups
#:* workflows
#:* development rules/structure (such as metatada/ontology principles)
#: '''b) Studying the code of existing mediawiki extensions before developing''', such as:
#:* PageForms,
#:* SemanticMediaWiki,
#:* Cite,
#:* Wikibase (Wikidata client),
#:and perhaps some others.
# '''Ontology planning:''' defining metadata scheme for clauses, contract models, and helper data objects like user manuals, guided tours, etc.
# '''Development activities:''' implementing the core features identified in the earlier stages.
# '''Testing''' individual components.
# '''Release the MVP''' to a limited audience or beta testers to collect feedback and monitor its performance in a real-world environment.
# '''Iterate Based on Feedback:''' Analyze the feedback received and make necessary improvements.
# '''Track key performance indicators (KPIs)''' to assess the success of the MVP and guide further iterations.

== Rough time estimates (for MVP development) ==
Estimated time required for experienced developers proficient in PHP and JavaScript to use MediaWiki and develop MediaWiki extensions.

==== Customization of contract templates and clauses (MediaWiki) ====
PHP & MediaWiki extension development: approximately 120-140 hours.

JavaScript for frontend: estimated 80-100 hours.

==== Basic contract creation (MediaWiki) ====
PHP & MediaWiki extension development: approximately 120-140 hours.

JavaScript for frontend: estimated 80-100 hours.

==== Advanced contract creation & Post-Deal support (instance application) ====
Development: estimated at 140-160 hours.

==== Negotiation & Signing (instance application) ====
Development: approximately 160-180 hours.

=== Totals ===
''These estimates are subject to variation based on the familiarity with developing MediaWiki extensions, specific requirements that are to be decided, and other factors.''

Total estimated: 700-820 hours (includes hours of coaching, coordination, and documentation)

WikiDeal:Minimum Viable Product

2023-11-29T14:49:37Z

Creativesoul4ever: /* Planing */

== Abstract ==
WikiDeal is a collaborative platform, much like Wikipedia, aiming to revolutionize contract management. Users can access, modify, and personalize contract models and clauses for a variety of agreements. The platform emphasizes decentralized ownership, allowing users to collectively govern and contribute to its evolution.

== The software development challenge for a Minimum Viable Product (MVP) ==
The proposed project scope cannot be solely implemented on the MediaWiki platform.

While MediaWiki excels in collaborative text editing and knowledge creation, its design, geared towards openness, proves inadequate for handling electronic signatures, private data, and sensitive or confidential content. The platform lacks official support for splitting access to content on a per-page basis, making it insufficiently secure for documents of a legal nature, such as contracts. Storing personalized clauses globally in the central database would significantly escalate the requirements for the database server. It is imperative not to store personal data on the wiki, including actual values of sensitive contract variables or real contracts. The above factors render the signing workflow on the wiki side unattainable.

What we can do, however, '''is utilize MediaWiki as a repository for clauses and contract models, with an integrated interactive contract prototype builder.''' This tool should enable users to pass variables, configure options, preload predefined sections and clauses, and select additional clauses from a designated "bank." Users should also be able to adjust the ordering of these components. The system will generate a dynamic preview of the contract, incorporating the selected clauses aligned with the contract model and substituting dynamic variables with values provided. It can be printed as is on the fly. The resulting text will not be stored or edited on the wiki.

Users can then request the resulting text in an editable format. This can be achieved by programmatically facilitating wiki markup as, for example, HTML via the MediaWiki API and sending it to a separate instance application. Further processing and import format will depend on the instance application specifics. The primary role of the instance application is to work as an interface to the contract prototype builder and import the resulting text into the application, where users can freely edit and securely store the document, which is accessible only to them.

WikiDeal caters to two primary user groups: those involved in creation (contract and clause models) and those utilizing the platform for building actual contracts. Exactly like on Wikipedia (editors vs readers). It remains open since anyone can become an editor. Established workflows for content discussion, consensus achievements, legal verification, and approval will probably allow us to keep the wiki open for anonymous editing, with the appropriate spam-combatting workflow.

Due to MediaWiki software specifics, the data not to be shared, such as personalized variables, adapted drafts, actual contracts, etc., shall be stored on the external instance application side.

So, the whole project can consist of two main parts:

# '''The wiki'''. Open to the community. Focused on creating contract model collections for different deals, countries, and use cases (and in multiple languages, maybe). Allows standard contract construction and printing. Even anonymously. It is already a considerable project.
# '''The instance application'''. Self hosted, personal or shared (like within an organisation). Allows editing, storing, signing and handling personalized copies of contracts generated using the wiki. Can implement the peer-to-peer signing workflow. Not MediaWiki. Independent, no MediaWiki account is required. Can connect to different WikiDeal instances (federated, decentralized).

== Key features ==
Also see: [[Key Features]]

* '''Contract Models''': Templates for agreements open for community editing and discussion.
* '''Clauses Customization''': Users can manipulate legal clauses to ensure adaptability and compliance.
* '''Contract Creation''': Users select models, input variables, and personalize contracts, saving them in different formats.
* '''Negotiation & Signing''': Contracts go through negotiation phases with different statuses (e.g., draft, signed).
* '''Post-Deal Support''': Reminders, automated payments, and service activation/cancellation based on contract terms.
* '''Decentralization''': Contracts are stored locally for privacy; proposals for decentralized solutions for organizations and individuals are in place.

With plans for a proof of concept and MVP, WikiDeal envisions a community-driven space fostering innovation in contract management.

Additional features in the pipeline include personalized contract styling, external contract creation tools, and true peer-to-peer contract creation, aiming for a transformative impact on how contracts are created, managed, and executed.

== Planing ==
# INTRODUCTION : all key-features for the Wikideal Minimum Viable product being interdependant, they will be developed in paralel, together, following the same planing.
# '''Users Needs analysis with experts.'''
#: '''a) Design activities:''' developing basic wireframes to visualize the layout and flow of the MVP and defining user stories to outline the expected user interactions. Including meeting to design and adapt:
#:* usecase scenarios
#:* mockups
#:* workflows
#:* development rules/structure (such as metatada/ontology principles)
#: '''b) Studying the code of existing mediawiki extensions before developing''', such as:
#:* PageForms,
#:* SemanticMediaWiki,
#:* Cite,
#:* Wikibase (Wikidata client),
#:and perhaps some others.
# '''Ontology planning:''' defining metadata scheme for clauses, contract models, and helper data objects like user manuals, guided tours, etc.
# '''Development activities:''' implementing the core features identified in the earlier stages.
# '''Testing''' individual components.
# '''Release the MVP''' to a limited audience or beta testers to collect feedback and monitor its performance in a real-world environment.
# '''Iterate Based on Feedback:''' Analyze the feedback received and make necessary improvements.
# '''Track key performance indicators (KPIs)''' to assess the success of the MVP and guide further iterations.

== Rough time estimates ==
Estimated time required for experienced developers proficient in PHP and JavaScript to use MediaWiki and develop MediaWiki extensions.

==== Customization of contract templates and clauses (MediaWiki) ====
PHP & MediaWiki extension development: approximately 120-140 hours.

JavaScript for frontend: estimated 80-100 hours.

==== Basic contract creation (MediaWiki) ====
PHP & MediaWiki extension development: approximately 120-140 hours.

JavaScript for frontend: estimated 80-100 hours.

==== Advanced contract creation & Post-Deal support (instance application) ====
Development: estimated at 140-160 hours.

==== Negotiation & Signing (instance application) ====
Development: approximately 160-180 hours.

=== Totals ===
''These estimates are subject to variation based on the familiarity with developing MediaWiki extensions, specific requirements that are to be decided, and other factors.''

Total estimated: 700-820 hours (includes hours of coaching, coordination, and documentation)

WikiDeal:Minimum Viable Product

2023-11-28T15:51:07Z

Creativesoul4ever: /* Rough time estimates */

== Abstract ==
WikiDeal is a collaborative platform, much like Wikipedia, aiming to revolutionize contract management. Users can access, modify, and personalize contract models and clauses for a variety of agreements. The platform emphasizes decentralized ownership, allowing users to collectively govern and contribute to its evolution.

== The software development challenge for a Minimum Viable Product (MVP) ==
The proposed project scope cannot be solely implemented on the MediaWiki platform.

While MediaWiki excels in collaborative text editing and knowledge creation, its design, geared towards openness, proves inadequate for handling electronic signatures, private data, and sensitive or confidential content. The platform lacks official support for splitting access to content on a per-page basis, making it insufficiently secure for documents of a legal nature, such as contracts. Storing personalized clauses globally in the central database would significantly escalate the requirements for the database server. It is imperative not to store personal data on the wiki, including actual values of sensitive contract variables or real contracts. The above factors render the signing workflow unattainable.

What we can do, however, '''is utilize MediaWiki as a repository for clauses and contract models, with an integrated interactive contract prototype builder.''' This tool should enable users to pass variables, configure options, preload predefined sections and clauses, and select additional clauses from a designated "bank." Users should also be able to adjust the ordering of these components. The system will generate a dynamic preview of the contract, incorporating the selected clauses aligned with the contract model and substituting dynamic variables with values provided. It can be printed as is on the fly. The resulting text will not be stored or edited on the wiki.

Users can then request the resulting text in an editable format. This can be achieved by programmatically facilitating wiki markup as, for example, HTML via the MediaWiki API and sending it to a separate instance application. Further processing and import format will depend on the instance application specifics. The primary role of the instance application is to provide access to the contract prototype builder and import the resulting text into the application, where users can freely edit and securely store the document, which is accessible only to them.

WikiDeal caters to two primary user groups: those involved in creation (contract and clause models) and those utilizing the platform for building actual contracts. Exactly like on Wikipedia (editors vs readers). It remains open since anyone can become an editor. Established workflows for content discussion, consensus achievements, legal verification, and approval will probably allow us to keep the wiki open for anonymous editing (mind spam combatting workflow). Maybe it won't be as open as Wikipedia: if we want to allow users to store anything (like personalized variables, etc.), the account creation shall be mandatory unless we move the “personalized” part to the external instance application.

So, the whole project can consist of two main parts:

# '''The wiki'''. Open to the community. Focused on creating contract model collections for different deals, countries, and use cases (and in multiple languages, maybe). Allows standard contract construction and printing. Even anonymously. It is already a considerable project.
# '''The instance application'''. Self hosted, personal or shared (like within an organisation). Allows editing, storing, signing and handling personalized copies of contracts generated using the wiki. Can implement the peer-to-peer signing workflow. Not MediaWiki. Independent, no MediaWiki account is required. Can connect to different WikiDeal instances (federated, decentralized).

== Key features ==
Also see: [[Key Features]]

* '''Contract Models''': Templates for agreements open for community editing and discussion.
* '''Clauses Customization''': Users can manipulate legal clauses to ensure adaptability and compliance.
* '''Contract Creation''': Users select models, input variables, and personalize contracts, saving them in different formats.
* '''Negotiation & Signing''': Contracts go through negotiation phases with different statuses (e.g., draft, signed).
* '''Post-Deal Support''': Reminders, automated payments, and service activation/cancellation based on contract terms.
* '''Decentralization''': Contracts are stored locally for privacy; proposals for decentralized solutions for organizations and individuals are in place.

With plans for a proof of concept and MVP, WikiDeal envisions a community-driven space fostering innovation in contract management.

Additional features in the pipeline include personalized contract styling, external contract creation tools, and true peer-to-peer contract creation, aiming for a transformative impact on how contracts are created, managed, and executed.

== Planing ==

# '''Users Needs analysis with experts.''' '''1a) Design activities:''' developing basic wireframes to visualize the layout and flow of the MVP and defining user stories to outline the expected user interactions. Including meeting to design and adapt : usecase scenarios - mockups - workflows - development rules/structure (such as metatada/ontology principles) 1b) Studying the code of existing mediawiki extensions before developing, such as : Pageforms, Semantic wiki, Cite extension, Wikibase client, abstract (reference : [[mediawikiwiki:Category:All_extensions|list of 1447 existing mediawiki extensions]]) <br />
# '''Development activities:''' implementing the core features identified in the earlier stages.
# '''Testing''' individual components.
#'''Release the MVP''' to a limited audience or beta testers to collect feedback and monitor its performance in a real-world environment.
#'''Iterate Based on Feedback:''' Analyze the feedback received and make necessary improvements.
#'''Track key performance indicators (KPIs)''' to assess the success of the MVP and guide further iterations.

== Rough time estimates ==
Estimated time required for experienced developers proficient in PHP and JavaScript to use MediaWiki and develop MediaWiki extensions.

==== Customization of contract templates and clauses (MediaWiki) ====
PHP & MediaWiki extension development: approximately 120-140 hours.

JavaScript for frontend: estimated 80-100 hours.

==== Basic contract creation (MediaWiki) ====
PHP & MediaWiki extension development: approximately 120-140 hours.

JavaScript for frontend: estimated 80-100 hours.

==== Advanced contract creation & Post-Deal support (instance application) ====
Development: estimated at 140-160 hours.

==== Negotiation & Signing (instance application) ====
Development: approximately 160-180 hours.

=== Totals ===
''These estimates are subject to variation based on the familiarity with developing MediaWiki extensions, specific requirements that are to be decided, and other factors.''

Total estimated: 700-820 hours (includes hours of coaching, coordination, and documentation)

WikiDeal:Minimum Viable Product

2023-11-28T15:07:06Z

Creativesoul4ever: /* Planification */

WikiDeal:Minimum Viable Product

2023-11-28T15:02:36Z

Creativesoul4ever:

WikiDeal:Minimum Viable Product

2023-11-28T15:00:11Z

Creativesoul4ever: /* Planification */

WikiDeal:Minimum Viable Product

2023-11-28T14:57:03Z

Creativesoul4ever: adding a new paragraph regarding milestones/planfication

WikiDeal:Minimum Viable Product

2023-11-28T14:37:54Z

Creativesoul4ever: /* Rough time estimates */

WikiDeal:Development

2023-11-27T16:02:13Z

Creativesoul4ever: