Rosana EPS Functionality Recovery + Scope Clarification (Riaan, Mira, Ivan, Arseni) — March 5, 2026

Participants: Riaan, Mira, Ivan, Arseni Type: ops_call Approximate duration: 55 minutes Date logged: 2026-03-05 Notion: Not created from this environment

Action items

• Riaan — Schedule a clarification call with Rosana and demo the current EPS / WordPress behavior live | Deadline: Mar 7 | Priority: urgent
• Riaan — Document the exact functionality Rosana says is missing versus what currently works | Deadline: Mar 7 | Priority: normal
• Ivan — Prepare a brief walkthrough of the original EPS design and what a fuller rebuild would involve | Deadline: Mar 7 | Priority: normal
• Mira — Collect any historical EPS context Rosana may reference so the team stops guessing through email | Deadline: Mar 7 | Priority: normal

Key quotes

— Riaan, re: current state versus expectations: "It just seems like there's functionality that she's expecting to see, but it's not there anymore."

— Arseni, re: the need for a live clarification call: "We should definitely have another call with her if she's not clear."

— Mira, re: the original EPS: "That EPS was a coded app that was on server."

Topics covered

1. Fix current functionality before expanding scope

The team aligned that Rosana first needs clarity on what is missing or misunderstood in the current EPS/WordPress behavior. The immediate priority is to restore or explain existing functionality before jumping into a larger rebuild discussion.

2. Email explanations are no longer enough

Riaan made clear that he inherited the system without enough background and that Rosana's requests are hard to resolve purely by email. The team agreed a live walkthrough is the best way to compare her expectations with the current implementation.

3. The original EPS and Ivan's redesign still matter