> For the complete documentation index, see [llms.txt](https://gympfy.gitbook.io/gympfy-whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://gympfy.gitbook.io/gympfy-whitepaper/whitepaper-gympfy/the-technology-behind-the-movement.md). # The Technology Behind the Movement Through the device's camera, the platform is capable of analyzing exercises in real time, identifying biomechanical patterns, and validating activities automatically. This technology ensures that the user experience is built upon real effort, creating a reliable foundation for progression, leaderboards, achievements, and rewards. #### A Digital Skeleton Upon starting an activity, the system identifies strategic anatomical keypoints on the human body, including joints such as shoulders, elbows, wrists, hips, knees, and ankles. These points are used to create a real-time digital representation of the user's movement. Instead of merely analyzing images, Gympfy interprets the mechanics of human motion, tracking the position and interaction between different bodily regions during each exercise. > This approach allows the platform to understand *how* the movement is being executed, rather than just detecting that a person is present in front of the camera. #### Repetition Validation Each exercise has specific execution standards. The platform continuously monitors body movement, calculating angles, ranges of motion (ROM), and transitions between different phases of the exercise. A repetition is only considered valid when all the defined criteria for that specific exercise are met. In this way, the system does not just count movements; it recognizes complete and consistent executions. #### Real-Time Feedback During the activity, the user receives instant visual and audio feedback. This interaction allows them to track their performance while the exercise is being performed, making the experience more dynamic, intuitive, and engaging. In addition to logging progress, the platform helps users better understand their own execution throughout the workout. #### A Reliable Foundation for Evolution Gympfy’s entire progression architecture depends on the ability to validate physical activities consistently. Experience, leaderboards, achievements, Evolution Companions, and SWEAT Points are all fueled by data generated through this technological layer. Consequently, progress within the ecosystem remains directly connected to the effort actually put in by the users. #### The Continuous Evolution of Artificial Intelligence Movement validation represents only the first step of Gympfy’s technological vision. As the ecosystem grows and new data is processed securely and responsibly, the platform will be able to incorporate advanced features such as: * In-depth biomechanical analysis; * Identification of fatigue patterns; * Injury prevention insights; * Deep personalization of the user experience. Our vision is to build a technology capable of understanding not just how many repetitions were performed, but how each person moves, evolves, and improves their health over time. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://gympfy.gitbook.io/gympfy-whitepaper/whitepaper-gympfy/the-technology-behind-the-movement.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.