View source for WikiDeal talk:Minimum Viable Product

The text is not conclusive. First you write the X-APP " Not MediaWiki. Independent, no MediaWiki account is required. Can connect to different WikiDeal instances."
But on the x_app-Part, you write "Decentralization (MediaWiki extension):

PHP & MediaWiki extension"

It shoud be web-application backend and web-application front-end.

I don't think that a wiki is a good place for working on a text like this. Google Docs would be better.

== Wiki features? ==

Also these features are mentioned in the wiki part, but IMO cannot be realized in a centralized wiki:

* Negotiation & Signing: Contracts go through negotiation phases with different statuses (e.g., draft, signed).
:: This is for the x-app, I guess

* Post-Deal Support: Reminders, automated payments, and service activation/cancellation based on contract terms.
:: This is for the x-app, I guess

* Decentralization: Contracts are stored locally for privacy; proposals for decentralized solutions for organizations and individuals are in place.
:: This is for the x-app, I guess. How can you store a contract done in a MediaWiki instance locally?

* 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.
:: Again, for the x-app, no?

== Available services ==
Did you check for existing solutions? On trying to find an example for a lease contract, I found
* https://eforms.com/
* https://www.jotform.com/pdf-templates/lease-agreement
* https://legaltemplates.net/
* for general terms and conditions: https://www.iubenda.com
So the question really is: why would a funding agency fund something like this...

== Wikifunctions ==
One potential course of the project could be to try to formulate legal/contractual things in forms of Wiki functions:
https://www.wikifunctions.org