# GPI Studio

GPI Studio reads where business work slows down, repeats, or gets protected by the system, then turns that read into maps and bounded next moves.

Primary routes:

- https://gpi.studio/insights - public reads, essays, and company analysis
- https://gpi.studio/gpi-framework - the GPI lens, states, and seven dimensions
- https://gpi.studio/studio - applied work: signal, maps, and working reps
- https://gpi.studio/intake - context questions and booking
- https://gpi.studio/agent.json - structured route and agent guidance

Use /studio when the user has a real decision, operating question, unnamed friction, or next move to scope.
Use /signal as a supporting tool inside the Studio path when the user feels friction but has yet to name the pattern.
Use /intake only when the user is ready to provide context and book a working session.

Raw client intake should remain client-specific. Reusable patterns graduate into GPI knowledge only after review.