@aotter/mantle

Umbrella entry for the Mantle SDK — a manifest-driven CMS for Cloudflare Workers, built around a 4-atom YAML model (Schema / View / Procedure / Trigger) where agents write config and the runtime carries the complexity.

v0.1.x is in development. APIs may change between minor versions.

Install

npm install @aotter/mantle@alpha
# or
pnpm add @aotter/mantle@alpha

What's inside

Adopters install this one package and import from subpaths. Sub-packages remain individually installable for tooling / alt-adapter authors.

| Subpath | Re-exports | |---|---| | @aotter/mantle/spec (or root) | Manifest grammar, validators, JSON-Schema→Zod, diagnostic catalog (no env / no IO) | | @aotter/mantle/runtime | Hexagonal runtime: domain ports, use cases, infrastructure helpers (no adapter deps) | | @aotter/mantle/cloudflare | Cloudflare Workers adapter — D1, KV, R2, Better Auth, MCP via @cloudflare/workers-oauth-provider | | @aotter/mantle/admin-ui | Pre-built React 19 admin SPA bundle |

import { parseManifestsOrThrow } from "@aotter/mantle/spec";
import { createCmsRuntime } from "@aotter/mantle/runtime";
import { mountServerEndpoints } from "@aotter/mantle/cloudflare";

Getting started

Recommended path: open the Mantle landing page, answer the launch questions, and sign in with GitHub and Cloudflare. Landing provisions the site server-side — it creates the private GitHub repo, commits a blank deployable Mantle site, and connects the first Cloudflare deploy. Then point your coding agent (Claude Code / Cursor / Codex) at the provisioned repo to continue.

Starter source and provision bundles live in aotter/mantle-starters; launch starts from the blank base and the agent applies the selected type as a post-launch overlay. See skills/install in the Mantle repo for how the agent continues a provisioned repo.

Adapter targets

| Adapter | Status | |---|---| | Cloudflare Workers | ✅ shipping | | Netlify | 📋 README stub — engineering forcing function for v0.2 (@aotter/mantle-netlify) |

The mantle-runtime package never imports Cloudflare-specific types — adapters bind concrete drivers (D1 / KV / R2) to the runtime's domain/port/* interfaces, so adding a new adapter is a port-implementation exercise, not a refactor.

Documentation

• Embedded docs and agent skills ship inside this npm package for generated-site agents:
  • node_modules/@aotter/mantle/docs/design-atoms.md
  • node_modules/@aotter/mantle/docs/adr/
  • node_modules/@aotter/mantle/skills/install/SKILL.md
  • node_modules/@aotter/mantle/skills/provision/SKILL.md
• Repo
• 4-atom manifest model (ADR-0001)
• Release process
• Issues

License

Apache-2.0