Skip to main content
An ownership signal gives an organization insight into how well engineers understand the logic and flow of the AI-generated code they ship. It comes from the explanation submitted for a specific change.

​
In the repository

Second Flow publishes a result link and updates the provider check outcome. Teams can use that outcome during review or make the check part of their merge requirements through repository rules. Read the explanation’s feedback alongside the code and review discussion. An ownership signal adds evidence of understanding to the workflow.

​
Across the workspace

Analysis & Signals gives workspace owners reports about understanding-check completion, question friction, hotspots, and ownership-signal coverage. These views describe repository workflows and code areas rather than rank individual engineers. Use them to identify where project documentation needs attention, where questions need clearer context, or where a review conversation may help.

​
Interpret results in context

Results reflect a particular explanation, source revision, and repository policy. They support code review and coaching. They are not a standalone basis for employment decisions or a developer leaderboard.