You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As an admin user,
I want admin bot management actions to update the readable bot representation only through simulator-published events,
so that the simulator remains authoritative for bot state.
Acceptance Criteria
Given an admin creates a bot
When the simulator publishes BotCreated
Then the read model creates the bot document.
Given an admin updates a bot
When the simulator publishes BotUpdated
Then the read model updates only after the event.
Given an admin removes a bot
When the simulator publishes BotRemoved
Then the read model marks it removed.
Given the admin app performs management actions
When those actions complete
Then the admin app does not directly write to Cosmos DB bots.
As an admin user,
I want admin bot management actions to update the readable bot representation only through simulator-published events,
so that the simulator remains authoritative for bot state.
Acceptance Criteria
Given an admin creates a bot
When the simulator publishes
BotCreatedThen the read model creates the bot document.
Given an admin updates a bot
When the simulator publishes
BotUpdatedThen the read model updates only after the event.
Given an admin removes a bot
When the simulator publishes
BotRemovedThen the read model marks it removed.
Given the admin app performs management actions
When those actions complete
Then the admin app does not directly write to Cosmos DB
bots.