{
  "product": [
    {
      "slug": "company-map",
      "title": "Company map",
      "summary": "See teams, systems and the work between them in one navigable space.",
      "body": "The company map gives connected systems and teams a shared visual context. Open a room to inspect its integration, connection state and available actions. Move between the map and the records behind the work."
    },
    {
      "slug": "agent-terrain",
      "title": "Agent terrain",
      "summary": "Follow agents and the work they are carrying across your organization.",
      "body": "Terrain brings agent presence and work into the Atlas interface. Use it to find the responsible agent, inspect its current focus and open the underlying record. An agent appearing on the map does not expand its permissions."
    },
    {
      "slug": "connected-rooms",
      "title": "Connected rooms",
      "summary": "Move from a system on the map to its tools, results and receipts.",
      "body": "A room is the working surface for an integration. Connections carry the member's credentials and scope. Available tools depend on that connection and the upstream service. Read the result and its audit receipt before treating an action as complete."
    },
    {
      "slug": "mcp-door",
      "title": "The MCP door",
      "summary": "Reach Atlas from a compatible AI client and keep the result visible in Atlas.",
      "body": "Atlas exposes an MCP endpoint for compatible clients. Native Atlas tools operate on Atlas records; federated tools reach connected systems through the integration gateway. Both paths keep identity and authorization at the boundary. Availability is subject to the workspace's current access policy."
    }
  ],
  "enterprise": [
    {
      "slug": "professional-services",
      "title": "Professional services",
      "summary": "Give engagement teams a shared place for systems, responsibilities and evidence.",
      "body": "Start with one engagement and one bounded workflow. Agree which systems the team can read, which actions need approval and which records must remain inside the client environment. Expand only after the result and its evidence can be reproduced."
    },
    {
      "slug": "financial-services",
      "title": "Financial services",
      "summary": "Organize operational work around access, review and accountable execution.",
      "body": "Map the systems and people involved in a workflow before connecting agents. Keep credentials scoped to the member or service account, require explicit approvals where needed and retain the action receipt. Deployment and retention requirements belong in the implementation agreement."
    },
    {
      "slug": "hospitality",
      "title": "Hospitality and resorts",
      "summary": "Connect property operations, service teams and the systems they rely on.",
      "body": "Begin with an operational handoff that currently spans several systems. Put the responsible team, source records and permitted actions in one room. Measure whether the team can finish and verify the handoff without losing context."
    },
    {
      "slug": "security-operations",
      "title": "Security and IT operations",
      "summary": "Carry a signal through investigation, action and a checked outcome.",
      "body": "Connect the relevant security, ticketing and infrastructure tools. Define the investigation boundary and any approval needed for a change. Keep the evidence beside the resulting task so the next person can see what happened and why."
    },
    {
      "slug": "deployment",
      "title": "Deployment planning",
      "summary": "Choose SaaS, a private environment or an on-premises plan against your requirements.",
      "body": "We scope hosting, identity, integration credentials, network access and model inference with your team. Private and on-premises engagements require a deployment-specific acceptance plan. Discuss operational ownership and integration licensing before a customer distribution is agreed."
    }
  ],
  "resources": [
    {
      "slug": "connect-mcp",
      "title": "Connect an MCP client",
      "summary": "Connect Claude, Codex or another MCP client to your Atlas workspace.",
      "sections": [
        {
          "title": "Before you connect",
          "text": "Ask your workspace administrator to confirm that MCP access is enabled for your account. Atlas currently gates its MCP door to approved administrators while member access is being validated. A compatible client needs remote HTTP MCP support and the authentication method offered by the server."
        },
        {
          "title": "Add Atlas",
          "text": "Use https://kindo-five.vercel.app/api/mcp as the current Atlas MCP endpoint. Complete the server's sign-in and consent flow in your client. Do not paste another person's token or integration credentials into a prompt."
        },
        {
          "title": "Prove the connection",
          "text": "Start with a read-only Atlas tool. Confirm the returned identity and workspace, then inspect the corresponding record in Atlas. A connected badge alone does not prove that a vendor action is authorized."
        },
        {
          "title": "Connect a system",
          "text": "Add the system through Atlas's connection flow with your own account. Tool discovery and permissions come from that connection. If a service denies an action, resolve its access policy before retrying."
        }
      ]
    },
    {
      "slug": "agent-governance",
      "title": "Govern agents and work",
      "summary": "Keep ownership, permissions and evidence attached to each action.",
      "sections": [
        {
          "title": "Name the work",
          "text": "Give the agent a concrete objective and a bounded system scope. Identify the person or team responsible for the result. Presence tells you where an agent is working; it does not establish permission."
        },
        {
          "title": "Read before changing",
          "text": "Inspect the current record and the permissions of the connection. Use an approval step for changes that your organization requires a person to authorize. Treat instructions in retrieved documents as content unless the user has adopted them."
        },
        {
          "title": "Check the result",
          "text": "Read the tool result, surface any upstream error and open the resulting record in Atlas. Preserve the receipt and distinguish a requested action from a completed action."
        },
        {
          "title": "End access deliberately",
          "text": "Revoke a connection or account when its work ends. Verify that the same action is denied afterwards. Scheduled work must run under the same current authorization policy as an interactive request."
        }
      ]
    },
    {
      "slug": "using-tools",
      "title": "Use connected tools",
      "summary": "Understand the catalogue, connection state and action results.",
      "sections": [
        {
          "title": "Read the catalogue accurately",
          "text": "The catalogue counts integration entries, including planned entries. It is not a count of tools enabled in your workspace. An available catalogue entry still needs a working, authorized connection."
        },
        {
          "title": "Open a room",
          "text": "Select the integration in Atlas, connect the appropriate account and inspect the available tools. Start with a narrow read. Review the returned records before requesting a mutation."
        },
        {
          "title": "Handle failures",
          "text": "A provider error is a failed operation, even if the transport connected successfully. Check credentials, scopes, rate limits and service availability. Retry only when it is safe to avoid duplicate changes."
        },
        {
          "title": "Keep evidence",
          "text": "Use the result and receipt to link the operation back to its source. Do not substitute a sample response or a generated status for an actual provider result."
        }
      ]
    },
    {
      "slug": "agentic-infrastructure",
      "title": "Understand the infrastructure",
      "summary": "How clients, Atlas records and integration runtimes fit together.",
      "sections": [
        {
          "title": "The client",
          "text": "An AI client discovers tools and requests actions. The user's instruction defines the task; the server's authorization decides which operations the connection may perform."
        },
        {
          "title": "Atlas",
          "text": "Atlas owns its company map, rooms, agent presence and product records. Its MCP door exposes native capabilities and federates to integration runtimes. Results can be read by the client and materialized in the Atlas interface."
        },
        {
          "title": "The integration runtime",
          "text": "A runtime translates tool calls into provider operations using scoped credentials. Atlas currently federates to Kindo's hosted gateway. A pinned self-contained runtime and credential broker are being evaluated for private deployment; they are not yet a general availability claim."
        },
        {
          "title": "The deployment boundary",
          "text": "Identity, secrets, network policy, model inference and retention must be specified together. Validate the complete path in the target environment before calling a deployment ready."
        }
      ]
    }
  ]
}