> For the complete documentation index, see [llms.txt](https://permawebdao-whitepaper.gitbook.io/permawebdao/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://permawebdao-whitepaper.gitbook.io/permawebdao/5.-open-stack.md). # 5. Open Stack The Open Stack is PermawebDAO’s unified entrypoint for developers. It exposes permanent data capabilities, the long-lifecycle runtime, the unified semantic layer, and application network features through a practical toolkit and interface suite. With the Open Stack, developers do not need to manage block structures, storage details, or indexing workflows directly. Instead, they build around stable SDKs, APIs, and reference components—accelerating product iteration and launches while remaining within protocol constraints and long-term verifiability. Its three core roles are: * Abstracting the permanent data facility and unified semantic layer into typed, versioned developer interfaces. * Providing consistent access and state management for Web frontends and contracts/agents. * Offering reusable templates and best practices for trading, content, governance, AI services, and more. #### 5.1 SDK Suite PermawebDAO provides multi-language SDKs as the primary toolkit for developers integrating with the ecosystem. The SDKs encapsulate the permanent data facility, unified semantic layer, and upper-layer modules (trading, governance, content, etc.), so developers can work with records and objects rather than low-level transactions and storage. Key characteristics: * Type safety and semantic consistency:\ All core objects (records, assets, accounts, content, governance units, etc.) are exposed as strongly-typed structures aligned 1:1 with the unified semantic model, avoiding ambiguity from inconsistent formats. * Explicit versions and backward compatibility:\ Interfaces and data structures carry version information; compatibility strategies allow handling legacy and new objects in the same codebase without breaking existing logic. * Unified read/write paths:\ SDKs provide high-level read/write operations against the permanent data facility and execution environments, abstracting away gateways, nodes, and execution backends to ensure consistent behavior across deployment contexts. * Security and signing standards:\ All state-changing and asset-related operations follow standardized signing, authorization, and replay protection rules at the SDK layer, reducing security risks from improper usage. On top of this, specialized extensions are provided: * Web/TypeScript SDK for frontends * Server-side SDKs for backend services and agents * Read-only SDKs for strategy engines and analytics systems All share the same object model and semantics, ensuring consistent developer experience across environments. #### 5.2 API Layer and Service Interfaces The API layer serves participants who cannot or prefer not to integrate SDKs directly, or who require service-style access. It abstracts the permanent data facility and indexing services into stable query and submission endpoints, and provides dedicated interface sets for the trading system and governance modules. Two main API categories: * Query and analytics APIs:\ Object- and relation-oriented queries—for example: * Transactions by account, asset, time range, and data domain * Media and interaction data by content object and tags * Governance history by proposal, module, or execution status * All queries use the unified semantic model to guarantee consistency across apps and versions. * Submission and execution APIs:\ Accept operation requests from UIs, services, or agents; normalize them into internal records and execution calls; and return deterministic results with record references. Permissions, parameter checks, and risk constraints are enforced at the protocol level. The API layer gives hosted services, analytics platforms, compliance/audit systems, and multi-chain gateways a standard way to integrate with PermawebDAO without understanding low-level details. #### 5.3 Developer Tools and Templates To lower the barrier to building long-lived applications on PermawebDAO, the Open Stack offers a set of supporting tools and templates covering local development, testing, and deployment. Core components: * CLI tools:\ For project initialization, schema management, type generation, frontend deployment, application metadata registration, and basic checks against the permanent data facility. * Local and testnet environments:\ Semantically aligned with mainnet to simulate record writes, indexing behavior, clearing/settlement flows, and governance processes—allowing developers to validate long-term compatibility and replayability before launch. * Reference templates and example apps:\ Ready-to-run projects for common scenarios (trading submodules, content publishing/subscription, governance dashboards, AI agent service interfaces) that demonstrate correct use of the permanent data facility, semantic layer, and Open Stack interfaces. * Monitoring and debugging tools:\ Visual and logging tools for record streams, event streams, and index views, helping identify issues like state inconsistencies, semantic mismatches, or clearing anomalies in complex applications. Together, these tools define a standardized engineering workflow: from schema definitions and runtime configuration to interface integration and governance linkage—without requiring teams to build infrastructure from scratch. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://permawebdao-whitepaper.gitbook.io/permawebdao/5.-open-stack.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.