@akanjs/cli 1.0.19 → 2.1.0-rc.0

package/guidelines/modelDocument/modelDocument.instruction.md

@@ -0,0 +1,29 @@
+# model.document.ts Guideline
+
+## Purpose
+Generate persistence behavior for a collection-backed Akan module. This file turns constant types into stored documents, query helpers, indexes, hooks, and model-level database helpers.
+
+## Ownership
+- Define `ModelFilter` with `from(cnst.Model, (filter) => ({ query, sort }))` for reusable list and lookup conditions.
+- Define `Model` with `by(cnst.Model)` for behavior of one loaded document.
+- Define `ModelModel` with `into(Model, ModelFilter, cnst.model, () => ({ ... }))` for collection-level helpers and schema options.
+- Document methods should mutate `this`, use `this.set(...)` for multi-field changes, and return `this` for chaining.
+- Model helpers should coordinate database lookups that are reused by services.
+
+## Current Akan Patterns
+- Query names become generated helpers such as list, find, pick, exists, count, and insight variants.
+- Use filter args for required query inputs and optional args only when absence has a clear query meaning.
+- Use schema indexes for fields that are frequently filtered, sorted, uniquely constrained, or text searched.
+- Use hooks for persistence lifecycle behavior that must always run with document saves.
+
+## Codegen Rules
+- Do not put API guards, page-specific fetch behavior, or UI state in document files.
+- Do not duplicate built-in all/latest/oldest behavior unless a business-specific sort is required.
+- Keep document methods small and deterministic; put cross-document workflows in service.
+- Index only query paths that are actually used by documented filters or lookups.
+
+## Review Checklist
+- The instruction points to current docs pages, not removed docs routes.
+- Generated examples use current Akan builder APIs and scanner-friendly filenames.
+- The output contract tells the model which file paths to return.
+- The guide avoids broad framework essays when a concrete file rule is better.

package/guidelines/modelService/modelService.generate.json

@@ -0,0 +1,37 @@
+{
+  "title": "Model Service",
+  "description": "Module service generation rules",
+  "group": "module",
+  "docsSource": "apps/angelo/page/akanjs/(docs)/conventions/module/service.tsx",
+  "codegenPriority": 2,
+  "deprecated": false,
+  "scans": [
+    {
+      "type": "docs",
+      "description": "Current docs source for Model Service",
+      "path": "apps/angelo/page/akanjs/(docs)/conventions/module/service.tsx"
+    },
+    {
+      "type": "example",
+      "description": "Existing Akan implementation examples",
+      "path": "{apps,libs}/*/lib/**/*.ts",
+      "sample": 4
+    }
+  ],
+  "update": {
+    "filePath": "./modelService.instruction.md",
+    "contents": [
+      "purpose",
+      "file ownership",
+      "current API patterns",
+      "codegen rules",
+      "validation checklist"
+    ],
+    "rules": [
+      "Use current Akan APIs only",
+      "Keep output parseable for codegen",
+      "Include ownership boundaries and review checklist"
+    ]
+  },
+  "page": "apps/angelo/page/akanjs/(docs)/conventions/module/service.tsx"
+}

package/guidelines/modelService/modelService.instruction.md

@@ -0,0 +1,28 @@
+# model.service.ts Guideline
+
+## Purpose
+Generate server-side business workflows. A service decides which documents to load, how document methods compose, which other services are needed, and when to save results.
+
+## Ownership
+- A database service extends the current `serve(db.model, ({ use, service }) => ({ ... }))` pattern used in nearby modules.
+- Use generated document helpers for CRUD, list, query, count, insight, search, and load operations.
+- Use injected services for cross-domain work instead of importing and constructing service classes manually.
+- Use injected utilities or options for external APIs, configuration, queues, and infrastructure dependencies.
+
+## Current Akan Patterns
+- Put multi-step business workflows in service, not signal or UI.
+- Load documents through generated helpers, call document instance methods, then save once when practical.
+- Throw clear domain errors when invariants fail.
+- Return typed constants or documents that signal and store can serialize safely.
+
+## Codegen Rules
+- Do not keep persistent mutable state on the service instance.
+- Do not duplicate query definitions that belong in document filters.
+- Do not expose service methods directly to pages; expose them through signal endpoints or slices.
+- Do not hide authorization decisions here when they belong in signal guards, but service may still enforce domain invariants.
+
+## Review Checklist
+- The instruction points to current docs pages, not removed docs routes.
+- Generated examples use current Akan builder APIs and scanner-friendly filenames.
+- The output contract tells the model which file paths to return.
+- The guide avoids broad framework essays when a concrete file rule is better.

package/guidelines/modelSignal/modelSignal.generate.json

@@ -0,0 +1,37 @@
+{
+  "title": "Model Signal",
+  "description": "Module signal generation rules",
+  "group": "module",
+  "docsSource": "apps/angelo/page/akanjs/(docs)/conventions/module/signal.tsx",
+  "codegenPriority": 2,
+  "deprecated": false,
+  "scans": [
+    {
+      "type": "docs",
+      "description": "Current docs source for Model Signal",
+      "path": "apps/angelo/page/akanjs/(docs)/conventions/module/signal.tsx"
+    },
+    {
+      "type": "example",
+      "description": "Existing Akan implementation examples",
+      "path": "{apps,libs}/*/lib/**/*.ts",
+      "sample": 4
+    }
+  ],
+  "update": {
+    "filePath": "./modelSignal.instruction.md",
+    "contents": [
+      "purpose",
+      "file ownership",
+      "current API patterns",
+      "codegen rules",
+      "validation checklist"
+    ],
+    "rules": [
+      "Use current Akan APIs only",
+      "Keep output parseable for codegen",
+      "Include ownership boundaries and review checklist"
+    ]
+  },
+  "page": "apps/angelo/page/akanjs/(docs)/conventions/module/signal.tsx"
+}

package/guidelines/modelSignal/modelSignal.instruction.md

@@ -0,0 +1,28 @@
+# model.signal.ts Guideline
+
+## Purpose
+Generate the page-callable API surface for a module. Signal classes expose internal tasks, list/detail slices, endpoints, realtime channels, and resolved field handlers.
+
+## Ownership
+- `Internal` is for scheduled, queued, or server-only behavior.
+- `Slice` is for page data loading: lists, insights, detail views, pagination, filters, and guards.
+- `Endpoint` is for user actions such as create, update, submit, approve, archive, sync, or upload.
+- The exported signal registry class ties internal, endpoint, and slice classes to the model constant.
+
+## Current Akan Patterns
+- Use guards at root/get/cru/action boundaries so generated fetch clients inherit correct access rules.
+- Slices should call service methods and return model constants, light models, insights, or serializable DTOs.
+- Endpoints should call service workflows and return the updated model or action result.
+- Name slices and endpoints after user-visible behavior, not transport details.
+
+## Codegen Rules
+- Do not place business workflows in signal when service can own them.
+- Do not expose internal-only operations as public endpoints.
+- Do not bypass generated fetch/store conventions with ad hoc network calls.
+- Keep argument names stable because dictionary, docs, and generated clients depend on them.
+
+## Review Checklist
+- The instruction points to current docs pages, not removed docs routes.
+- Generated examples use current Akan builder APIs and scanner-friendly filenames.
+- The output contract tells the model which file paths to return.
+- The guide avoids broad framework essays when a concrete file rule is better.

package/guidelines/modelStore/modelStore.generate.json

@@ -0,0 +1,37 @@
+{
+  "title": "Model Store",
+  "description": "Module store generation rules",
+  "group": "module",
+  "docsSource": "apps/angelo/page/akanjs/(docs)/conventions/module/store.tsx",
+  "codegenPriority": 2,
+  "deprecated": false,
+  "scans": [
+    {
+      "type": "docs",
+      "description": "Current docs source for Model Store",
+      "path": "apps/angelo/page/akanjs/(docs)/conventions/module/store.tsx"
+    },
+    {
+      "type": "example",
+      "description": "Existing Akan implementation examples",
+      "path": "{apps,libs}/*/lib/**/*.ts",
+      "sample": 4
+    }
+  ],
+  "update": {
+    "filePath": "./modelStore.instruction.md",
+    "contents": [
+      "purpose",
+      "file ownership",
+      "current API patterns",
+      "codegen rules",
+      "validation checklist"
+    ],
+    "rules": [
+      "Use current Akan APIs only",
+      "Keep output parseable for codegen",
+      "Include ownership boundaries and review checklist"
+    ]
+  },
+  "page": "apps/angelo/page/akanjs/(docs)/conventions/module/store.tsx"
+}

package/guidelines/modelStore/modelStore.instruction.md

@@ -0,0 +1,28 @@
+# model.store.ts Guideline
+
+## Purpose
+Generate client state coordination for a module. Store connects generated fetch calls to form state, list state, detail state, toast messages, and UI-facing actions.
+
+## Ownership
+- Create the store with the current `stateOf(fetch.model, customState)` pattern used by nearby modules.
+- Use generated `st.use.*` selectors in UI and generated `st.do.*` actions for state changes.
+- Keep temporary UI state, selected IDs, query args, and form state in store when shared across components.
+- Call generated fetch endpoints from store actions rather than directly inside presentation components.
+
+## Current Akan Patterns
+- Use store actions for submit, refresh, pagination, filter changes, dialog-confirmed actions, and optimistic UI updates.
+- Use generated field setters for Template form inputs where available.
+- Keep server invariants in service; store should coordinate user interaction and client state.
+- Use user-facing messages consistently with dictionary terms.
+
+## Codegen Rules
+- Do not duplicate server data shape as independent client interfaces.
+- Do not store derived values that can be computed cheaply from existing state.
+- Do not perform persistence logic in React components when a store action can own it.
+- Do not call private or internal signal operations from UI state.
+
+## Review Checklist
+- The instruction points to current docs pages, not removed docs routes.
+- Generated examples use current Akan builder APIs and scanner-friendly filenames.
+- The output contract tells the model which file paths to return.
+- The guide avoids broad framework essays when a concrete file rule is better.

package/guidelines/modelTemplate/modelTemplate.generate.json

@@ -0,0 +1,37 @@
+{
+  "title": "Model Template",
+  "description": "Module form UI generation rules",
+  "group": "module",
+  "docsSource": "apps/angelo/page/akanjs/(docs)/conventions/module/template.tsx",
+  "codegenPriority": 3,
+  "deprecated": false,
+  "scans": [
+    {
+      "type": "docs",
+      "description": "Current docs source for Model Template",
+      "path": "apps/angelo/page/akanjs/(docs)/conventions/module/template.tsx"
+    },
+    {
+      "type": "example",
+      "description": "Existing Akan implementation examples",
+      "path": "{apps,libs}/*/lib/**/*.ts",
+      "sample": 4
+    }
+  ],
+  "update": {
+    "filePath": "./modelTemplate.instruction.md",
+    "contents": [
+      "purpose",
+      "file ownership",
+      "current API patterns",
+      "codegen rules",
+      "validation checklist"
+    ],
+    "rules": [
+      "Use current Akan APIs only",
+      "Keep output parseable for codegen",
+      "Include ownership boundaries and review checklist"
+    ]
+  },
+  "page": "apps/angelo/page/akanjs/(docs)/conventions/module/template.tsx"
+}

package/guidelines/modelTemplate/modelTemplate.instruction.md

@@ -0,0 +1,25 @@
+# Model.Template.tsx Guideline
+
+## Purpose
+Generate form and interaction fragments bound to store form state and generated setters.
+
+## Ownership
+- Template owns create/edit form pieces and reusable input groups.
+- It may use store hooks and generated setters when it is a client component.
+- It should not own persistence workflow decisions.
+
+## Current Akan Patterns
+- Use dictionary-backed labels and descriptions.
+- Use generated form state and setter actions.
+- Split repeated scalar editors into scalar Template files when reusable.
+
+## Codegen Rules
+- Do not call service or signal directly from inputs.
+- Do not duplicate validation that belongs in constants or service invariants.
+- Do not build page layout here when Zone should compose it.
+
+## Review Checklist
+- The instruction points to current docs pages, not removed docs routes.
+- Generated examples use current Akan builder APIs and scanner-friendly filenames.
+- The output contract tells the model which file paths to return.
+- The guide avoids broad framework essays when a concrete file rule is better.

package/guidelines/modelUnit/modelUnit.generate.json

@@ -0,0 +1,37 @@
+{
+  "title": "Model Unit",
+  "description": "Module compact display UI rules",
+  "group": "module",
+  "docsSource": "apps/angelo/page/akanjs/(docs)/conventions/module/unit.tsx",
+  "codegenPriority": 3,
+  "deprecated": false,
+  "scans": [
+    {
+      "type": "docs",
+      "description": "Current docs source for Model Unit",
+      "path": "apps/angelo/page/akanjs/(docs)/conventions/module/unit.tsx"
+    },
+    {
+      "type": "example",
+      "description": "Existing Akan implementation examples",
+      "path": "{apps,libs}/*/lib/**/*.ts",
+      "sample": 4
+    }
+  ],
+  "update": {
+    "filePath": "./modelUnit.instruction.md",
+    "contents": [
+      "purpose",
+      "file ownership",
+      "current API patterns",
+      "codegen rules",
+      "validation checklist"
+    ],
+    "rules": [
+      "Use current Akan APIs only",
+      "Keep output parseable for codegen",
+      "Include ownership boundaries and review checklist"
+    ]
+  },
+  "page": "apps/angelo/page/akanjs/(docs)/conventions/module/unit.tsx"
+}

package/guidelines/modelUnit/modelUnit.instruction.md

@@ -0,0 +1,25 @@
+# Model.Unit.tsx Guideline
+
+## Purpose
+Generate compact reusable light-model displays such as cards, rows, avatars, badges, and summaries.
+
+## Ownership
+- Unit owns repeated display of light model data.
+- It may accept navigation props or small display options.
+- It should stay reusable across list and relation contexts.
+
+## Current Akan Patterns
+- Use LightModel fields only unless a full model prop is explicitly passed.
+- Prefer small named components over one large card with every variant.
+- Use Link when navigation is part of the unit.
+
+## Codegen Rules
+- Do not fetch data or mutate state in Unit.
+- Do not assume full-model fields are available on light models.
+- Do not hide action workflows in list display.
+
+## Review Checklist
+- The instruction points to current docs pages, not removed docs routes.
+- Generated examples use current Akan builder APIs and scanner-friendly filenames.
+- The output contract tells the model which file paths to return.
+- The guide avoids broad framework essays when a concrete file rule is better.

package/guidelines/modelUtil/modelUtil.generate.json

@@ -0,0 +1,37 @@
+{
+  "title": "Model Util",
+  "description": "Module utility UI rules",
+  "group": "module",
+  "docsSource": "apps/angelo/page/akanjs/(docs)/conventions/module/util.tsx",
+  "codegenPriority": 3,
+  "deprecated": false,
+  "scans": [
+    {
+      "type": "docs",
+      "description": "Current docs source for Model Util",
+      "path": "apps/angelo/page/akanjs/(docs)/conventions/module/util.tsx"
+    },
+    {
+      "type": "example",
+      "description": "Existing Akan implementation examples",
+      "path": "{apps,libs}/*/lib/**/*.ts",
+      "sample": 4
+    }
+  ],
+  "update": {
+    "filePath": "./modelUtil.instruction.md",
+    "contents": [
+      "purpose",
+      "file ownership",
+      "current API patterns",
+      "codegen rules",
+      "validation checklist"
+    ],
+    "rules": [
+      "Use current Akan APIs only",
+      "Keep output parseable for codegen",
+      "Include ownership boundaries and review checklist"
+    ]
+  },
+  "page": "apps/angelo/page/akanjs/(docs)/conventions/module/util.tsx"
+}

package/guidelines/modelUtil/modelUtil.instruction.md

@@ -0,0 +1,25 @@
+# Model.Util.tsx Guideline
+
+## Purpose
+Generate small model-specific client controls such as action buttons, toolbars, dialogs, query panels, and navigation helpers.
+
+## Ownership
+- Util owns interactive helpers that are too small to be a Zone.
+- It may call store actions and open dialogs.
+- It should stay model-specific and composable.
+
+## Current Akan Patterns
+- Use dictionary text for confirmations and action labels.
+- Keep destructive actions explicit and confirmable.
+- Prefer store actions over inline fetch calls.
+
+## Codegen Rules
+- Do not put large page layout in Util.
+- Do not duplicate Template form code.
+- Do not bypass guards or server-side invariants.
+
+## Review Checklist
+- The instruction points to current docs pages, not removed docs routes.
+- Generated examples use current Akan builder APIs and scanner-friendly filenames.
+- The output contract tells the model which file paths to return.
+- The guide avoids broad framework essays when a concrete file rule is better.

package/guidelines/modelView/modelView.generate.json

@@ -0,0 +1,37 @@
+{
+  "title": "Model View",
+  "description": "Module full detail UI rules",
+  "group": "module",
+  "docsSource": "apps/angelo/page/akanjs/(docs)/conventions/module/view.tsx",
+  "codegenPriority": 3,
+  "deprecated": false,
+  "scans": [
+    {
+      "type": "docs",
+      "description": "Current docs source for Model View",
+      "path": "apps/angelo/page/akanjs/(docs)/conventions/module/view.tsx"
+    },
+    {
+      "type": "example",
+      "description": "Existing Akan implementation examples",
+      "path": "{apps,libs}/*/lib/**/*.ts",
+      "sample": 4
+    }
+  ],
+  "update": {
+    "filePath": "./modelView.instruction.md",
+    "contents": [
+      "purpose",
+      "file ownership",
+      "current API patterns",
+      "codegen rules",
+      "validation checklist"
+    ],
+    "rules": [
+      "Use current Akan APIs only",
+      "Keep output parseable for codegen",
+      "Include ownership boundaries and review checklist"
+    ]
+  },
+  "page": "apps/angelo/page/akanjs/(docs)/conventions/module/view.tsx"
+}

package/guidelines/modelView/modelView.instruction.md

@@ -0,0 +1,25 @@
+# Model.View.tsx Guideline
+
+## Purpose
+Generate full-model detail displays for detail pages, view modals, and sections needing complete model data.
+
+## Ownership
+- View owns presentation of one full model.
+- It can compose Unit displays for related light models.
+- It should show data clearly without owning page-level state.
+
+## Current Akan Patterns
+- Use full model props and render important fields, relations, and resolved values.
+- Use dictionary terms for field labels where possible.
+- Keep display variants named by layout or purpose.
+
+## Codegen Rules
+- Do not perform click workflows here; wrap with Util or Zone when interaction is needed.
+- Do not fetch data inside View.
+- Do not omit core model fields when the view claims to be general.
+
+## Review Checklist
+- The instruction points to current docs pages, not removed docs routes.
+- Generated examples use current Akan builder APIs and scanner-friendly filenames.
+- The output contract tells the model which file paths to return.
+- The guide avoids broad framework essays when a concrete file rule is better.

package/guidelines/modelZone/modelZone.generate.json

@@ -0,0 +1,37 @@
+{
+  "title": "Model Zone",
+  "description": "Module page section UI rules",
+  "group": "module",
+  "docsSource": "apps/angelo/page/akanjs/(docs)/conventions/module/zone.tsx",
+  "codegenPriority": 3,
+  "deprecated": false,
+  "scans": [
+    {
+      "type": "docs",
+      "description": "Current docs source for Model Zone",
+      "path": "apps/angelo/page/akanjs/(docs)/conventions/module/zone.tsx"
+    },
+    {
+      "type": "example",
+      "description": "Existing Akan implementation examples",
+      "path": "{apps,libs}/*/lib/**/*.ts",
+      "sample": 4
+    }
+  ],
+  "update": {
+    "filePath": "./modelZone.instruction.md",
+    "contents": [
+      "purpose",
+      "file ownership",
+      "current API patterns",
+      "codegen rules",
+      "validation checklist"
+    ],
+    "rules": [
+      "Use current Akan APIs only",
+      "Keep output parseable for codegen",
+      "Include ownership boundaries and review checklist"
+    ]
+  },
+  "page": "apps/angelo/page/akanjs/(docs)/conventions/module/zone.tsx"
+}

package/guidelines/modelZone/modelZone.instruction.md

@@ -0,0 +1,25 @@
+# Model.Zone.tsx Guideline
+
+## Purpose
+Generate page sections that compose loaders, lists, views, templates, utilities, and section-level UI state.
+
+## Ownership
+- Zone owns page-level composition around one model.
+- It coordinates Load wrappers, Unit/View display, Util controls, and section layout.
+- It may hold local UI state that is only meaningful for the section.
+
+## Current Akan Patterns
+- Use store selectors and actions to connect data to the section.
+- Split display into Unit/View and controls into Util before Zone grows too large.
+- Name zones after page sections or user tasks.
+
+## Codegen Rules
+- Do not put low-level input groups here when Template owns them.
+- Do not duplicate Unit or View display code.
+- Do not implement service workflow logic in Zone.
+
+## Review Checklist
+- The instruction points to current docs pages, not removed docs routes.
+- Generated examples use current Akan builder APIs and scanner-friendly filenames.
+- The output contract tells the model which file paths to return.
+- The guide avoids broad framework essays when a concrete file rule is better.

package/guidelines/moduleCodegen/moduleCodegen.generate.json

@@ -0,0 +1,37 @@
+{
+  "title": "Module Codegen",
+  "description": "AI module generation orchestration",
+  "group": "module",
+  "docsSource": "apps/angelo/page/akanjs/(docs)/conventions/module/overview.tsx",
+  "codegenPriority": 1,
+  "deprecated": false,
+  "scans": [
+    {
+      "type": "docs",
+      "description": "Current docs source for Module Codegen",
+      "path": "apps/angelo/page/akanjs/(docs)/conventions/module/overview.tsx"
+    },
+    {
+      "type": "example",
+      "description": "Existing Akan implementation examples",
+      "path": "{apps,libs}/*/lib/**/*.ts",
+      "sample": 4
+    }
+  ],
+  "update": {
+    "filePath": "./moduleCodegen.instruction.md",
+    "contents": [
+      "purpose",
+      "file ownership",
+      "current API patterns",
+      "codegen rules",
+      "validation checklist"
+    ],
+    "rules": [
+      "Use current Akan APIs only",
+      "Keep output parseable for codegen",
+      "Include ownership boundaries and review checklist"
+    ]
+  },
+  "page": "apps/angelo/page/akanjs/(docs)/conventions/module/overview.tsx"
+}

package/guidelines/moduleCodegen/moduleCodegen.instruction.md

@@ -0,0 +1,28 @@
+# Module Codegen Orchestration Guideline
+
+## Purpose
+Use this to orchestrate AI-assisted module creation. The model should emit small, parseable file blocks and preserve Akan ownership boundaries.
+
+## Ownership
+- Input description explains the business object, lifecycle, actions, queries, UI needs, and relations.
+- The first output pass should prioritize data shape and persistence over decorative UI.
+- Each returned code block must start with `// File: <relative path>` so `AiSession.writeTypescripts()` can parse it.
+- Generated files must target `lib/<model>/...` or `lib/__scalar/<scalar>/...` only unless explicitly requested.
+
+## Current Akan Patterns
+- Phase 1: generate or update `model.constant.ts`, `model.dictionary.ts`, and `model.document.ts`.
+- Phase 2: generate service, signal, and store only when there are business workflows or page-callable actions.
+- Phase 3: generate UI files only after store/signal data flow is known.
+- Use docs-backed examples from the current app and connected libs before inventing patterns.
+
+## Codegen Rules
+- Return only file blocks for writes, plus no prose in codegen responses unless explicitly requested.
+- Prefer conservative defaults: one useful query, one insight only if analytics are requested, and minimal UI variants.
+- Avoid broad abstractions; create helper functions only when they remove clear duplication inside the target module.
+- When unsure whether a value should be scalar or module, choose scalar for embedded value objects and module for independent lifecycle or permissions.
+
+## Review Checklist
+- The instruction points to current docs pages, not removed docs routes.
+- Generated examples use current Akan builder APIs and scanner-friendly filenames.
+- The output contract tells the model which file paths to return.
+- The guide avoids broad framework essays when a concrete file rule is better.

package/guidelines/moduleOverview/moduleOverview.generate.json

@@ -0,0 +1,37 @@
+{
+  "title": "Module Overview",
+  "description": "Module file roles and growth order",
+  "group": "core",
+  "docsSource": "apps/angelo/page/akanjs/(docs)/conventions/module/overview.tsx",
+  "codegenPriority": 1,
+  "deprecated": false,
+  "scans": [
+    {
+      "type": "docs",
+      "description": "Current docs source for Module Overview",
+      "path": "apps/angelo/page/akanjs/(docs)/conventions/module/overview.tsx"
+    },
+    {
+      "type": "example",
+      "description": "Existing Akan implementation examples",
+      "path": "{apps,libs}/*/lib/**/*.ts",
+      "sample": 4
+    }
+  ],
+  "update": {
+    "filePath": "./moduleOverview.instruction.md",
+    "contents": [
+      "purpose",
+      "file ownership",
+      "current API patterns",
+      "codegen rules",
+      "validation checklist"
+    ],
+    "rules": [
+      "Use current Akan APIs only",
+      "Keep output parseable for codegen",
+      "Include ownership boundaries and review checklist"
+    ]
+  },
+  "page": "apps/angelo/page/akanjs/(docs)/conventions/module/overview.tsx"
+}