> For the complete documentation index, see [llms.txt](https://sonic-ai-works.gitbook.io/sonic-networks-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://sonic-ai-works.gitbook.io/sonic-networks-docs/documentation/developers.md).

# Developers

Canonical SONIC Network v1.0.0 engineering documentation for architecture, access, Developer role, auth, frontend, AI/music, finance, mail, Solana programs and runtime operations.

Build against one SONIC platform contract rather than application-specific auth, mail or provider logic.

{% columns %}
{% column %}

### Start building

Use the quickstart, API Reference and Developer dashboard for credentials, webhooks and usage.

<a class="button primary" data-icon="bolt">Developer Quickstart</a>
{% endcolumn %}

{% column %}

### Understand the platform

Use Architecture & Runtime for identity/access, mail, workers, finance and operational correctness.

<a class="button secondary" data-icon="diagram-project">Architecture & Runtime</a>
{% endcolumn %}
{% endcolumns %}

## Developer access model

```
session
→ SONIC identity
→ workspace membership
→ DEVELOPER role / explicit permission
→ Developer entitlement
→ resource scope
→ AAL / session freshness / risk
→ operation
```

Developer role is not Admin, Owner or Finance authority.

## Recommended path

1. Developer quickstart
2. Identity, Access & Roles
3. Mail & Notification Architecture
4. Frontend & Design System
5. AI & Music
6. Finance & Protocols
7. Solana Programs

## Runtime

```
Developer Dashboard
→ /api/v1 auth/access context
→ scoped API keys + signed webhooks
→ usage / logs / request IDs
→ domain APIs
→ durable workers/providers
→ reconciliation and audit
```

Live credential changes can require fresh strong authentication even when the user already has a valid session.


---

# 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, and the optional `goal` query parameter:

```
GET https://sonic-ai-works.gitbook.io/sonic-networks-docs/documentation/developers.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.