Future-state Deyaar prototype · Public facts + illustrative operations

CEO · Mar Casa · Demo role, not authorization

Demo guide & reset

How to run this prototype

Future-state Deyaar prototype · Public facts + illustrative operations

Modules

35

Personas

10

Illustrative records

549

Published sources

19

A fifteen-minute walkthrough

One path through the prototype that shows breadth without rushing.

  1. Select the CEO persona and open the executive decision cockpit. Persona switching always returns to that role’s workspace.
  2. Switch to the Programme Director and follow the dependency chain from a failed field check to the readiness gate.
  3. Price the recovery in scenario comparison, move the sliders, and send an option for approval.
  4. Switch to the CFO and open payment application check to see claimed against evidence-supported.
  5. Approve the agent proposal in the approval queue and watch the task appear on the task board.
  6. Finish on the board brief and download it.

The three connected stories

Each one runs end to end across several modules.

A — Mar Casa commissioning readiness

  1. • A failed smoke damper check is recorded in the field.
  2. • It raises a non-conformance, which traces back to an RFI and a superseded drawing revision.
  3. • The affected activity sits on the commissioning chain into the scenario readiness gate.
  4. • Three recovery options are priced with explicit arithmetic.
  5. • The director approves one; a contractor task is created and the CEO tracks the decision.

B — Park Five stone specification

  1. • A facade-facing stone option change is raised as a variation.
  2. • Cheaper-and-slower, balanced and faster-and-dearer routes are priced side by side.
  3. • Each route carries a compliance review gate with its own duration.
  4. • Scenario values never overwrite the published award value.

C — ELEVE payment application

  1. • An application is tested line by line against sample bill-of-quantities rates.
  2. • Claimed quantities are compared with quantities supported by field evidence.
  3. • Duplicate evidence and a missing approval are flagged.
  4. • Retention is calculated on the stated basis and a clarification is prepared for approval.

The rules this prototype keeps

Stated so nobody in the room has to guess.

  • Published facts are paraphrased from official sources and always carry a link. Everything else is marked as scenario.
  • Construction award values and project investment values are never summed together, and a parent award is never split into invented child values.
  • Coverage is described as selected public awards, never as the full portfolio.
  • No scenario date is presented as a publicly committed opening date.
  • All negative operational performance belongs to fictional organisations. Real contractors appear only in the published award register, exactly as announced.
  • The persona selector is demo role switching. It is not authentication and grants no real permission.
  • The assistant is a local demo assistant working over structured records. It is not a live general-purpose model and does not search the web.
  • External product links are launchers that open sign-in pages. There is no single sign-on and no connected integration.

Reset the demonstration

Clears the persona selection, every task, approval and agent run created in this browser.

Currently holding 8 task(s), 3 approval item(s) and 6 agent run(s) in this browser.