Clara observations and conflicts

Clara is most useful when she reads the same surface the team is already using. Instead of sending operators to a separate analytics tab, the observations live beside the routes, flags, and bets that produced them.

What Clara is doing

Clara watches for patterns worth review, including:

• rollout drift against the original bet
• route conflicts where multiple changes touch the same traffic
• quality issues that make a conclusion less trustworthy

The observation is the start of a review, not the end of it.

Conflict detection

Conflicts matter because a team can easily misread the effect of one rollout when two or three changes are touching the same audience. Clara surfaces that overlap so operators can acknowledge it while the context is still fresh.

The operator still decides

TrueClara is deliberately not an auto-action layer. Clara should make the next human decision sharper, faster, and more traceable.