Does AI worldview evolve differently to the human worldview during program development

[BugsFreed]

Select Topic Area

Product Feedback

Body

Title is deep but my example is very simple.
Now:
I am using Visual Studio 2022 17.14.25 Jan 2026 edition with the built in Github Copilot which I have a licensed subscription to use.
In the copilot I am using Clause Sonnet 4.5 in agent mode (and ask and debug) and have great successes.

But:
AI’s seem to have a concept issue with this very very simple below issue:
[Comments in square brackets are directed to you the reader the rest are to Claude:]

Issue:
Draw me a rectangle [now imagine where is the bottom-left corner of that rectangle and keep it in mind]
Rotate the rectangle counter-clockwise by 90 degrees. [in your opinion, where is the bottom-left now??]
Draw a 2cm vertical line down from the bottom left hand corner of that rectangle.

Success??:
So the AI draws a line from what we humans would now call the bottom-right hand corner. For us, the rotation is complete and the original bottom-left became the bottom-right. We would naturally draw a line from the actual new bottom-left as per the instruction (which was created as top-left).
For the AI, the bottom-left is what it knows from the time of creation so it draws the line from the bottom-right.

..and this is not the only time this happens, its just the easiest example to choose. Maybe AI’s worldview is for the program from the point of creation and never updates its time of reference for the new worldview after each transition. I've seen other effects that lead me to this conclusion. Does anyone else notice similar effect and sometimes 'annoyances'.

[Tech Info: Windows 11 computer: Building a WPF .NET 8.0 C# user interface in standard XAML with .cs behind code: Only special package added is NuGet PDFSharp-MigraDoc-WPF but I was not rendering to pdf at the time]

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐

[beenish-1]

This behavior is real and comes from a frame-of-reference ambiguity, not a lack of geometric understanding.

When you create a rectangle, its corners are fixed vertices, for example:

• bottomLeft
• bottomRight
• topRight
• topLeft

Rotating the rectangle (using WPF, XAML, PDFSharp, SVG, etc.) transforms the coordinates, but the vertex labels don’t automatically update. That means the original bottomLeft is still the same vertex in memory, even if it now appears visually at the top-left, top-right, or bottom-right.

Humans naturally reinterpret “bottom-left” after rotation. AI tools often continue referring to the original vertex unless told to recalculate which corner is now bottom-left in screen coordinates.

Two interpretations exist:

• Object-relative: “bottom-left” = original vertex, regardless of rotation
• World-relative: “bottom-left” = vertex with the lowest X and Y after rotation

Most AI tools default to the object-relative interpretation.

Workaround: Be explicit about recomputing positions. For example:

“Rotate the rectangle 90° counter-clockwise, then determine which vertex is now the bottom-left in world coordinates, and draw the line from that point.”

This issue isn’t limited to rectangles—it appears in many UI, CAD, and rendering scenarios where transforms change orientation but don’t rename vertices.

[BugsFreed]

Understood this yes, thank you for objective response.
The issue is not that we humans are unable to frame a prompt to instruct the AI correctly. It is a question of correcting/allowing for the AI object-relative view versus human world-relative view now, while the models are young. Imagine when you set multiple AIs to perform solution calculations communicating amongst themselves, each one with its own creation reference point. Mayhem.. or at least multiple redundant queries!
In my opinion, there is no need for this object-relative view point, the AI is supposed to interact with a human-centric philosophy, though I am sure someone will find a use for the AI object-relative view. And "instructing" the AI correctly is wrong as it is a waste of both out time, mental energy and finally compute resources. Change to a more human perspective now would alleviate many challenges we face writing prompts and interpreting answers from the AI. Remember the example of the vertex of the square is a simplistic example.
So: do we want to be able to give the AI a choice of the reference frame (AI-Centric or Human-Centric view with all the qualification and explanation that that would need) or do we just say, human-centric is the only viewpoint that should exist, because the AI object-relative view point is really an accident.
I'd love to see a response on this from Anthropic regarding Claude Sonnet 4.5 and I'd love to know if ALL AI models suffer this ambiguity or whether it is just Claude.