Sociuu Investigate

Establish expected versus observed behavior, environment, timeframe, affected tenant/persona and source. Search relevant code, tests and existing tasks. A report labelled bug is an observation, not proof of a defect.

Use the available first-party tools for relevant evidence. Keep client scope explicit and output sanitized. Read-only Production investigation requires the applicable repository and user authority; tool access alone does not authorize new Production work. Do not require Production data for local reproduction.

Test competing explanations with the smallest useful checks. Use CE Debug for technical diagnosis when appropriate, preserving the request's read-only ceiling. Do not create tasks, modify configuration or send messages for an investigation-only request. If local reproduction needs changes, use only authorized isolated setup.

When connector/API evidence is independent, a focused lower-capability evidence worker may collect and cite it. Give it the exact question and read-only boundary; the coordinating agent evaluates contradictions and makes the classification.