Gao Agent Builder - Studio Integration Patch

Document:* GAB/2.5 — Studio Integration Addendum Applies to: GAO Agent Builder Spec GAB/2.5 Patch Version: GAB/2.5-SI.1 Status: Normative Date: 2026-03-08

This patch is additive to GAB/2.5. All existing sections remain in force. This document inserts new content and amends Sections 2.1, 2.2, 2.3, and 5.

Patch Summary#

GAB/2.5 was written as a standalone product specification with numeric layer references. This patch formally establishes that Gao Agent Builder is not an independent product — it is the Agent Builder module embedded within Gao Studio — and replaces all numeric layer references with the canonical layer names used across the Gao Internet specification set.

Canonical layer name mapping

Old Reference

Canonical Layer Name

Layer 1 – Workspace

Operations Layer – Gao Workspace

Layer 2 – Browser

Gateway Layer – Gao Browser

Layer 3 – SDK

Developer Layer – Gao SDK

Layer 4 – Payment

Settlement Layer – Gao Payment

Layer 5 – Domain

Identity Layer – Gao Domain

Layer 6 – Network

Transport Layer – Gao Network

Layer 7 – DePIN

Infrastructure Layer – Gao DePIN

Layer 8 – AI OS

Intelligence Layer – Gao AI OS

This patch:

Amends Section 2 to reflect Studio as the containing environment and canonical layer names
Inserts Section 2.4 — Gao System SDK as mandatory intermediary
Inserts Section 2.5 — Studio entry point and navigation
Amends Section 5 to add Studio-specific normative principles
Adds Section 29 — Studio Integration Contract

Amendment to Section 1 — Purpose#

Add after first paragraph:

Studio Context: Gao Agent Builder is deployed as the Agent Builder module within Gao Studio (studio.gao). It is accessed via the Agent Builder tab inside Studio. Gao Studio is the privileged dApp running in the Operations Layer (Gao Workspace) that serves as the Control Hub for all of Gao Internet. Agent Builder does not operate as an independent entry point — its user-facing surface is always Studio.

Amendment to Section 2 — Architectural Position#

Amended Section 2.1 — Gao Internet Layer Stack

Replace the existing table with the following:

Layer Name

Role

Studio Module

Operations Layer – Gao Workspace

Operations console and agent management

Studio UI Host

Gateway Layer – Gao Browser

Gateway, client execution, approvals

Approval surfaces

Developer Layer – Gao SDK

Developer integration and tooling

Gao System SDK

Settlement Layer – Gao Payment

Settlement, receipts, budget enforcement

Payment Console

Identity Layer – Gao Domain

Root identity and authority

Domain binding

Transport Layer – Gao Network

Transport and relay

Transport Debug Console

Infrastructure Layer – Gao DePIN

Distributed compute, storage, bandwidth

Node & DePIN Console

Intelligence Layer – Gao AI OS

Standards (AIP) + runtime enforcement (GAR)

Agent Builder Runtime

Amended Section 2.2 — Position of Gao Agent Builder

Replace existing text with:

Gao Agent Builder is the Agent Builder module within Gao Studio — not a standalone product. It is an Operations Layer-native module that composes with all Gao layers and exposes a unified agent-building surface within the Studio environment.

Containment hierarchy:

Gao Internet
 └── Core Layers
      └── Operations Layer – Gao Workspace
            └── Gao Studio   ← Control Hub (privileged dApp)
                  └── Agent Builder Module   ← GAB/2.5 scope

Entry point:

studio.gao → Agent Builder tab

Execution chain from Studio:

User
 → studio.gao (Gao Studio – Operations Layer)
      → Gao System SDK          ← mandatory intermediary
           → GAR (Intelligence Layer – Gao AI OS)   ← enforcement runtime
           → Settlement Layer – Gao Payment
           → Identity Layer – Gao Domain
           → Infrastructure Layer – Gao DePIN
           → Transport Layer – Gao Network

Agent Builder must:

Use Studio as the primary UI and operations surface
Route all cross-layer calls through Gao System SDK (see Section 2.4)
Use GAR as the only valid execution enforcement layer
Never bypass Studio’s permission model or capability token system

Amended Section 2.3 — What Gao Agent Builder is not

Append to existing list:

Gao Agent Builder is not:

a standalone product with its own independent entry point
a replacement for Gao Studio
permitted to call Gao layers directly without routing through Gao System SDK

New Section 2.4 — Gao System SDK as Mandatory Intermediary#

Gao Studio mediates all cross-layer access via the Gao System SDK. This is a normative requirement that applies to all modules within Studio — including Agent Builder.

SDK Role in Agent Builder Execution

When Agent Builder initiates any cross-layer operation (agent deploy, tool call, payment intent, domain resolution, DePIN compute), the call must:

Be issued from the Agent Builder module
Pass through the Gao System SDK
Be validated by the SDK’s Capability Token Engine
Be evaluated by the SDK’s RBAC + ABAC Policy Engine
Produce an audit event via the SDK’s Audit Logger
Be forwarded to the target layer (GAR, Settlement, Identity, Infrastructure, Transport)

SDK Capability Format

All Agent Builder capability tokens follow the Gao System SDK format:

<layer>:<resource>:<action>

Examples relevant to Agent Builder:

intelligence:agent:deploy
intelligence:agent:run
intelligence:agent:suspend
intelligence:sandbox:create
intelligence:sandbox:execute
gateway:browser:create
gateway:browser:automate
settlement:intent:create
identity:record:resolve
infrastructure:compute:allocate
transport:relay:test
developer:connector:gmail:send
developer:connector:meshii:message

SDK Invariants for Agent Builder

Agent Builder may not call any layer directly — all calls route through Gao System SDK.
The SDK’s Capability Token Engine must validate every call before forwarding.
Capability tokens issued for agent execution are time-bound and domain-scoped.
Every SDK call from Agent Builder produces an immutable audit event.
SDK versioning is transparent and subject to DAO governance in decentralized mode.

Primary Access

Surface

URL

Studio primary

studio.gao

Studio fallback

gao.global/studio

Agent Builder

studio.gao → Agent Builder tab

Studio Tab Structure (relevant to Agent Builder)

Tab

GAB/2.5 Reference

Agent Builder

§6.1 – Agent Definition Studio

Prompt Builder

§6.2 – Prompt-to-Agent Composer

Tools

§6.3 – Skill and Tool Composer

Sandbox

§7 – Secure Execution Sandbox

Browser

§9 – Browser Automation Runtime

Connectors

§10 – Native Connector Registry

Models

§15 – Model Strategy

Memory

§16.5 – Memory Manager

Policies

§16.3 – Policy Profile Manager

Budget

§16.3 – Policy Profile Manager

Deployment

§6.6 – Deployment Manager

Traces

§16.6 – Audit and Trace Explorer

Receipts

§16.6 – Audit and Trace Explorer

Checkpoints

§16.4 – Runtime Session Manager

Artifacts

§25 – Artifact System

Knowledge

§26 – Knowledge Ingestion Pipeline

Scheduler

§27 – Agent Scheduling Engine

Memory Graph

§28 – Agent Memory Graph

Enterprise

§21 – Enterprise Profile

Amendment to Section 5 — Normative Product Principles#

Append the following principles to the existing list:

11. Studio-contained operation — Agent Builder operates exclusively within Gao Studio. It has no independent entry point and must not expose execution surfaces outside the Studio environment.

12. SDK-mediated cross-layer access — Every cross-layer call from Agent Builder must route through Gao System SDK. Direct layer access is prohibited regardless of the action or risk tier.

13. Studio permission inheritance — Agent Builder inherits and respects Gao Studio’s RBAC model. The Studio roles (Owner, Builder, Developer, Operator, Finance, Auditor) govern access to all Agent Builder surfaces.

New Section 23 — Studio Integration Contract#

23.1 Purpose

This section defines the normative integration contract between Gao Agent Builder (GAB/2.5) and Gao Studio (v1.1). It specifies what Studio provides to Agent Builder, what Agent Builder must expose back to Studio, and the invariants that govern their interaction.

23.2 What Studio Provides to Agent Builder

Provision

Description

UI Host

Operations Layer Workspace surface renders all Agent Builder tabs

Gao System SDK

Mandatory cross-layer call intermediary

RBAC enforcement

Studio’s role model controls Agent Builder access

Capability Token Engine

All agent capability tokens are issued via SDK

Audit Logger

All Agent Builder actions logged through Studio’s audit infrastructure

Event Bus

Cross-module events propagate via Studio event bus

Domain Authority Context

Studio provides the authenticated domain context for all agent operations

Session Management

Studio manages the authenticated user session

23.3 What Agent Builder Exposes to Studio

Exposure

Description

Agent Registry

Agent metadata queryable by Studio’s Ops Console

Trace Graph

Full execution traces displayed in Studio’s Trace Explorer

Receipts

Payment receipts and finality state surfaced in Studio’s Finance tab

Artifact Store

Artifacts accessible and promotable from Studio’s Artifact tab

Deployment State

Hosted app status visible in Studio’s Deployment tab

Memory Graph

Operational memory graph queryable from Studio’s Memory Graph tab

Scheduler Jobs

Scheduled execution jobs visible and controllable from Studio’s Scheduler tab

Budget Burn

Spend and budget state surfaced in Studio’s Budget tab

23.4 Cross-Module Call Protocol

When Agent Builder initiates a call that requires a Studio-managed resource (domain authority, payment intent, DePIN compute), the following protocol applies:

Agent Builder Module
 → Gao System SDK (call with capability token request)
     → Capability Token Engine (validate actor, domain, resource, action)
         → RBAC + ABAC Policy Engine (evaluate role and attribute constraints)
             → Audit Logger (emit pre-action event)
                 → Target Layer (Intelligence / Settlement / Identity / Infrastructure / Transport)
                     → Audit Logger (emit post-action result)
                         → Event Bus (propagate result to subscribed modules)

---

#### 23.5 Shared Data Contracts

Contract

Defined In

Shared With

`AgentManifest`

GAB/2.5 §17.1

Studio Agent Registry

`ToolContract`

GAB/2.5 §17.2

Studio Ops Console

`SkillManifest`

GAB/2.5 §17.3

Studio Skill tab

`DeploymentProfile`

GAB/2.5 §17.5

Studio Deployment tab

`SandboxProfile`

GAB/2.5 §17.6

Studio Sandbox tab

`ConnectorSet`

GAB/2.5 §17.7

Studio Connector tab

`ArtifactContract`

GAB/2.5 §25.4

Studio Artifact tab

`SchedulerJob`

GAB/2.5 §27.4

Studio Scheduler tab

`MemoryGraph`

GAB/2.5 §28.4

Studio Memory Graph tab

`CapabilityToken`

Studio Gao System SDK

Agent Builder all modules

---

#### 23.6 Studio Integration Invariants

1.  Agent Builder must never expose execution surfaces outside of Gao Studio.
    
2.  All capability tokens used by Agent Builder must be issued by the Studio Gao System SDK.
    
3.  Agent Builder’s Ops Console (GAB/2.5 §6.7) is rendered as Studio tabs — it is not a separate UI.
    
4.  Agent Builder’s audit events are consumed by Studio’s Audit Logger — no separate audit sink.
    
5.  Agent Builder may not issue domain authority grants — these must come from Studio’s Domain Authority Context.
    
6.  Upgrades to the Agent Builder module that affect the Studio integration surface require DAO approval in decentralized mode.
    
7.  The Gao System SDK version must be compatible with both Studio v1.1 and GAB/2.5 — version mismatches must be surfaced to the Auditor role before any execution proceeds.
    

---

#### 23.7 Updated Execution Pipeline (Post-Patch)

The complete v2.5 execution pipeline with Studio integration and canonical layer names:

User (authenticated via studio.gao) ↓ Gao Studio (Operations Layer – Gao Workspace) ↓ Gao System SDK (capability validation + audit) ↓ Memory Graph Retrieval (context grounding) ↓ Planner (Intelligence Layer – Gao AI OS) ↓ Policy Gate (GAR – Intelligence Layer) ↓ Execution: Sandbox / Browser Runtime / Tool Router / Connector Registry ↓ Artifact Emission → Artifact Store ↓ Knowledge Ingestion (if data sources ingested) ↓ Hosting Engine (Identity Layer – Gao Domain) ↓ Public URL + Scheduler (if recurring) ↓ Memory Graph Update + Full Audit Trail ↓ Studio Event Bus (result propagated to all subscribed Studio modules)

23.8 Pipeline-to-Layer Reference

Pipeline Component

Gao Layer

Operations console

Operations Layer – Gao Workspace

Approvals and gateway

Gateway Layer – Gao Browser

Developer tooling

Developer Layer – Gao SDK

Payment and receipts

Settlement Layer – Gao Payment

Identity and authority

Identity Layer – Gao Domain

Remote transport

Transport Layer – Gao Network

Heavy compute

Infrastructure Layer – Gao DePIN

Standards and runtime

Intelligence Layer – Gao AI OS / GAR

23.9 Competitive Note — Studio as Structural Moat

The Studio integration adds a structural moat that Agent Builder alone cannot provide:

Advantage

Description

Unified control plane

Every agent, app, domain, payment, and node managed in one privileged environment

SDK-enforced boundaries

No module — including Agent Builder — can bypass the cross-layer call contract

Role-aware UI

Studio’s RBAC model gates access to Agent Builder surfaces by organizational role

Cross-module observability

Agent traces, receipts, artifacts, and memory visible alongside DePIN nodes, governance proposals, and payment state

Single audit stream

All actions across Studio and Agent Builder feed one unified audit log

This makes Gao Studio + Agent Builder a structurally more complete system than any standalone agent builder — including Abacus DeepAgent — which has no equivalent unified control plane.

GAB/2.5-SI.1 — Studio Integration Patch Toii Labs LLC — Gao Internet Core Architecture Applies to: GAO Agent Builder Spec GAB/2.5 + GAO Studio Spec v1.1

Gao Agent Builder - Studio Integration Patch

Gao Agent Builder - Studio Integration Patch

Patch Summary#

Amendment to Section 1 — Purpose#

Amendment to Section 2 — Architectural Position#

Amended Section 2.1 — Gao Internet Layer Stack

Amended Section 2.2 — Position of Gao Agent Builder

Amended Section 2.3 — What Gao Agent Builder is not

New Section 2.4 — Gao System SDK as Mandatory Intermediary#

SDK Role in Agent Builder Execution

SDK Capability Format

SDK Invariants for Agent Builder

New Section 2.5 — Studio Entry Point and Navigation#

Primary Access

Studio Tab Structure (relevant to Agent Builder)

Amendment to Section 5 — Normative Product Principles#

New Section 23 — Studio Integration Contract#

23.1 Purpose

23.2 What Studio Provides to Agent Builder

23.3 What Agent Builder Exposes to Studio

23.4 Cross-Module Call Protocol

23.8 Pipeline-to-Layer Reference

23.9 Competitive Note — Studio as Structural Moat