Sample · fictional data · offline demo · DLD/Ejari matching is MOCKED · nothing is sent anywhere
ORCA force · escape test

Can a locked fee sheet survive a WhatsApp close?

Demo stageSample
1The locked sheet
2The escape attempt

ORCA can see

  • The locked sheet, its hash and every version
  • Any commission recorded on-platform (non-matching = rejected)
  • A client report tied to the hash
  • Standing-check consent / decline

ORCA cannot see

  • WhatsApp messages or calls
  • Cash or bank transfers off-platform
  • Whether the deal closed — unless the client reports it or a registry match exists
3Detector 1 · client report (primary)

On the client's locked screen: one tap — "I was asked to pay a different amount". Records the claimed amount, timestamp and the sheet hash.

4Detector 2 · registry match (bonus)
Mocked Needs DLD partner access — unverified. No DLD / Ejari connection exists. The rows below are fictional sample registrations.
5Honest verdict

Enforced by the system

  • Fee arithmetic from a country rules file; verified caps blocked, unverified rules only tagged
  • Lock = SHA-256 of canonical JSON, same hash on both phones
  • Any other commission number is rejected on-platform
  • Edits = new version, mandatory reason, hash-chained; client total can never increase
  • Agent split must sum exactly to the commission
  • Report is bound to the hash, so the agreed figure cannot be disputed

Depends on detection

  • Anything said on WhatsApp, by phone or in person
  • Cash or transfers outside ORCA
  • Collusive deals where the client benefits and stays silent
  • Registry matching — needs DLD partner access, unverified
  • Upholding a report still needs a human review
ORCA force demo · Sample data · No claim is made that UAE Pass, DLD, Ejari, Bayut or Property Finder integrations work. All matching shown is mocked.