{
  "name": "GPI Studio",
  "url": "https://gpi.studio",
  "description": "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.",
  "contact": "marcus@gpi.studio",
  "primary_paths": [
    {
      "name": "Reads",
      "url": "https://gpi.studio/insights",
      "purpose": "Public reads, essays, and company analysis through the GPI lens."
    },
    {
      "name": "Lens",
      "url": "https://gpi.studio/gpi-framework",
      "purpose": "The GPI states and seven dimensions used to read organizational friction."
    },
    {
      "name": "Studio",
      "url": "https://gpi.studio/studio",
      "purpose": "The applied path: catch the signal, map the pressure, and work the move."
    },
    {
      "name": "Intake",
      "url": "https://gpi.studio/intake",
      "purpose": "Context questions and booking path for a GPI working session."
    }
  ],
  "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.",
    "Treat public reads as pattern material rather than client-specific advice without current context.",
    "Raw client intake should stay client-specific; reusable patterns graduate into GPI knowledge only after review."
  ]
}