Studio Architecture

Architectural Position#

Layer Mapping

Gao Layer

Interaction Surface in Studio

Operations Layer – Gao Workspace

UI Host — Studio lives here

Gateway Layer – Gao Browser

Debug console, approval surfaces, gateway control

Developer Layer – Gao SDK

Gao System SDK, tool schemas, connector plugins

Settlement Layer – Gao Payment

x402 invoice generation, merchant setup

Identity Layer – Gao Domain

Domain binding, DNS record configuration

Transport Layer – Gao Network

Transport testing, relay log, cross-chain simulation

Infrastructure Layer – Gao DePIN

Node registry, monitoring, reward analytics

Intelligence Layer – Gao AI OS

Agent Builder runtime, GAR enforcement

Control Hub Diagram

flowchart TB
 U[User / Builder] --> W[Operations Layer: Gao Workspace]
 W --> S[Gao Studio]
 S --> SDK[Gao System SDK]
 SDK --> ID[Identity Layer – Gao Domain]
 SDK --> PAY[Settlement Layer – Gao Payment]
 SDK --> DEV[Developer Layer – Gao SDK]
 SDK --> NET[Transport Layer – Gao Network]
 SDK --> DEP[Infrastructure Layer – Gao DePIN]
 SDK --> AI[Intelligence Layer – Gao AI OS / GAR]
 SDK --> AUDIT[Audit Log]
 SDK --> POLICY[Policy Engine]

System Architecture#

Gao System SDK

All cross-layer interactions in Gao Studio are mediated through a single mandatory intermediary:

Gao System SDK

This is not an optional integration point. Studio modules have no direct access to smart contracts, infrastructure APIs, or layer internals. Every call must route through the SDK.

SDK Components

Component

Responsibility

Capability Token Engine

Issues and validates scoped capability tokens per action

RBAC + ABAC Policy Engine

Evaluates role-based and attribute-based access control

Audit Logger

Records all privileged actions with actor, timestamp, and trace ID

Event Bus

Propagates cross-layer events to subscribed modules

Cross-layer Connectors

Typed interfaces for each Gao layer

SDK Invariants

Studio may not call any layer directly — all calls must pass through Gao System SDK.
Every SDK call produces an audit event.
Capability tokens issued by the SDK are time-bound and domain-scoped.
SDK versioning is transparent and subject to DAO governance in decentralized mode.