@aotter/mantle 0.0.11-alpha.41 → 0.0.11-alpha.43

package/docs/design-atoms.md

@@ -148,11 +148,12 @@ admin UI surfaces the child only as locale tabs in the parent's editor.
 
 #### Lifecycle
 
-**`spec.lifecycle: 'simple' | 'editorial'`** — controls the entry's
-state machine.
+**`spec.lifecycle: 'simple' | 'editorial' | 'none'`** — controls the
+entry's state machine.
 
 - `simple` (default) — `draft → published → archived`. No approval
-  queue. **This is the only mode whose runtime ships in v0.1.0.**
+  queue. **This is the only content-workflow mode whose runtime ships
+  in v0.1.0.**
 - `editorial` — the six-state machine with an approval queue
   (`draft → review → approved → scheduled → published → archived`,
   with `published` returnable to `draft` for republish). **Grammar
@@ -161,10 +162,20 @@ state machine.
   with the diagnostic `LIFECYCLE_NOT_IN_V010` and a message
   pointing at the v0.1.x roadmap. Authors should not write
   `lifecycle: editorial` in v0.1.0 manifests; it will fail boot.
-
-The two modes are **per-Schema and mix freely** within a site. There
-is no site-wide lifecycle setting; one Schema can be `simple` while
-another is `editorial`.
+- `none` — **operational records**, not authored content: orders,
+  inventory snapshots, grant/audit rows — anything written by
+  Procedures as a side effect rather than drafted by a person. No
+  content workflow applies: entries are live (`published`) the moment
+  they are created, are editable in place regardless of status, and
+  have **no** publish / unpublish / archive transitions (all reject
+  with `CONFLICT`). The admin console renders these collections flat —
+  no draft/published filter buckets, no publish controls. Declare it
+  on any Schema whose rows a human should *inspect and correct*, never
+  *stage and publish*.
+
+The modes are **per-Schema and mix freely** within a site. There is no
+site-wide lifecycle setting; one Schema can be `simple` while another
+is `editorial` and a third is `none`.
 
 **Property-level extensions** (JSON Schema vendor keywords, all optional):
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@aotter/mantle",
-  "version": "0.0.11-alpha.41",
+  "version": "0.0.11-alpha.43",
   "description": "Umbrella entry for @aotter/mantle. Adopters install this one package and import from subpaths: /spec, /runtime, /cloudflare, /admin-ui. Sub-packages remain individually installable on npm for tooling / alt-adapter authors. The Netlify adapter ships as a private workspace stub in v0.1 — its subpath will be added when the impl lands in v0.2.",
   "license": "Apache-2.0",
   "homepage": "https://mantle.tools/",
@@ -47,20 +47,20 @@
     "README.md"
   ],
   "dependencies": {
-    "@aotter/mantle-cloudflare": "0.0.11-alpha.41",
-    "@aotter/mantle-runtime": "0.0.11-alpha.41",
-    "@aotter/mantle-admin-ui": "0.0.11-alpha.41",
-    "@aotter/mantle-spec": "0.0.11-alpha.41"
+    "@aotter/mantle-admin-ui": "0.0.11-alpha.43",
+    "@aotter/mantle-runtime": "0.0.11-alpha.43",
+    "@aotter/mantle-spec": "0.0.11-alpha.43",
+    "@aotter/mantle-cloudflare": "0.0.11-alpha.43"
   },
   "peerDependencies": {
-    "@cloudflare/workers-oauth-provider": "^0.7.0",
+    "@cloudflare/workers-oauth-provider": "^0.8.0",
     "aws4fetch": "^1.0.20",
     "better-auth": "^1.6.23",
     "hono": "^4.12.0",
     "zod": "^4.0.0"
   },
   "devDependencies": {
-    "@cloudflare/workers-oauth-provider": "^0.7.0",
+    "@cloudflare/workers-oauth-provider": "^0.8.0",
     "@types/node": "^25",
     "aws4fetch": "^1.0.20",
     "better-auth": "^1.6.23",

package/skills/develop/SKILL.md

@@ -4,7 +4,7 @@ description: Work on any Mantle project using the Core SDK contract. Use for man
 source: "@aotter/mantle"
 sourcePath: skills/develop/SKILL.md
 when_to_invoke: |
-  Working dir contains a Mantle project: package.json depends on @aotter/mantle or @aotter/mantle-*, and manifests/ or src/mantleConfig.ts exists.
+  Working dir contains a Mantle project: package.json depends on @aotter/mantle or @aotter/mantle-*, and manifests/ or src/mantle/config.ts exists. Legacy projects may still use src/mantleConfig.ts.
 applies_to: mantle@v0.1.0
 ---
 
@@ -17,7 +17,7 @@ owns the workflow vocabulary.
 ## First Read
 
 1. `package.json` for the installed `@aotter/mantle*` versions.
-2. `manifests/` and `src/mantleConfig.ts` for the active atoms and adapter wiring.
+2. `manifests/` and `src/mantle/config.ts` for the active atoms and adapter wiring. If the project is older, check `src/mantleConfig.ts`.
 3. Optional local context: `.mantle/launch-state.json`, `.mantle/handoff.md`,
    `.mantle/plugins.json`, `.mantle/plugins.lock.json`, and `.mantle/recipes/`.
 4. Installed Core docs in `node_modules/@aotter/mantle/docs/`.

package/skills/install/SKILL.md

@@ -45,7 +45,8 @@ A landing-provisioned repo carries its launch context and ground truth in:
 | `.mantle/features.json` | Starter launch context and applied starter state |
 | `.mantle/handoff.md` | The launch handoff note written for you |
 | `manifests/*.yaml` | Schemas / Views / Procedures / Triggers |
-| `src/mantleConfig.ts` | Site defaults, handler registration, runtime bindings |
+| `src/mantle/config.ts` | Site defaults, runtime bindings |
+| `src/mantle/handlers/index.ts` | Procedure handler registration |
 | `src/handlers/` | Handler implementations |
 | `AGENTS.md` | Cross-tool agent entry |
 | `.agent/skills/` + `.claude/skills/` | Vendored Core skills from `@aotter/mantle`: `mantle:develop`, `mantle:plugin`, `mantle:theme`, `mantle:update` |

package/skills/plugin/SKILL.md

@@ -51,7 +51,7 @@ stop and ask for the recipe instead of guessing.
 
 1. `package.json` for Mantle version and adapter package.
 2. `manifests/` for current atom names and route/tool collisions.
-3. `src/mantleConfig.ts` for registered handlers, templates, and optional ports.
+3. `src/mantle/config.ts` and `src/mantle/handlers/` for registered handlers, templates, and optional ports. Older projects may use `src/mantleConfig.ts`.
 4. `.mantle/plugins.json` and `.mantle/plugins.lock.json` if present.
 5. `.mantle/launch-state.json` only as context, not as plugin authority.
 

package/skills/theme/SKILL.md

@@ -16,7 +16,7 @@ tokens, or recipes, but the skill contract is Core-owned.
 ## First Read
 
 1. `.mantle/handoff.md` and `.mantle/recipes/` if present.
-2. `styles/`, `components/`, `src/home.tsx`, `src/theme*`, and `kiwa-ui.json`
+2. `styles/`, `components/`, `src/web/`, `src/theme*`, and `kiwa-ui.json`
    if present.
 3. `manifests/` to understand which content shape drives the public UI.