@hamak/smart-data-dico 1.18.0 → 1.18.1

package/backend/dist/server.mjs

@@ -82888,6 +82888,22 @@ var init_dist6 = __esm({
   }
 });
 
+// backend/src/services/ai/authoringRules.ts
+var AUTHORING_RULES;
+var init_authoringRules = __esm({
+  "backend/src/services/ai/authoringRules.ts"() {
+    "use strict";
+    AUTHORING_RULES = `AUTHORING RULES \u2014 Smart Data Dictionary file format. Follow exactly when creating or changing model elements (prefer the dedicated tools; these rules govern what a valid result looks like):
+
+- UUIDs: every entity, attribute (including nested properties/items), relationship, rule, and case has a real UUID (v1\u2013v5). Never hand-type hex \u2014 the tools generate them. Identifiers are unique across the WHOLE package, not per file: a duplicate entity name, or a duplicate rule/case/relationship UUID anywhere in the package, is a hard load error.
+- References are UUID-based, never name-based, so renames don't break links. Every reference (relationship ends, rule targets, action/state-machine ownerRef) must resolve within the package.
+- Keep the three governance concepts SEPARATE \u2014 never collapse them: Validation (attribute.validation \u2014 pattern, maxLength, enumValues, minimum\u2026) vs Constraint (entity.constraints[] \u2014 unique, check, foreignKey, index; DB-enforced) vs Rule (a first-class business invariant across fields/lifecycle). type: enum \u2192 allowed values live in validation.enumValues, not a separate field.
+- Conceptual vs physical stay distinct: author logical names (PascalCase entities, camelCase attributes, logical/derived types); physical.* holds table/column names and dbTypes. Never write SQL/DDL with conceptual names.
+- Reserved metadata keys you may set on an element: system.hidden ("true" hides it from lists/diagrams/exports; "false" pins it visible over any rule) and system.style (a defined Element Style name \u2192 styles it in diagrams). Prefer the hide / element-style tools over writing these metadata keys directly.
+- Project config in dico.config.json carries: types[] (reusable derived attribute types), hideRules[] (glob/regex that bulk-hide reverse-engineering waste), and elementStyles[] + styleRules[] (named diagram styles bound to roles). Manage these with the dedicated tools (createDerivedType, defineElementStyle, addStyleRule) rather than editing config blindly.`;
+  }
+});
+
 // backend/src/utils/appDir.ts
 import fs from "fs";
 import path8 from "path";
@@ -116532,6 +116548,9 @@ function sqlSettingsInstruction(cfg) {
 function buildSystemPrompt(pageContext, conversationSystemPrompt, mode = "designer", modelOutline, sqlInstruction) {
   const base = typeof conversationSystemPrompt === "string" && conversationSystemPrompt.trim().length > 0 ? conversationSystemPrompt.trim().slice(0, 8e3) : SYSTEM_PROMPT;
   let out = base + getModeSystemSuffix(mode);
+  if (mode === "designer") out += `
+
+${AUTHORING_RULES}`;
   if (typeof sqlInstruction === "string" && sqlInstruction.trim().length > 0) {
     out += `
 
@@ -116883,6 +116902,7 @@ var init_aiController = __esm({
     init_logger();
     init_config();
     init_agentToolRegistry();
+    init_authoringRules();
     init_appDir();
     init_conversationService();
     init_promptService();

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@hamak/smart-data-dico",
-  "version": "1.18.0",
+  "version": "1.18.1",
   "description": "Collaborative data dictionary management system — model, document, and govern your data landscape",
   "type": "module",
   "bin": {