WikiDeal - User contributions [en]

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:

WikiDeal:Minimum Viable Product

2023-11-27T15:54:25Z

Creativesoul4ever: Re-estimated X-app hour of dev

'''English resume :'''

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 HTML via MediaWiki API and sending it to a separate application (referred to as the "X app"). Further processing and import format will depend on the X app specifics. The primary role of the X app 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 content 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 X app.

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 X app'''. Personal. Allows editing and storing personalized copies of contracts generated on WikiDeal. Can implement the peer-to-peer signing workflow. Not MediaWiki. Independent, no MediaWiki account is required. Can connect to different WikiDeal instances.
----

'''''Key features for the wiki include:'''''

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.

Estimated time required for two experienced developers proficient in PHP and JavaScript to use MediaWiki and develop MediaWiki extensions :

''Customization of contract templates and clauses:''

PHP & MediaWiki extension development : approximately 100-120 hours.

JavaScript for Frontend : estimated 60-80 hours.

''Contract creation :''

PHP & MediaWiki extension development: approximately 120-140 hours.

JavaScript for Frontend : estimated 80-100 hours.

Post-processing support (MediaWiki extension):

PHP & MediaWiki extension development: estimated at 100-120 hours. JavaScript for Frontend : estimated 60-80 hours.

These estimates are subject to variation based on the actual complexity of implementing MediaWiki extensions, specific requirements, and developers familiarity with developing MediaWiki extensions.

'''Total estimated : 640-780 hours (+ hours of coaching/coordination/documentation)'''
----'''''The "x-app"'''''

''Decentralization (MediaWiki extension):''

PHP & MediaWiki extension: approximately 240-280 hours.

JavaScript for Frontend (if applicable): estimated 160 and 200 hours.

----

'''''Other extensions (nice to have)'''''

''Negotiation and signing :''

PHP & MediaWiki Extension: approximately 100-120 hours.

JavaScript for Frontend : estimated 60-80 hours.

----

WikiDeal:Minimum Viable Product

2023-11-27T15:50:23Z

Creativesoul4ever:

'''English resume :'''

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 HTML via MediaWiki API and sending it to a separate application (referred to as the "X app"). Further processing and import format will depend on the X app specifics. The primary role of the X app 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 content 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 X app.

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 X app'''. Personal. Allows editing and storing personalized copies of contracts generated on WikiDeal. Can implement the peer-to-peer signing workflow. Not MediaWiki. Independent, no MediaWiki account is required. Can connect to different WikiDeal instances.
----

'''''Key features for the wiki include:'''''

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.

Estimated time required for two experienced developers proficient in PHP and JavaScript to use MediaWiki and develop MediaWiki extensions :

''Customization of contract templates and clauses:''

PHP & MediaWiki extension development : approximately 100-120 hours.

JavaScript for Frontend : estimated 60-80 hours.

''Contract creation :''

PHP & MediaWiki extension development: approximately 120-140 hours.

JavaScript for Frontend : estimated 80-100 hours.

Post-processing support (MediaWiki extension):

PHP & MediaWiki extension development: estimated at 100-120 hours. JavaScript for Frontend : estimated 60-80 hours.

These estimates are subject to variation based on the actual complexity of implementing MediaWiki extensions, specific requirements, and developers familiarity with developing MediaWiki extensions.

'''Total estimated : 640-780 hours (+ hours of coaching/coordination/documentation)'''
----'''''The "x-app"'''''

''Decentralization (MediaWiki extension):''

PHP & MediaWiki extension: approximately 120-140 hours.

JavaScript for Frontend (if applicable): estimated 80 and 100 hours.

----

'''''Other extensions (nice to have)'''''

''Negotiation and signing :''

PHP & MediaWiki Extension: approximately 100-120 hours.

JavaScript for Frontend : estimated 60-80 hours.

----

WikiDeal:Minimum Viable Product

2023-11-27T15:48:37Z

Creativesoul4ever:

'''English resume :'''

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 HTML via MediaWiki API and sending it to a separate application (referred to as the "X app"). Further processing and import format will depend on the X app specifics. The primary role of the X app 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 content 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 X app.

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 X app'''. Personal. Allows editing and storing personalized copies of contracts generated on WikiDeal. Can implement the peer-to-peer signing workflow. Not MediaWiki. Independent, no MediaWiki account is required. Can connect to different WikiDeal instances.

'''''Key features for the wiki include:'''''

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.

Estimated time required for two experienced developers proficient in PHP and JavaScript to use MediaWiki and develop MediaWiki extensions :

''Customization of contract templates and clauses:''

PHP & MediaWiki extension development : approximately 100-120 hours.

JavaScript for Frontend : estimated 60-80 hours.

''Contract creation :''

PHP & MediaWiki extension development: approximately 120-140 hours.

JavaScript for Frontend : estimated 80-100 hours.

Post-processing support (MediaWiki extension):

PHP & MediaWiki extension development: estimated at 100-120 hours. JavaScript for Frontend : estimated 60-80 hours.

These estimates are subject to variation based on the actual complexity of implementing MediaWiki extensions, specific requirements, and developers familiarity with developing MediaWiki extensions.

'''Total estimated : 640-780 hours (+ hours of coaching/coordination/documentation)'''
----'''''The "x-app"'''''

''Decentralization (MediaWiki extension):''

PHP & MediaWiki extension: approximately 120-140 hours.

JavaScript for Frontend (if applicable): estimated 80 and 100 hours.

----

'''''Other extensions (nice to have)'''''

''Negotiation and signing :''

PHP & MediaWiki Extension: approximately 100-120 hours.

JavaScript for Frontend : estimated 60-80 hours.

----

WikiDeal:Minimum Viable Product

2023-11-27T15:45:57Z

Creativesoul4ever:

'''English resume :'''

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 HTML via MediaWiki API and sending it to a separate application (referred to as the "X app"). Further processing and import format will depend on the X app specifics. The primary role of the X app 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 content 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 X app.

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 X app'''. Personal. Allows editing and storing personalized copies of contracts generated on WikiDeal. Can implement the peer-to-peer signing workflow. Not MediaWiki. Independent, no MediaWiki account is required. Can connect to different WikiDeal instances.

'''''Key features for the wiki include:'''''

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.

Estimated time required for two experienced developers proficient in PHP and JavaScript to use MediaWiki and develop MediaWiki extensions :

''Customization of contract templates and clauses:''

PHP & MediaWiki extension development : approximately 100-120 hours.

JavaScript for Frontend : estimated 60-80 hours.

''Contract creation :''

PHP & MediaWiki extension development: approximately 120-140 hours.

JavaScript for Frontend : estimated 80-100 hours.

Post-processing support (MediaWiki extension):

PHP & MediaWiki extension development: estimated at 100-120 hours. JavaScript for Frontend : estimated 60-80 hours.

These estimates are subject to variation based on the actual complexity of implementing MediaWiki extensions, specific requirements, and developers familiarity with developing MediaWiki extensions.

'''Total estimated : 800-980 hours'''
----'''''The "x-app"'''''

''Decentralization (MediaWiki extension):''

PHP & MediaWiki extension: approximately 120-140 hours.

JavaScript for Frontend (if applicable): estimated 80 and 100 hours.

----

'''''Other extensions (nice to have)'''''

''Negotiation and signing :''

PHP & MediaWiki Extension: approximately 100-120 hours.

JavaScript for Frontend : estimated 60-80 hours.

----

WikiDeal:Minimum Viable Product

2023-11-27T15:42:22Z

Creativesoul4ever:

'''English resume :'''

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 HTML via MediaWiki API and sending it to a separate application (referred to as the "X app"). Further processing and import format will depend on the X app specifics. The primary role of the X app 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 content 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 X app.

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 X app'''. Personal. Allows editing and storing personalized copies of contracts generated on WikiDeal. Can implement the peer-to-peer signing workflow. Not MediaWiki. Independent, no MediaWiki account is required. Can connect to different WikiDeal instances.

'''''Key features for the wiki include:'''''

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.

Estimated time required for two experienced developers proficient in PHP and JavaScript to use MediaWiki and develop MediaWiki extensions :

''Customization of contract templates and clauses:''

PHP & MediaWiki extension development : approximately 100-120 hours.

JavaScript for Frontend : estimated 60-80 hours.

''Contract creation :''

PHP & MediaWiki extension development: approximately 120-140 hours.

JavaScript for Frontend : estimated 80-100 hours.

Post-processing support (MediaWiki extension):

PHP & MediaWiki extension development: estimated at 100-120 hours. JavaScript for Frontend : estimated 60-80 hours.

These estimates are subject to variation based on the actual complexity of implementing MediaWiki extensions, specific requirements, and developers familiarity with developing MediaWiki extensions.

'''Total estimated : 800-980 hours'''
----'''''The "x-app"'''''

Decentralization (MediaWiki extension): PHP & MediaWiki extension: approximately 120-140 hours. JavaScript for Frontend (if applicable): estimated 80 and 100 hours.

----

'''''Other extensions (nice to have)'''''

Negotiation and signing :

PHP & MediaWiki Extension: approximately 100-120 hours.

JavaScript for Frontend : estimated 60-80 hours.

----

WikiDeal:Minimum Viable Product

2023-11-27T15:40:10Z

Creativesoul4ever: separating x-app from the other feature, to make it in 2 step

'''English resume :'''

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 HTML via MediaWiki API and sending it to a separate application (referred to as the "X app"). Further processing and import format will depend on the X app specifics. The primary role of the X app 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 content 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 X app.

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 X app'''. Personal. Allows editing and storing personalized copies of contracts generated on WikiDeal. Can implement the peer-to-peer signing workflow. Not MediaWiki. Independent, no MediaWiki account is required. Can connect to different WikiDeal instances.

'''Key features for the wiki include:'''

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.

Estimated time required for two experienced developers proficient in PHP and JavaScript to use MediaWiki and develop MediaWiki extensions :

Customization of contract templates and clauses: PHP & MediaWiki extension development : approximately 100-120 hours. JavaScript for Frontend : estimated 60-80 hours.

Contract creation : PHP & MediaWiki extension development: approximately 120-140 hours. JavaScript for Frontend : estimated 80-100 hours.

Negotiation and signing : PHP & MediaWiki Extension: approximately 100-120 hours. JavaScript for Frontend : estimated 60-80 hours.

Post-processing support (MediaWiki extension): PHP & MediaWiki extension development: estimated at 100-120 hours. JavaScript for Frontend : estimated 60-80 hours.

These estimates are subject to variation based on the actual complexity of implementing MediaWiki extensions, specific requirements, and developers familiarity with developing MediaWiki extensions.

'''Total estimated : 800-980 hours'''
----'''The "x-app"'''

Decentralization (MediaWiki extension): PHP & MediaWiki extension: approximately 120-140 hours. JavaScript for Frontend (if applicable): estimated 80 and 100 hours.

WikiDeal:Minimum Viable Product

2023-11-27T15:35:48Z

Creativesoul4ever: adding controbutions from various experts about MVP

'''English resume :'''

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 HTML via MediaWiki API and sending it to a separate application (referred to as the "X app"). Further processing and import format will depend on the X app specifics. The primary role of the X app 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 content 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 X app.

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 X app'''. Personal. Allows editing and storing personalized copies of contracts generated on WikiDeal. Can implement the peer-to-peer signing workflow. Not MediaWiki. Independent, no MediaWiki account is required. Can connect to different WikiDeal instances.

'''Key features for the wiki include:'''

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.

Estimated time required for two experienced developers proficient in PHP and JavaScript to use MediaWiki and develop MediaWiki extensions :

Customization of contract templates and clauses: PHP & MediaWiki extension development : approximately 100-120 hours. JavaScript for Frontend : estimated 60-80 hours.

Contract creation : PHP & MediaWiki extension development: approximately 120-140 hours. JavaScript for Frontend : estimated 80-100 hours.

Negotiation and signing : PHP & MediaWiki Extension: approximately 100-120 hours. JavaScript for Frontend : estimated 60-80 hours.

Post-processing support (MediaWiki extension): PHP & MediaWiki extension development: estimated at 100-120 hours. JavaScript for Frontend : estimated 60-80 hours.

Decentralization (MediaWiki extension): PHP & MediaWiki extension: approximately 120-140 hours. JavaScript for Frontend (if applicable): estimated 80 and 100 hours.

These estimates are subject to variation based on the actual complexity of implementing MediaWiki extensions, specific requirements, and developers familiarity with developing MediaWiki extensions.

Total estimated : 880-1080 hours

WikiDeal:Development

2023-11-27T15:33:35Z

Creativesoul4ever: added link to MVP page