← Back to index

WikiDeal Architecture — One Wiki, Many Apps

WikiDeal is strongly inspired by Wikipedia, but with a major architectural adaptation. Where the Wikimedia network runs many separate wikis (Wikipedia, Wikibooks, Wiktionary…), WikiDeal runs a single MediaWiki (one per language, for now) feeding many smartphone applications.

The Core Difference

📚 Wikimedia / Wikipedia

🏢 WikiDeal

One Wiki → Many Apps

📖 Single WikiDeal MediaWiki (per language)
clauses · bases · models · amendments · rules · validated agreements
↓   feeds   ↓
👶 Babysitting appselected & approved clauses
⚖️ Arbitration apptriggered when arbitration is needed
🏠 Coop Housing appscoped models
… more appseach with its own cache/scope

How Apps Use the Wiki

MechanismWhat it means
Select within the modelApps select only certain options/clauses/models from the shared wiki content. Some options are not even selectable in a given model.
Lock / unlock (bridage)Selected options can be locked or unlocked — each with its legal impact.
Lawyer validationValidation by lawyers prevents incoherent orders and contracts with legal breaches / problematic situations.
Per-app cachesA common base, but caches restrict each app to certain functions — different validated clauses/models per contract type.
Embedding (incrustation)The transactional dashboard stays outside the wiki, but at transaction time its forms (e.g. registration / checkout) embed references to the conditions and contracts that live on the wiki in lawyer-validated mode (Contract-Validated:). The wiki is the single source of truth; the app surfaces it inline.

What Stays Identical to Wikipedia

WikiDeal keeps the same MediaWiki, the same licenses, the same participatory management structures and procedures: revision, editing, and approval (the proper term — not "validation"). The difference is the app layer on top, not the wiki foundation.

Reusable Teaser (link from many pages)

To avoid repeating the full explanation everywhere, a short teaser sentence links back here from many pages: