diff --git a/.github/pr-assets/what-tangle-is/infra-after-desktop.png b/.github/pr-assets/what-tangle-is/infra-after-desktop.png new file mode 100644 index 0000000..26b29ba Binary files /dev/null and b/.github/pr-assets/what-tangle-is/infra-after-desktop.png differ diff --git a/.github/pr-assets/what-tangle-is/infra-after-mobile.png b/.github/pr-assets/what-tangle-is/infra-after-mobile.png new file mode 100644 index 0000000..97d76ff Binary files /dev/null and b/.github/pr-assets/what-tangle-is/infra-after-mobile.png differ diff --git a/components/LandingPage.tsx b/components/LandingPage.tsx index 2296524..2984299 100644 --- a/components/LandingPage.tsx +++ b/components/LandingPage.tsx @@ -12,26 +12,18 @@ const startingPoints = [ description: "Route model requests through one API.", href: "/gateway", }, - { - name: "Agent Builder", - state: "Hosted-assistant preview", - description: - "Planned hosted path for assistant creation and approved channels.", - href: null, - }, ]; const LandingPage = () => { return (

- Build and run assistants on Tangle + Build and run AI agents on Tangle

- Tangle provides isolated sandboxes, agent runtime, model routing, - integrations, and evaluation tools. Agent Builder is becoming the hosted - path for creating an assistant and connecting approved channels. That - hosted path is in preview while Builder adopts the shared kit. + Tangle provides five layers for AI agents: Sandbox, Runtime, Router, + Integrations, and observability through Intelligence. Evaluation is part + of each layer and the products built on them.

@@ -39,7 +31,7 @@ const LandingPage = () => { id="start-here" className="text-2xl font-semibold text-gray-900 dark:text-white" > - Choose where to start + Start with a live service
-

- The hospitality preview is designed to turn a guest message into an - assigned task and bring overdue work to a person. The complete - request-to-resolution flow is still being verified with a design - partner. -

+
+

+ Hosted assistants are a preview +

+

+ Tangle's first packaged use case is a hospitality assistant. + Agent Builder is expected to provide the creation and approved channel + setup path. The first completed text reply and full + request-to-resolution flow have not yet been verified. +

+

- For an in-browser coding workspace, see the{" "} + See how the five layers fit in the{" "} + + infrastructure architecture + + . For an in-browser coding workspace, see the{" "} - Build, run, improve loop -

- Build, run, improve loop: workbench -> sandbox runtime -> protocol (payments + - evaluation). -
- - -**Flow:** design -> execute -> evaluate -> pay. Each run captures evaluation metadata that reviewers and later runs can draw on. - -## What Runs Where - -| Layer | Runs here | Examples | -| --------------- | ----------------------------- | -------------------------------------------------------- | -| Workbench | Human and agent collaboration | Workflows, profiles, simulations, reviews | -| Gateway | Inference routing and billing | Model access, BYOK, ZDR compliance, operator selection | -| Sandbox runtime | Executed tasks and tools | Agent sessions, tool calls, file edits | -| Protocol | Coordination and settlement | Service registry, operator payments, staking, incentives | - -## The Four Layers - -**1) Execution Layer** -Sandboxed runtimes with isolation, resource limits, and audit logs. This is where tasks actually run. - -**2) Inference Layer** -The [Gateway](/gateway) routes inference requests across provider APIs and registered operators. It handles model selection, compliance filtering ([ZDR](/gateway/zdr), [no-train](/gateway/no-train)), [BYOK](/gateway/byok) credential management, and billing. - -**3) Protocol Layer** -The coordination plane. It handles operator discovery, payment routing, and incentive enforcement. - -**4) Experience Layer** -The Blueprint Agent and [Blueprint SDK](https://github.com/tangle-network/blueprint/tree/main). This is where teams design workflows, run simulations, and ship services. - -The SDK also includes optional gateways for integrating external events and payment-driven HTTP job execution (webhooks, -x402). - -## Interfaces and Integration Points - -Not every service fits a pure on-chain request flow. Tangle supports multiple integration styles: - -- On-chain triggers: jobs and services can be created and invoked through protocol transactions. -- External triggers: operators can expose HTTP ingress (webhooks) that translate external events into job executions. -- Alternative settlement: operators can optionally accept paid HTTP job calls via x402 (stablecoin settlement on EVM - chains), then translate them into job executions. -- Multi-tenant APIs: when services expose off-chain HTTP or gRPC endpoints, operators can front them with an auth proxy - that injects tenant identity and enforces scopes. - -Developer references: - -- Job triggers map: `/developers/blueprint-runner/job-triggers` -- Webhooks: `/developers/blueprint-runner/webhooks` -- x402: `/developers/blueprint-runner/x402` -- Auth proxy: `/developers/blueprint-auth` - -## Trust and Delegation - -Agents only reach production when delegation is safe. Tangle enforces policy gates before execution, emits logs and execution metadata for every run, and keeps results reviewable so teams can decide what reaches production. - -## What we optimize for - -- **Isolation first**: Every workload runs inside a sandbox with explicit permissions. -- **Reviewable outcomes**: Logs, metadata, and evaluations give reviewers evidence about what ran and how it performed. -- **Composable services**: Blueprints define reusable services that can be instantiated on demand. -- **Economic alignment**: Operators and developers earn based on usage and reliability. -- **Developer speed**: Workflows are testable, repeatable, and easy to ship. +# Infrastructure Architecture + +Tangle builds five infrastructure layers for AI agents. +Products and research systems use the same layers. +Evaluation belongs inside each layer and product. + +| Layer | Responsibility | Start here | +| ---------------------------- | ---------------------------------------------------------------------------------- | ------------------------------------------------------------------ | +| Sandbox | Give an agent an isolated computer with files, a shell, and browser access. | [Sandbox](/sandbox) | +| Runtime | Control agent sessions, execution, and streaming events in sandboxes. | [Runtime](/infrastructure/introduction) | +| Router | Send model requests to supported providers or explicitly selected operator routes. | [Router](/gateway) | +| Integrations | Connect agents to supported tools, data, and external events. | [Protocol job triggers](/developers/blueprint-runner/job-triggers) | +| Observability (Intelligence) | Collect traces so teams can inspect runs and compare changes. | [Intelligence](/intelligence) | + +An application can start a session through Runtime in a Sandbox. +The agent can call models through Router and use integrations permitted by that application. +Intelligence can record the run's trace. +Evaluation can check execution, routing, tool use, and the resulting product behavior against the evidence each surface produces. + +## Products and research + +The product lab builds Agent Builder, Braid, vertical apps, and hosted assistants on this infrastructure. +Hosted assistants are the first packaged use case and remain a preview. +The first completed text reply and request-to-resolution flow have not yet been verified. +The research lab uses the same infrastructure for discovery and the software factory. + +## Managed and operator paths + +The managed [Sandbox](/sandbox) and [Router](/gateway) services are live. +Standard Router requests use supported provider APIs. +An operator-pinned or SpendAuth request can use a registered operator route. +The [protocol](/network/overview) separately supports operator-hosted Blueprint services and on-chain settlement. +That path requires a registered service instance and a reachable operator endpoint. +Access to a managed service does not establish an operator service or an on-prem installation. + +Tangle plans to offer infrastructure that can be hosted on-prem. +These docs do not provide an on-prem installation path today. diff --git a/pages/vision/core-concepts.mdx b/pages/vision/core-concepts.mdx index 8f3adb5..c2fd68d 100644 --- a/pages/vision/core-concepts.mdx +++ b/pages/vision/core-concepts.mdx @@ -3,10 +3,14 @@ Definitions for the terms used throughout Tangle's docs. - **Blueprint Agent**: An in-browser IDE where you describe a project and an AI agent builds it with you. -- **Sandbox runtime**: The isolated execution environment where agents and services run in isolation from the host and each other. +- **Sandbox**: An isolated computer for agent work. +- **Runtime**: The session and execution controls for agents running in sandboxes. +- **Router**: The model request path for supported providers and explicitly selected operator routes. +- **Integrations**: Connections between agents and supported tools, data, or external events. +- **Intelligence**: Observability for inspecting traces and comparing agent runs. - **Agent**: An AI worker running inside a sandbox. - **Agent profile**: A configuration that defines models, tools, budgets, and policies for an agent. -- **Evaluation**: A structured assessment of task results, cost, and policy compliance. +- **Evaluation**: A structured assessment of task results, cost, or policy compliance, built into layers and products. - **Simulation run**: A multi-variant evaluation of an agent or workflow across many tasks. - **Blueprint**: A reusable service template that defines interfaces, execution requirements, and expected outputs. - **Service instance**: A live deployment of a Blueprint, launched on demand and run by operators. diff --git a/pages/vision/introduction.mdx b/pages/vision/introduction.mdx index c0cc92c..6c45dc2 100644 --- a/pages/vision/introduction.mdx +++ b/pages/vision/introduction.mdx @@ -1,32 +1,34 @@ -# Build and run assistants on Tangle +# Tangle builds infrastructure for AI agents -Tangle builds hosted AI assistants for businesses, starting with hospitality. -The hospitality preview is designed to turn a guest message into an assigned task and bring overdue work to a person. -The complete request-to-resolution flow is still being verified with a design partner. +Tangle provides five infrastructure layers: Sandbox, Runtime, Router, Integrations, and observability through Intelligence. +Evaluation belongs inside each layer and each product. +Tangle's product and research labs use the same infrastructure. -Developers use Tangle's [Sandbox](/sandbox), [Router](/gateway), agent runtime, integrations, and evaluation tools to build and run agents. -Agent Builder is becoming the hosted path for creating an assistant and connecting approved channels. -That hosted path is in preview while Builder adopts the shared kit. +Developers can start with the live [Sandbox](/sandbox) and [Router](/gateway) services. +The [architecture page](/vision/architecture) explains the five layers and the separate protocol path for operator-hosted services. -## What exists today +## The five layers -- **Sandbox:** an isolated computer for an agent, with files, a shell, and browser access. -- **Router:** one API for model requests across supported providers. -- **Intelligence:** traces and comparisons that help a person inspect an agent run and evaluate a change. -- **Blueprint Agent:** an [in-browser coding workspace](/blueprint-agent/introduction) for building projects with an AI agent. -- **Platform:** one account, API keys, and a shared balance for supported services. +- **[Sandbox](/sandbox):** isolated computers for agent work. +- **[Runtime](/infrastructure/introduction):** sessions and execution control for agents in those sandboxes. +- **[Router](/gateway):** model requests across supported providers and explicit operator routes. +- **Integrations:** connections to supported tools, data, and external events. +- **[Intelligence](/intelligence):** traces and comparisons for inspecting runs and measuring changes. -The hosted assistant offer uses these shared components. -A live component does not establish that the complete hosted assistant workflow is ready. +Evaluation uses evidence from these layers to test behavior and changes. +It is part of the infrastructure and its products, rather than a separate infrastructure layer. -## Who this is for +## Products built on the infrastructure -- **Business operators** evaluating the hospitality assistant preview. -- **Developers** running agents in [Sandbox](/sandbox) or building a hosted assistant in Agent Builder. -- **Teams** inspecting run evidence in [Intelligence](/intelligence). +The product lab uses these layers for Agent Builder, Braid, vertical apps, and hosted assistants. +The research lab uses them for discovery and the software factory. +The hosted assistants are the first packaged use case, starting with hospitality. +Agent Builder is expected to provide the hosted creation and approved-channel setup path. +The first completed text reply and request-to-resolution flow have not yet been verified. +The hosted assistant remains a preview. -## Where it goes +## Deployment boundaries -The first acceptance proof is a real hospitality request completed from message through task assignment, follow-up, and human escalation when needed. -The protocol is a separate long-term path for operator-hosted services and on-chain settlement. -The managed Sandbox and Router services are live today. +Managed Sandbox and Router services are live today. +The [protocol](/network/overview) supports a separate path for operator-hosted Blueprint services and on-chain settlement. +The company plans a hostable on-prem option for infrastructure; these docs do not present an available installation path. diff --git a/pages/vision/use-cases.mdx b/pages/vision/use-cases.mdx index afa3ae5..6c6eaad 100644 --- a/pages/vision/use-cases.mdx +++ b/pages/vision/use-cases.mdx @@ -1,41 +1,36 @@ # Use Cases -Teams build these products on Tangle when work needs isolation, auditability, and paid execution. These examples show how the workbench, sandbox runtime, and protocol fit together. +Teams use Tangle's infrastructure for isolated execution, model routing, integrations, and run evidence. +Protocol-backed services add an operator and settlement path when a service needs one. ## Agentic Software Engineering Run background agents that build features, refactor code, write tests, and open pull requests. Work stays isolated and reviewable. Good for: product teams using the workbench with strict review gates. -Layers: workbench + runtime. ## Evaluation and Governance Pipelines Execute large evaluation suites across prompts, models, and tools. Each run produces structured metrics so teams can track regressions and enforce policies. Good for: AI builders who need repeatable evaluations and policy enforcement. -Layers: workbench + runtime. ## Regulated and Sensitive Workflows Deploy AI workflows on protected data with strict isolation, resource limits, and audit logs. Outputs are linked to run metadata so reviewers can inspect what happened. Good for: regulated teams that require strong isolation and auditability. -Layers: runtime + protocol (for paid operators). ## Data and Knowledge Operations Use Blueprints to run extraction, transformation, labeling, and retrieval jobs. Operators provide compute while the protocol coordinates payments and accountability. Good for: teams turning knowledge work into reliable, reusable services. -Layers: [Blueprint SDK](https://github.com/tangle-network/blueprint/tree/main) + protocol. ## AI Ops and Reliability Operate autonomous monitoring, cost optimization, and incident response workflows. Operators are paid for uptime and performance, while services can enforce reliability targets. Good for: operators and infrastructure engineers running long-lived services. -Layers: runtime + protocol. ## Marketplace-Ready AI Services Package an agent workflow or infrastructure service as a Blueprint, publish it once, and let others instantiate it on demand. Payments flow to operators and developers based on usage. Good for: builders who want distribution without running their own infrastructure. -Layers: [Blueprint SDK](https://github.com/tangle-network/blueprint/tree/main) + protocol. Some services also expose HTTP-first integration points, such as webhooks for event triggers or x402 for paid job calls. diff --git a/theme.config.tsx b/theme.config.tsx index cde32c2..dc821c9 100644 --- a/theme.config.tsx +++ b/theme.config.tsx @@ -16,9 +16,9 @@ function Head() { // Set default values for title and description const defaultTitle = "Tangle Docs"; - const tabTitle = "Tangle Docs - Assistants and Developer Tools"; + const tabTitle = "Tangle Docs - AI Agent Infrastructure"; const defaultDescription = - "Build assistants with Tangle's hosted preview, Sandbox, and Router."; + "Build and run AI agents with Tangle Sandbox, Runtime, Router, Integrations, and Intelligence."; // Get the title and description from the front matter, or use the default values const title = frontMatter.title