Switch the flow, persona, and example before exporting.
The evidence should explain a discrepancy, not become the workflow.
This prototype compares today’s verification flow, the evidence-first design, and Elodie’s task-led proposal. Switch personas to see who can suggest, review, update PMS, and close the work.
Interactive Property Handbook prototype · 9 July 2026 · source: NX-1578 design and Elodie’s workflow proposal
Flow
Persona
Selected workflow
Units / DE_BER_001_Bahadir / Property Handbook
What the evidence builder is
A safe snapshot used only for comparison
It runs inside the existing Notion extraction job. It stores safe item-level observations so the server can compare Source with fresh PMS later.
✓stores safe typed items, scope, capture time, identity, and hashes
✓creates no suggestion, task, approval, or PMS update
✓never claims that Notion or PMS changed
✓is unnecessary for a manual guest report that has no Notion discrepancy
Where the current design is too heavy
It mixes discrepancy detection with work routing
The evidence-first design handles system differences well, but its suggestion flow currently routes GuestCom proposals to ops admin rather than the Property Manager.
1keep evidence for system-detected Source and PMS differences
2use a typed correction request for GuestCom reports
3use a task to route the request to the Property Manager
4only a successful PMS action closes the request
Recommended simplification
Use the evidence builder only to create trustworthy system discrepancies. Use Elodie’s task-led flow for human-reported corrections. Both should end in the same typed PMS writer and Activity log.
Decision still needed: can the Property Manager role apply and dismiss GuestCom suggestions, or must that remain with ops admin?