@akanjs/cli 1.0.20 → 2.1.0-rc.1

package/guidelines/componentRule/componentRule.generate.json

@@ -0,0 +1,37 @@
+{
+  "title": "Component Rule",
+  "description": "Shared component implementation rules",
+  "group": "core",
+  "docsSource": "apps/angelo/page/akanjs/(docs)/references/ui/overview.tsx",
+  "codegenPriority": 3,
+  "deprecated": false,
+  "scans": [
+    {
+      "type": "docs",
+      "description": "Current docs source for Component Rule",
+      "path": "apps/angelo/page/akanjs/(docs)/references/ui/overview.tsx"
+    },
+    {
+      "type": "example",
+      "description": "Existing Akan implementation examples",
+      "path": "{apps,libs}/*/lib/**/*.ts",
+      "sample": 4
+    }
+  ],
+  "update": {
+    "filePath": "./componentRule.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)/references/ui/overview.tsx"
+}

package/guidelines/componentRule/componentRule.instruction.md

@@ -0,0 +1,28 @@
+# Akan Component Rule Guideline
+
+## Purpose
+Use this for shared UI rules across module, scalar, app UI, and docs components.
+
+## Ownership
+- Accept `className?: string` for reusable components and forward it through `clsx`.
+- Use semantic HTML and accessible labels for interactive elements.
+- Use `akanjs/ui` and project UI libraries before adding new primitives.
+- Keep presentation components small; move page composition to Zone and actions to Util or store.
+
+## Current Akan Patterns
+- Unit renders compact repeated display, View renders full detail display, Template renders form fragments, Util renders small controls, Zone composes page sections.
+- Server components should stay display-only unless the file convention says otherwise.
+- Client components can use store hooks and event handlers where interaction is required.
+- Use generated model types from app client or module constants; do not invent duplicate UI-only model shapes.
+
+## Codegen Rules
+- Do not put business workflow decisions in render code.
+- Do not use undocumented UI components or props.
+- Do not use hardcoded colors when DaisyUI semantic classes work.
+- Do not create broad component abstractions before repeated patterns exist.
+
+## 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/cssRule/cssRule.generate.json

@@ -0,0 +1,37 @@
+{
+  "title": "CSS Rule",
+  "description": "Tailwind and DaisyUI styling rules",
+  "group": "core",
+  "docsSource": "apps/angelo/page/akanjs/(docs)/docs/arch/css.tsx",
+  "codegenPriority": 3,
+  "deprecated": false,
+  "scans": [
+    {
+      "type": "docs",
+      "description": "Current docs source for CSS Rule",
+      "path": "apps/angelo/page/akanjs/(docs)/docs/arch/css.tsx"
+    },
+    {
+      "type": "example",
+      "description": "Existing Akan implementation examples",
+      "path": "{apps,libs}/*/lib/**/*.ts",
+      "sample": 4
+    }
+  ],
+  "update": {
+    "filePath": "./cssRule.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)/docs/arch/css.tsx"
+}

package/guidelines/cssRule/cssRule.instruction.md

@@ -0,0 +1,28 @@
+# CSS Rule Guideline
+
+## Purpose
+Use TailwindCSS and DaisyUI in a theme-safe, composable way for Akan UI and docs pages.
+
+## Ownership
+- Use Tailwind utility classes for layout, spacing, typography, and responsive behavior.
+- Use DaisyUI semantic tokens such as base, primary, secondary, accent, info, success, warning, and error.
+- Use `clsx` from `akanjs/client` for conditional class composition.
+- Forward `className` at the end of composed class strings to allow callers to extend styles.
+
+## Current Akan Patterns
+- Prefer mobile-first responsive classes.
+- Use card, btn, input, badge, alert, divider, tabs, modal, and other documented DaisyUI classes when they match the design.
+- Use consistent density and spacing within one component family.
+- Keep custom CSS files rare and scoped to cases utilities cannot express cleanly.
+
+## Codegen Rules
+- Do not hardcode hex colors or one-off brand colors unless the existing file already defines that design system.
+- Do not use important flags to fight component composition.
+- Do not hide focus states on interactive elements.
+- Do not add global CSS for one component-specific layout.
+
+## 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/docPageRule/docPageRule.generate.json

@@ -0,0 +1,37 @@
+{
+  "title": "Docs Page Rule",
+  "description": "Docs page writing rules",
+  "group": "core",
+  "docsSource": "apps/angelo/page/akanjs/(docs)/cheatsheet/dev/docs.tsx",
+  "codegenPriority": 3,
+  "deprecated": false,
+  "scans": [
+    {
+      "type": "docs",
+      "description": "Current docs source for Docs Page Rule",
+      "path": "apps/angelo/page/akanjs/(docs)/cheatsheet/dev/docs.tsx"
+    },
+    {
+      "type": "example",
+      "description": "Existing Akan implementation examples",
+      "path": "{apps,libs}/*/lib/**/*.ts",
+      "sample": 4
+    }
+  ],
+  "update": {
+    "filePath": "./docPageRule.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)/cheatsheet/dev/docs.tsx"
+}

package/guidelines/docPageRule/docPageRule.instruction.md

@@ -0,0 +1,25 @@
+# Docs Page Rule Guideline
+
+## Purpose
+Use this when generating or updating Akan docs pages under the current docs route tree.
+
+## Ownership
+- Docs pages live under `apps/angelo/page/akanjs/(docs)`.
+- Pages use `Docs`, `Code`, `Scroll`, and app localization helpers used by nearby pages.
+- A docs page should teach one concept with examples, alerts, and navigation anchors.
+
+## Current Akan Patterns
+- Use current route groups: docs, conventions, references, cheatsheet, and plugins.
+- Prefer concise sections with code snippets and practical rules.
+- Use Mermaid only when it clarifies architecture or flow.
+
+## Codegen Rules
+- Do not write docs for removed route paths.
+- Do not generate placeholder pages when source docs already exist.
+- Do not include implementation claims that are not backed by code or nearby docs.
+
+## 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/docSyncRule/docSyncRule.generate.json

@@ -0,0 +1,37 @@
+{
+  "title": "Docs Sync Rule",
+  "description": "Docs to guideline sync rules",
+  "group": "core",
+  "docsSource": "apps/angelo/page/akanjs/(docs)/docs/_index.tsx",
+  "codegenPriority": 3,
+  "deprecated": false,
+  "scans": [
+    {
+      "type": "docs",
+      "description": "Current docs source for Docs Sync Rule",
+      "path": "apps/angelo/page/akanjs/(docs)/docs/_index.tsx"
+    },
+    {
+      "type": "example",
+      "description": "Existing Akan implementation examples",
+      "path": "{apps,libs}/*/lib/**/*.ts",
+      "sample": 4
+    }
+  ],
+  "update": {
+    "filePath": "./docSyncRule.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)/docs/_index.tsx"
+}

package/guidelines/docSyncRule/docSyncRule.instruction.md

@@ -0,0 +1,25 @@
+# Docs To Guideline Sync Rule
+
+## Purpose
+Use this when applying current docs page information back into guideline instruction files.
+
+## Ownership
+- Docs pages are the source of truth for product-facing explanations.
+- Guideline instructions are compressed operational rules for AI codegen.
+- Sync should preserve codegen-specific output contracts and validation rules that docs pages may not mention.
+
+## Current Akan Patterns
+- Extract ownership boundaries, API names, file paths, examples, and warnings from docs pages.
+- Convert long explanatory sections into prompt-friendly bullet rules.
+- Keep docs links or source paths in `generate.json` metadata.
+
+## Codegen Rules
+- Do not copy large TSX page content directly into markdown instructions.
+- Do not remove codegen output format requirements during sync.
+- Do not let stale instruction examples override newer docs examples.
+
+## 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/enumConstant/enumConstant.generate.json

@@ -0,0 +1,37 @@
+{
+  "title": "Enum Constant",
+  "description": "enumOf category value rules",
+  "group": "core",
+  "docsSource": "apps/angelo/page/akanjs/(docs)/conventions/module/constant.tsx",
+  "codegenPriority": 2,
+  "deprecated": false,
+  "scans": [
+    {
+      "type": "docs",
+      "description": "Current docs source for Enum Constant",
+      "path": "apps/angelo/page/akanjs/(docs)/conventions/module/constant.tsx"
+    },
+    {
+      "type": "example",
+      "description": "Existing Akan implementation examples",
+      "path": "{apps,libs}/*/lib/**/*.ts",
+      "sample": 4
+    }
+  ],
+  "update": {
+    "filePath": "./enumConstant.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/constant.tsx"
+}

package/guidelines/enumConstant/enumConstant.instruction.md

@@ -0,0 +1,28 @@
+# enumOf Guideline
+
+## Purpose
+Use enum classes for categorical values that need type safety, defaults, dictionary entries, and stable API values.
+
+## Ownership
+- Define enum classes near the constant or scalar that owns the category.
+- Use camelCase values that are stable API/storage values.
+- Export the enum class so constants, dictionaries, UI, service, and signal can share it.
+- Provide dictionary entries for each public enum value and description.
+
+## Current Akan Patterns
+- Use enums for status, role, type, mode, channel, lifecycle, and similar finite sets.
+- Use boolean fields only when there are exactly two stable states and labels are obvious.
+- Use string fields only when the value is open-ended or user-defined.
+- Keep enum names domain-specific enough to avoid collisions.
+
+## Codegen Rules
+- Do not generate plain string unions when enum dictionary coverage is needed.
+- Do not rename stored enum values casually; persisted data may depend on them.
+- Do not add unused enum values just for hypothetical future UI.
+- Do not mix display labels into stored enum values.
+
+## 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/fieldRule/fieldRule.generate.json

@@ -0,0 +1,37 @@
+{
+  "title": "Field Rule",
+  "description": "Current via field helper rules",
+  "group": "core",
+  "docsSource": "apps/angelo/page/akanjs/(docs)/conventions/module/constant.tsx",
+  "codegenPriority": 1,
+  "deprecated": false,
+  "scans": [
+    {
+      "type": "docs",
+      "description": "Current docs source for Field Rule",
+      "path": "apps/angelo/page/akanjs/(docs)/conventions/module/constant.tsx"
+    },
+    {
+      "type": "example",
+      "description": "Existing Akan implementation examples",
+      "path": "{apps,libs}/*/lib/**/*.ts",
+      "sample": 4
+    }
+  ],
+  "update": {
+    "filePath": "./fieldRule.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/constant.tsx"
+}

package/guidelines/fieldRule/fieldRule.instruction.md

@@ -0,0 +1,31 @@
+# Akan Field Rule Guideline
+
+## Purpose
+Use this whenever generating constants or scalar constants. It defines the current `via()` field helper style and field option rules.
+
+## Ownership
+- `field(Type)` defines a required public field.
+- `field(Type, options)` defines a field with defaults, examples, validation, aggregation, or relation metadata.
+- `field(Type).optional()` marks a nullable or optional business value when absence is valid.
+- `field.hidden(Type).optional()` is for internal state that should not be treated as a normal public field.
+- `field.secret(Type).optional()` is for sensitive values that should not be selected by default.
+- `field([Type])` defines arrays; provide empty array defaults when the app expects list operations.
+
+## Current Akan Patterns
+- Use `String`, `Boolean`, `Date`, `Int`, `Float`, `ID`, scalar classes, model light classes, or enum classes as field types.
+- Use `enumOf()` classes for categorical values that need type-safe values and dictionary entries.
+- Use scalar classes for embedded reusable value objects such as price, address, coordinate, or file metadata.
+- Use light model classes for embedded resolved references when the parent stores or exposes a compact related model.
+
+## Codegen Rules
+- Every generated field should have a clear business reason and a dictionary label/description unless it is hidden or secret.
+- Use `example` values when the field appears in APIs or docs.
+- Use `default` for stable empty states such as empty string, zero, false, empty list, or date factory.
+- Use validation options only for domain invariants, not UI-only preferences.
+- Do not create fields only because a UI might someday need 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/framework/framework.generate.json

@@ -0,0 +1,37 @@
+{
+  "title": "Akan.js Framework",
+  "description": "Compact global context for Akan AI codegen",
+  "group": "core",
+  "docsSource": "apps/angelo/page/akanjs/(docs)/docs/intro/fundamentals.tsx",
+  "codegenPriority": 1,
+  "deprecated": false,
+  "scans": [
+    {
+      "type": "docs",
+      "description": "Current docs source for Akan.js Framework",
+      "path": "apps/angelo/page/akanjs/(docs)/docs/intro/fundamentals.tsx"
+    },
+    {
+      "type": "example",
+      "description": "Existing Akan implementation examples",
+      "path": "{apps,libs}/*/lib/**/*.ts",
+      "sample": 4
+    }
+  ],
+  "update": {
+    "filePath": "./framework.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)/docs/intro/fundamentals.tsx"
+}

package/guidelines/framework/framework.instruction.md

@@ -0,0 +1,29 @@
+# Akan.js Framework Guide
+
+## Purpose
+Use this as the compact framework context for AI codegen. It should explain how Akan turns convention-based files into a full-stack app without teaching every API in one place.
+
+## Ownership
+- `apps/<app>` contains app code, pages, env files, module folders, UI, webkit, srvkit, and common utilities.
+- `libs/<lib>` contains reusable domain and utility libraries consumed by apps.
+- `pkgs/akanjs` contains framework facets such as base, constant, document, service, signal, store, client, ui, and CLI tooling.
+- Domain behavior lives near the model folder instead of being split by technical layer first.
+
+## Current Akan Patterns
+- Database module flow is `constant -> dictionary -> document -> service -> signal -> store -> UI`.
+- Scalars live under `lib/__scalar/<scalarName>` and represent embedded value objects.
+- Service modules live under `lib/_<serviceName>` when behavior is not centered on one stored model.
+- Generated registry files such as `cnst.ts`, `db.ts`, `dict.ts`, `sig.ts`, `srv.ts`, and `st.ts` are scanner outputs and should not be hand-authored.
+- Pages and components should consume generated client/server helpers rather than duplicating model shapes.
+
+## Codegen Rules
+- Prefer the most specific guideline for file syntax; use this guide only for global architecture context.
+- When generating a new feature, start with the smallest necessary layer set and add later layers only when required by behavior.
+- Keep business decisions in constant, document, or service; keep API exposure in signal; keep client coordination in store; keep rendering in UI files.
+- Use direct module imports where scanner rules expect them, and avoid inventing new top-level app folders.
+
+## 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/modelConstant/modelConstant.generate.json

@@ -0,0 +1,37 @@
+{
+  "title": "Model Constant",
+  "description": "Module constant generation rules",
+  "group": "module",
+  "docsSource": "apps/angelo/page/akanjs/(docs)/conventions/module/constant.tsx",
+  "codegenPriority": 1,
+  "deprecated": false,
+  "scans": [
+    {
+      "type": "docs",
+      "description": "Current docs source for Model Constant",
+      "path": "apps/angelo/page/akanjs/(docs)/conventions/module/constant.tsx"
+    },
+    {
+      "type": "example",
+      "description": "Existing Akan implementation examples",
+      "path": "{apps,libs}/*/lib/**/*.ts",
+      "sample": 4
+    }
+  ],
+  "update": {
+    "filePath": "./modelConstant.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/constant.tsx"
+}

package/guidelines/modelConstant/modelConstant.instruction.md

@@ -0,0 +1,30 @@
+# model.constant.ts Guideline
+
+## Purpose
+Generate the business data shape for a collection-backed Akan module. This file is the shared type source used by document, service, signal, store, and UI.
+
+## Ownership
+- Define enum classes first when the model has categorical states.
+- Define `ModelInput` for fields accepted from create or edit flows.
+- Define `ModelObject` by extending `via(ModelInput, (field) => ({ ... }))` for stored fields controlled by system or service behavior.
+- Define `LightModel` by selecting compact list/reference fields from the object layer.
+- Define full `Model` by combining object and light layers and adding only small static or type helpers when needed.
+- Define `ModelInsight` only when aggregation or dashboard values are useful.
+
+## Current Akan Patterns
+- Use `via()` and the `field` helper for all model layers.
+- Use `field.hidden()` and `field.secret()` for internal or sensitive values.
+- Use scalars from `../__scalar/<name>/<name>.constant` when a field group is reusable and embedded.
+- Use direct imports for related light models to avoid circular barrel imports.
+
+## Codegen Rules
+- Keep the light model small enough for lists, cards, and relation previews.
+- Do not put persistence queries, service workflows, fetch calls, or React UI in constant files.
+- Use stable defaults for arrays and frequently read values.
+- Add dictionary coverage for public fields, enums, insights, and query-facing names.
+
+## 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/modelDictionary/modelDictionary.generate.json

@@ -0,0 +1,37 @@
+{
+  "title": "Model Dictionary",
+  "description": "Module dictionary generation rules",
+  "group": "module",
+  "docsSource": "apps/angelo/page/akanjs/(docs)/conventions/module/dictionary.tsx",
+  "codegenPriority": 1,
+  "deprecated": false,
+  "scans": [
+    {
+      "type": "docs",
+      "description": "Current docs source for Model Dictionary",
+      "path": "apps/angelo/page/akanjs/(docs)/conventions/module/dictionary.tsx"
+    },
+    {
+      "type": "example",
+      "description": "Existing Akan implementation examples",
+      "path": "{apps,libs}/*/lib/**/*.ts",
+      "sample": 4
+    }
+  ],
+  "update": {
+    "filePath": "./modelDictionary.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/dictionary.tsx"
+}

package/guidelines/modelDictionary/modelDictionary.instruction.md

@@ -0,0 +1,30 @@
+# model.dictionary.ts Guideline
+
+## Purpose
+Generate user-facing language for a model. Dictionary entries should make fields, enum values, queries, slices, endpoints, errors, and UI phrases readable in every supported language.
+
+## Ownership
+- `modelName` and `modelDesc` describe the model itself.
+- Public model fields need `fieldName` and `desc-fieldName` entries.
+- Enum values need `enum-field-value` and `enumdesc-field-value` entries.
+- Document queries and sorts need query labels, descriptions, and argument descriptions when surfaced to UI or docs.
+- Signal slices and endpoints need API labels, API descriptions, argument labels, and argument descriptions.
+- Custom UI text should live near the model when it is model-specific.
+
+## Current Akan Patterns
+- Use `ModelDictionary`, `SignalDictionary`, base translations, and base signal translations where available in nearby examples.
+- Keep language order consistent with the app convention.
+- Prefer short labels and useful descriptions over repeating the field name.
+- Group entries by model, insight, query, endpoint, enum, error, and UI sections.
+
+## Codegen Rules
+- Dictionary keys must match generated field, enum, query, slice, endpoint, and argument names.
+- Do not add orphan translations that are not used by the model or UI.
+- Do not omit descriptions for public fields or externally visible arguments.
+- Preserve generated base translations instead of rewriting common keys.
+
+## 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/modelDocument/modelDocument.generate.json

@@ -0,0 +1,37 @@
+{
+  "title": "Model Document",
+  "description": "Module persistence generation rules",
+  "group": "module",
+  "docsSource": "apps/angelo/page/akanjs/(docs)/conventions/module/document.tsx",
+  "codegenPriority": 1,
+  "deprecated": false,
+  "scans": [
+    {
+      "type": "docs",
+      "description": "Current docs source for Model Document",
+      "path": "apps/angelo/page/akanjs/(docs)/conventions/module/document.tsx"
+    },
+    {
+      "type": "example",
+      "description": "Existing Akan implementation examples",
+      "path": "{apps,libs}/*/lib/**/*.ts",
+      "sample": 4
+    }
+  ],
+  "update": {
+    "filePath": "./modelDocument.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/document.tsx"
+}