# Describe the workflow. Ship the service.

Mantle turns a YAML Manifest into a typed service. Core compiles your data model and operations into a RuntimePlan; your chosen adapter connects it to storage and exposes supported APIs.

| Atom | Purpose |
|---|---|
| Schema | Stored data, indexes and lifecycle. |
| View | A named read over a Schema. |
| Procedure | Business logic with typed inputs and outputs. |
| Trigger | An entry point to a Procedure: HTTP, MCP or a lifecycle hook. |

## Choose your runtime

Mantle runs on Cloudflare, Bun, Vercel Functions and in the browser. **Their integrations differ**; choosing an adapter does not enable every Mantle feature.

| Host / adapter | Storage | What you get |
|---|---|---|
| **Cloudflare Workers** | D1 | REST and HTTP Triggers, plus integrations for Admin, Auth, MCP, public web and cache. Optional R2 and Queues. |
| **Bun** | Your `bun:sqlite` database | Runtime, REST and HTTP Triggers. Your app owns the server, auth and other integrations. |
| **Vercel Functions** | An injected storage adapter; optional libSQL / Turso driver | Runtime, REST and HTTP Triggers, with platform `waitUntil`. Your app owns auth and route composition. |
| **Browser / IndexedDB** | An application-owned browser database | Direct runtime calls for local apps and previews. No mounted HTTP, Admin, Auth or MCP endpoints; SQL Views are unsupported. Sync is application-owned. |

Core shares the Manifest model and execution pipeline across these adapters. Check the [capability matrix and setup examples](./concepts/runtime-and-adapters.md#capability-matrix) before choosing a host. The Worker quickstart below follows the Cloudflare path.

## Start building

- **With code:** [Run a minimal Worker](./start/quickstart-worker.md), then follow the [project layout and CLI loop](./start/project-and-cli.md).
- **With an agent:** [Design and preview in Builder](./start/builder.md), then download a handoff ZIP for your coding agent.

You own the project files and `manifests/`. `mantle generate` compiles existing manifests; it does not scaffold a project or fetch a Starter.

## Find the details

| Need | Read |
|---|---|
| Model a workflow | [The four atoms](./concepts/four-atoms.md), [reads](./concepts/views.md), [writes and hooks](./concepts/procedures-and-triggers.md) |
| Control access | [Authorization](./concepts/authorization.md), [MCP and agents](./concepts/mcp-and-agents.md) |
| Ship on Cloudflare | [Worker composition](./cloudflare/conventional-worker.md), [authentication](./cloudflare/authentication.md), [deploy and operate](./cloudflare/deploy-and-operate.md) |
| Build public pages | [Templates, SEO and cache](./cloudflare/public-web.md) |
| Follow an example | [Intake](./examples/intake-form.md), [publication](./examples/publication.md), [reservation](./examples/reservation.md), [commerce](./examples/commerce-transaction.md) |
| Look up syntax or APIs | [Manifest reference](./reference/manifest.md), [HTTP, MCP, CLI and packages](./reference/surface.md) |

The sidebar contains the full handbook.

## How mantle-home is built

This site combines renderers according to the page's needs:

| Surface | Rendering |
|---|---|
| Homepage and Builder shell | Hono JSX generates HTML at build time. |
| Blog | `mantle-web` composes content and SEO; the site's templates render HTML on request using the shared Hono JSX shell. |
| Interactive Builder and Admin preview | React loads when needed. Builder projects and preview data stay in browser IndexedDB. |
| Documentation | VitePress generates static pages from the Core handbook and this site's introduction. |

Hono JSX keeps the public shell renderable without loading the editor; React handles the interactive workspace. Shared styles and header/footer components keep them consistent. Kiwa supplied some copied components, not the site's runtime framework.

These are **mantle-home's choices**. Mantle Core does not require Hono JSX, React or VitePress; your application owns its frontend and templates.

## Versions and agent access

These docs cover an **unreleased development snapshot**. The site's SDK and handbook are source-pinned to Core `f43ebfd` (`0.1.2-alpha.1`). The footer links to that exact handbook revision. Use [version-matched guidance](./reference/surface.md#versions) for npm installs.

Every page has a Markdown mirror, including <a href="/docs/index.md" download>this page</a>. Agents can start from the [documentation index](/llms.txt).