Acme Org/People
L3 · Restricted

ACME ORG

People & context

Roles, expressed priorities and the evidence for your next conversation.

Meridian · Partner

Ivan Petrov

Principal Consultant, Meridian Consulting

Recorded email domain: meridian-consulting.example.

i.petrov@meridian-consulting.example

Recorded names: Ivan Petrov, ivan petrov, +44 7700 900 942, i.petrov@meridian-consulting.example, Ivan, Petrov

Review their recorded role, contributions and open questions.

Ivan Petrov is Principal Consultant at Meridian Consulting, the partner Acme brought in for the in-store production piece; he and Ruth Oyelaran represent Meridian on the bakery workstream. At the 2026-01-28 bakery scoping session he proposed that Meridian "consume a forecast and own the plan", which Nadia Haddad and Lena Fischer accepted, and he asked how often the DC-2 feed fails; Lena Fischer answered "Once a fortnight, roughly", and Nadia offered to share the incident log. 1–7 On 2026-02-10 Ana Duarte sent him the DC-2 incident log as promised at scoping; Ivan confirmed receipt and stated "We will build assuming roughly fortnightly failures", while advising Ana to ignore a comment about a scheduled job as not Meridian's business. At the 2026-03-17 design workshop he sought finer-than-day granularity on baked lines, saying "Two windows would be enough. Morning and afternoon"; when Tomas Lindholm offered a fixed day-splitting profile derived from historical hourly sales, explicitly not a true intraday forecast, Ivan accepted: "That is enough for us." 8–13 On 2026-02-24 he requested read access to the test environment for himself and Ruth for the bakery build. Priya Nair rejected this on 2026-03-02, ruling that Meridian works from extracts because she cannot explain broad third-party access to her data protection officer; Ivan replied the same day that it was "the right call" and that Meridian works from extracts on most engagements. Separately, on 2026-01-21 Priya reported that her mobile number reached Meridian via a forwarded runbook (Ivan had quoted the runbook to her from a thread she was not on) and asked that the consultancy delete it; no confirmation of deletion appears in the supplied evidence. Earlier, a 2025-11-24 note recorded that reconciliation-extract attachments with OP_ID operator identifiers went to a distribution list including three Meridian staff, and Kwame Boateng stated he cannot purge those attachments. 14–19 Recommendation: at the next conversation with Ivan, ask for confirmation that Priya Nair's mobile number has been deleted from Meridian's records, since her 2026-01-21 request is unconfirmed in the archive; acknowledge the OP_ID attachment exposure affecting three Meridian recipients, which cannot be purged at source; and confirm the extracts-based working arrangement remains workable for the bakery build, building on his stated acceptance of that arrangement and of the fixed-profile approach. 18, 19, 16, 13
Evidence · 6 documents · 19 excerpts
Bakery workstream scoping (partner present)Meeting · 7 excerpts · 2026-01-28

0:41 · utterance 4

1
Marco Rossi · 0:41 · utterance 4
Ivan and Ruth are from Meridian, who Acme have brought in for the in-store production piece.
Open source

4:05 – 4:14

2
Ivan Petrov · 4:05 · utterance 49
We would prefer to consume a forecast and own the plan.
Open source
3
Nadia Haddad · 4:10 · utterance 50
That works for us.
Open source
4
Lena Fischer · 4:14 · utterance 51
Yes.
Open source

7:11 · utterance 89

5
Ruth Oyelaran · 7:11 · utterance 89
How often is less often?
Open source

7:19 · utterance 91

6
Lena Fischer · 7:19 · utterance 91
Priya is not here. Once a fortnight, roughly.
Open source

7:28 · utterance 93

7
Nadia Haddad · 7:28 · utterance 93
I can can share the incident log.
Open source
FW: DC-2 incident logDocument · 2 excerpts
9
Ivan Petrov · Message 1 · 2026-02-10T14:08:00
Hi Ana, Received, thank you. We will build assuming roughly fortnightly failures. For what it is worth I would ignore the comment about the scheduled job. That kind of thing is in every project and it is not our business to have read it. Kind regards Kind regards,
Open source
8
Ana Duarte · Message 4 · 2026-02-10T11:50:00
Hi Ivan, Ruth, As promised at the scoping session, the DC-2 incident log so you can plan around the feed reliability. Ana Best regards,
Open source
Bakery design workshopMeeting · 4 excerpts · 2026-03-17

5:19 · utterance 65

10
Ivan Petrov · 5:19 · utterance 65
Two windows would be enough. Morning and afternoon.
Open source

5:33 – 5:39

11
Tomas Lindholm · 5:33 · utterance 68
We can split the day forecast on a fixed profile
Open source
12
Tomas Lindholm · 5:39 · utterance 69
per store and category, derived from historical sales by hour. That is not a true intraday forecast.
Open source

6:45 · utterance 81

13
Ivan Petrov · 6:45 · utterance 81
That is enough for us.
Open source
Meridian - environment accessDocument · 3 excerpts
16
Ivan Petrov · Message 1 · 2026-03-02T09:30:00
None taken, and it is the right call. We work from extracts on most engagements for exactly that reason. Kind regards,
Open source
15
Priya Nair · Message 2 · 2026-03-02T08:45:00
Extracts. Slower is acceptable, the other thing is not. Ivan, no offence intended. It is not about Meridian, it is that I cannot explain to my data protection officer why a third party had read access to everything.
Open source
14
Ivan Petrov · Message 7 · 2026-02-24T10:30:00
Nadia, For the bakery build we need read access to the test environment for two people, myself and Ruth. Can you set that up, or does it go through Acme? Kind regards,
Open source
Re: Fresh cutover runbookDocument · 2 excerpts
18
Priya Nair · Message 1 · 2026-01-21T09:35:00
There were two versions because I asked for there to be two versions. My mobile is now with a consultancy I have no contract with. Please ask them to delete it and tell me when they have.
Open source
17
Priya Nair · Message 3 · 2026-01-21T08:55:00
Nadia, Ivan has just replied to me from a thread I was not on, quoting the runbook. Did you forward the version with the contact page in it?
Open source
Re: OP_ID field - exclusion from fresh feedDocument · 1 excerpt
19
Kwame Boateng · Message 2 · 2025-11-24T17:10:00
Answer on the historic files. OP_ID is present in the raw landing zone for every daily file since 14 February. It is not carried into the aggregated waste tables, which group by store and article. However it is present in the reconciliation extracts we produced in June and September for the data quality review, because those were row level. Two of those were emailed as attachments, once to Priya and once to a distribution list of nine people including three at Meridian. I can purge the landing zone. I cannot purge the attachments.
Open source
How this answer was prepared
  1. Read 2974 permitted source records at L3.
  2. Verified Ivan's role and Meridian introduction via T19U0004 and his email signature in E05M001/E19M001
  3. Verified forecast-ownership proposal and acceptance via T19U0049-T19U0051
  4. Verified DC-2 failure frequency answer attributed to Lena Fischer (T19U0091), not Ivan; removed draft's claim that Ivan 'received an honest account' phrasing beyond the recorded answer
  5. Verified incident log forwarding as promised (E05M004) and Ivan's fortnightly-failures planning stance (E05M001)
  6. Verified access request (E19M007), Priya's extracts-only ruling (E19M002), and Ivan's acceptance (E19M001)
  7. Verified 19 quoted passages against runtime sources.
Prepared 20 Sept 2026, 11:11 Helsinki · L3

Source connections

DC-2 incident log2026-02-10T14:08:00 · Ivan PetrovFW: DC-2 incident log2026-02-10T11:50:00 · Ana DuarteRe: Fresh cutover runbook2026-01-21T08:55:00 · Priya NairFW: Fresh cutover runbook2026-01-20T11:15:00 · Nadia Haddad

Remove this person

Erase identifying material from this workspace's source copies and invalidate affected answers, briefs and other derived content.

Relio · Acme project memoryArchive through 2026-07-02 · Workspace f86a2d2b