@c4a/server-cli 0.4.15-alpha.5 → 0.4.15-alpha.6

package/index.js

@@ -222212,20 +222212,20 @@ class GleaningExtractor {
 // ../llm/src/prompts/docAtomAnnotation.ts
 init_src();
 var DOC_ATOM_DEFS = [
-  ["entities", "Named things: systems, services, modules, documents, APIs (NOT people/teams — use roles for those)", entityAtomSchema],
+  ["entities", "Named things with independent identity — something you can ask questions about ('What does X do?', 'Who owns X?'). Examples: systems, services, modules, APIs, products. If it is a value, address, path, or configuration detail, it is an attribute of an entity, not an entity itself. (NOT people/teams — use roles for those). kind: implementation=internal systems/services, external=third-party dependencies, concept=abstract/not-yet-implemented", entityAtomSchema],
   ["relations", "Connections between entities", relationAtomSchema],
   ["behaviors", "Actions/operations: functions, API calls, user actions, workflows", behaviorAtomSchema],
   ["attributes", "Properties of entities", attributeAtomSchema],
   ["states", "Possible states of entities", stateAtomSchema],
-  ["rules", "Business/domain rules: validations, constraints expressed as logic", ruleAtomSchema],
+  ["rules", "Conditional business/domain logic: IF condition THEN consequence (e.g., 'IF user not authenticated THEN reject request')", ruleAtomSchema],
   ["transitions", "State changes: from→to triggered by events or guards", transitionAtomSchema],
   ["events", "Occurrences that trigger behaviors", eventAtomSchema],
   ["decisions", "Architectural or business decisions", decisionAtomSchema],
   ["metrics", "Measurable targets: SLA, throughput, error_rate, with thresholds", metricAtomSchema],
-  ["roles", "Actors: human roles, teams, personas that perform behaviors", roleAtomSchema],
-  ["constraints", "Hard/soft requirements", constraintAtomSchema],
+  ["roles", "Actors: human roles, teams, personas that perform behaviors. kind: human=individual role, team=group/department, persona=user archetype. System-triggered actions use entity relations, NOT roles", roleAtomSchema],
+  ["constraints", "Declarative requirements: 'X must/should/must-not Y' (e.g., 'passwords must be >= 8 chars'). Unlike rules, constraints have no IF-THEN condition — they are unconditional mandates or restrictions", constraintAtomSchema],
   ["comparisons", "Side-by-side evaluations", comparisonAtomSchema],
-  ["boundaries", "System/domain boundaries: what is included vs excluded", boundaryAtomSchema]
+  ["boundaries", "Explicit scope declarations: what is included vs excluded. Only extract when the text explicitly declares scope (e.g., 'this product covers X but NOT Y'). Implicit containment (A runs inside B) is expressed via entity relations, not boundaries", boundaryAtomSchema]
 ];
 function buildAtomTypesBlock() {
   return DOC_ATOM_DEFS.map(([name21, desc, schema], i) => {
@@ -222255,7 +222255,8 @@ Return a single JSON object keyed by paragraph tags. Only include paragraphs tha
     "relations": [{ "from": "UserService", "to": "Database", "type": "DEPENDS_ON", "confidence": 0.9 }]
   },
   "P3": {
-    "rules": [{ "description": "User must be authenticated before access", "expression": "user.isAuthenticated == true", "confidence": 0.85 }]
+    "constraints": [{ "description": "User must be authenticated before access", "severity": "must", "confidence": 0.9 }],
+    "rules": [{ "description": "Reject request if user is not authenticated", "expression": "IF !user.isAuthenticated THEN reject", "confidence": 0.85 }]
   }
 }
 
@@ -222268,6 +222269,11 @@ Return a single JSON object keyed by paragraph tags. Only include paragraphs tha
 - Every atom MUST include a "confidence" field (0.0-1.0) indicating how confident you are in the extraction. Use higher values (0.85-1.0) for explicitly stated facts and lower values (0.5-0.7) for inferred or ambiguous information.
 - **Classify correctly:** People, teams, and personas → "roles" (not "entities"). Technical systems, services, modules → "entities".
 - **Entity reference consistency (CRITICAL):** Every entity name referenced in relation.from, relation.to, behavior.subject, or any other cross-reference field MUST also appear in the "entities" array of the SAME paragraph (or a preceding paragraph in the same chunk). If an entity is mentioned for the first time in a relation, you MUST also extract it as an entity. This ensures no "dangling references" — every name used in relations has a corresponding entity declaration.
+- **Cross-atom reference consistency:** transitions[].from and transitions[].to values MUST exist in states[].values of the same entity. roles[].performs values MUST match names declared in behaviors[].name.
+- **Constraints vs rules distinction:** Use "constraints" for unconditional declarative mandates ('X must Y'). Use "rules" for conditional logic ('IF X THEN Y'). Do not mix them — a requirement with no condition is a constraint, a requirement triggered by a condition is a rule. Do NOT invent a rule for every constraint — only create a rule when the text explicitly states conditional logic.
+- **One statement, multiple atoms:** A single sentence can produce several atom types simultaneously. Do NOT force a choice — extract all that apply. Example: "system uptime must be ≥ 99.9%" → constraint (severity: must) + metric (threshold: "≥ 99.9%").
+- **Relation types:** Use standard relation types when possible: CONTAINS (parent→child composition), DEPENDS_ON (runtime dependency), IMPLEMENTS (code/component→spec realization), PRODUCES (process→output), TRIGGERS (event/process triggering), REFERENCES (weak cross-reference). Only invent a new type when none of these fit.
+- **Decisions:** Extract as "decisions" when the text records a deliberate choice between alternatives with rationale (e.g., "we chose X because Y", "after evaluating A/B/C, selected B"). Do not extract routine descriptions as decisions.
 - Respond in the same language as the input text (e.g., Chinese input → Chinese descriptions, English input → English descriptions).
 - JSON structure keys (tag, atom type names, field names) must always be in English.
 - Be thorough: extract ALL relevant atoms from each paragraph.
@@ -222325,10 +222331,10 @@ var ENTITY_RESOLUTION_SYSTEM_PROMPT = `You are an entity resolution assistant. Y
 - Abbreviations should be merged with their full forms (e.g. "AGW" → "API Gateway")
 
 ## Task 2: Remove Noise
-- Remove names that are NOT meaningful named entities — they are generic words, actions, or descriptions
-- Examples of noise: common verbs/nouns (登录, 路由, 直连), generic technical terms (Env, query), action descriptions (Kill 3001 进程)
-- Examples of REAL entities to KEEP: product names (TTAstra, Gulux), tools (nvm, Rush), services (Op Main 服务), platforms (AGW 平台)
-- When uncertain, KEEP the name — only remove if clearly not a named entity
+- Apply the **identity test**: a real entity is something you can discuss independently ("What is X?", "How does X work?", "Who owns X?"). Names that fail this test — values, addresses, actions, generic descriptions — are noise.
+- Remove names that are NOT meaningful named entities: generic words, action descriptions, or things that are attributes/values rather than independent subjects
+- Examples of REAL entities to KEEP: product names (TTAstra, Gulux), tools (nvm, Rush), services (Op Main 服务), platforms (AGW 平台) — these all pass the identity test
+- When uncertain, KEEP the name — only remove if it clearly fails the identity test
 
 ## Output
 Valid JSON only. No markdown fences, no explanation.`;
@@ -222571,7 +222577,7 @@ Each diagram paragraph is tagged with [P0], [P1], etc. You must classify the dia
    Relation schema: ${relationFields2}
 3. Extract action nodes as behaviors (what the process does at each step).
    Behavior schema: ${behaviorFields2}
-4. Extract diamond/decision nodes as decisions.
+4. Extract diamond/condition nodes: if it represents a deliberate choice with rationale → "decisions"; if it represents conditional branching logic (IF-THEN) → "rules".
    Decision schema: ${decisionFields}
 
 ### Sequence → entities + relations + behaviors + events
@@ -222604,9 +222610,9 @@ Each diagram paragraph is tagged with [P0], [P1], etc. You must classify the dia
    Relation schema: ${relationFields2}
 
 ### Architecture → entities + relations + constraints
-1. Extract each system/service/container/component as an entity.
+1. Extract each system/service/container/component as an entity. Use kind to indicate origin: "implementation" for internal systems/services, "external" for third-party dependencies (databases, cloud services, external APIs).
    Entity schema: ${entityFields2}
-2. Extract connections between components as relations.
+2. Extract connections between components as relations. Use standard types: CONTAINS (parent→child), DEPENDS_ON (runtime dependency), TRIGGERS (event/process triggering).
    Relation schema: ${relationFields2}
 3. Extract deployment constraints, technology choices.
    Constraint schema: ${constraintFields2}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@c4a/server-cli",
-  "version": "0.4.15-alpha.5",
+  "version": "0.4.15-alpha.6",
   "type": "module",
   "bin": {
     "c4a-server": "./index.js"

package/serve.js

@@ -196217,20 +196217,20 @@ class GleaningExtractor {
 // ../llm/src/prompts/docAtomAnnotation.ts
 init_src();
 var DOC_ATOM_DEFS = [
-  ["entities", "Named things: systems, services, modules, documents, APIs (NOT people/teams — use roles for those)", entityAtomSchema],
+  ["entities", "Named things with independent identity — something you can ask questions about ('What does X do?', 'Who owns X?'). Examples: systems, services, modules, APIs, products. If it is a value, address, path, or configuration detail, it is an attribute of an entity, not an entity itself. (NOT people/teams — use roles for those). kind: implementation=internal systems/services, external=third-party dependencies, concept=abstract/not-yet-implemented", entityAtomSchema],
   ["relations", "Connections between entities", relationAtomSchema],
   ["behaviors", "Actions/operations: functions, API calls, user actions, workflows", behaviorAtomSchema],
   ["attributes", "Properties of entities", attributeAtomSchema],
   ["states", "Possible states of entities", stateAtomSchema],
-  ["rules", "Business/domain rules: validations, constraints expressed as logic", ruleAtomSchema],
+  ["rules", "Conditional business/domain logic: IF condition THEN consequence (e.g., 'IF user not authenticated THEN reject request')", ruleAtomSchema],
   ["transitions", "State changes: from→to triggered by events or guards", transitionAtomSchema],
   ["events", "Occurrences that trigger behaviors", eventAtomSchema],
   ["decisions", "Architectural or business decisions", decisionAtomSchema],
   ["metrics", "Measurable targets: SLA, throughput, error_rate, with thresholds", metricAtomSchema],
-  ["roles", "Actors: human roles, teams, personas that perform behaviors", roleAtomSchema],
-  ["constraints", "Hard/soft requirements", constraintAtomSchema],
+  ["roles", "Actors: human roles, teams, personas that perform behaviors. kind: human=individual role, team=group/department, persona=user archetype. System-triggered actions use entity relations, NOT roles", roleAtomSchema],
+  ["constraints", "Declarative requirements: 'X must/should/must-not Y' (e.g., 'passwords must be >= 8 chars'). Unlike rules, constraints have no IF-THEN condition — they are unconditional mandates or restrictions", constraintAtomSchema],
   ["comparisons", "Side-by-side evaluations", comparisonAtomSchema],
-  ["boundaries", "System/domain boundaries: what is included vs excluded", boundaryAtomSchema]
+  ["boundaries", "Explicit scope declarations: what is included vs excluded. Only extract when the text explicitly declares scope (e.g., 'this product covers X but NOT Y'). Implicit containment (A runs inside B) is expressed via entity relations, not boundaries", boundaryAtomSchema]
 ];
 function buildAtomTypesBlock() {
   return DOC_ATOM_DEFS.map(([name21, desc, schema2], i) => {
@@ -196260,7 +196260,8 @@ Return a single JSON object keyed by paragraph tags. Only include paragraphs tha
     "relations": [{ "from": "UserService", "to": "Database", "type": "DEPENDS_ON", "confidence": 0.9 }]
   },
   "P3": {
-    "rules": [{ "description": "User must be authenticated before access", "expression": "user.isAuthenticated == true", "confidence": 0.85 }]
+    "constraints": [{ "description": "User must be authenticated before access", "severity": "must", "confidence": 0.9 }],
+    "rules": [{ "description": "Reject request if user is not authenticated", "expression": "IF !user.isAuthenticated THEN reject", "confidence": 0.85 }]
   }
 }
 
@@ -196273,6 +196274,11 @@ Return a single JSON object keyed by paragraph tags. Only include paragraphs tha
 - Every atom MUST include a "confidence" field (0.0-1.0) indicating how confident you are in the extraction. Use higher values (0.85-1.0) for explicitly stated facts and lower values (0.5-0.7) for inferred or ambiguous information.
 - **Classify correctly:** People, teams, and personas → "roles" (not "entities"). Technical systems, services, modules → "entities".
 - **Entity reference consistency (CRITICAL):** Every entity name referenced in relation.from, relation.to, behavior.subject, or any other cross-reference field MUST also appear in the "entities" array of the SAME paragraph (or a preceding paragraph in the same chunk). If an entity is mentioned for the first time in a relation, you MUST also extract it as an entity. This ensures no "dangling references" — every name used in relations has a corresponding entity declaration.
+- **Cross-atom reference consistency:** transitions[].from and transitions[].to values MUST exist in states[].values of the same entity. roles[].performs values MUST match names declared in behaviors[].name.
+- **Constraints vs rules distinction:** Use "constraints" for unconditional declarative mandates ('X must Y'). Use "rules" for conditional logic ('IF X THEN Y'). Do not mix them — a requirement with no condition is a constraint, a requirement triggered by a condition is a rule. Do NOT invent a rule for every constraint — only create a rule when the text explicitly states conditional logic.
+- **One statement, multiple atoms:** A single sentence can produce several atom types simultaneously. Do NOT force a choice — extract all that apply. Example: "system uptime must be ≥ 99.9%" → constraint (severity: must) + metric (threshold: "≥ 99.9%").
+- **Relation types:** Use standard relation types when possible: CONTAINS (parent→child composition), DEPENDS_ON (runtime dependency), IMPLEMENTS (code/component→spec realization), PRODUCES (process→output), TRIGGERS (event/process triggering), REFERENCES (weak cross-reference). Only invent a new type when none of these fit.
+- **Decisions:** Extract as "decisions" when the text records a deliberate choice between alternatives with rationale (e.g., "we chose X because Y", "after evaluating A/B/C, selected B"). Do not extract routine descriptions as decisions.
 - Respond in the same language as the input text (e.g., Chinese input → Chinese descriptions, English input → English descriptions).
 - JSON structure keys (tag, atom type names, field names) must always be in English.
 - Be thorough: extract ALL relevant atoms from each paragraph.
@@ -196330,10 +196336,10 @@ var ENTITY_RESOLUTION_SYSTEM_PROMPT = `You are an entity resolution assistant. Y
 - Abbreviations should be merged with their full forms (e.g. "AGW" → "API Gateway")
 
 ## Task 2: Remove Noise
-- Remove names that are NOT meaningful named entities — they are generic words, actions, or descriptions
-- Examples of noise: common verbs/nouns (登录, 路由, 直连), generic technical terms (Env, query), action descriptions (Kill 3001 进程)
-- Examples of REAL entities to KEEP: product names (TTAstra, Gulux), tools (nvm, Rush), services (Op Main 服务), platforms (AGW 平台)
-- When uncertain, KEEP the name — only remove if clearly not a named entity
+- Apply the **identity test**: a real entity is something you can discuss independently ("What is X?", "How does X work?", "Who owns X?"). Names that fail this test — values, addresses, actions, generic descriptions — are noise.
+- Remove names that are NOT meaningful named entities: generic words, action descriptions, or things that are attributes/values rather than independent subjects
+- Examples of REAL entities to KEEP: product names (TTAstra, Gulux), tools (nvm, Rush), services (Op Main 服务), platforms (AGW 平台) — these all pass the identity test
+- When uncertain, KEEP the name — only remove if it clearly fails the identity test
 
 ## Output
 Valid JSON only. No markdown fences, no explanation.`;
@@ -196576,7 +196582,7 @@ Each diagram paragraph is tagged with [P0], [P1], etc. You must classify the dia
    Relation schema: ${relationFields2}
 3. Extract action nodes as behaviors (what the process does at each step).
    Behavior schema: ${behaviorFields2}
-4. Extract diamond/decision nodes as decisions.
+4. Extract diamond/condition nodes: if it represents a deliberate choice with rationale → "decisions"; if it represents conditional branching logic (IF-THEN) → "rules".
    Decision schema: ${decisionFields}
 
 ### Sequence → entities + relations + behaviors + events
@@ -196609,9 +196615,9 @@ Each diagram paragraph is tagged with [P0], [P1], etc. You must classify the dia
    Relation schema: ${relationFields2}
 
 ### Architecture → entities + relations + constraints
-1. Extract each system/service/container/component as an entity.
+1. Extract each system/service/container/component as an entity. Use kind to indicate origin: "implementation" for internal systems/services, "external" for third-party dependencies (databases, cloud services, external APIs).
    Entity schema: ${entityFields2}
-2. Extract connections between components as relations.
+2. Extract connections between components as relations. Use standard types: CONTAINS (parent→child), DEPENDS_ON (runtime dependency), TRIGGERS (event/process triggering).
    Relation schema: ${relationFields2}
 3. Extract deployment constraints, technology choices.
    Constraint schema: ${constraintFields2}

package/web/assets/ContentDetail-C0zfArPg.js

@@ -0,0 +1 @@
+import{c as o,u as m,a as c,j as e,b as d,C as h}from"./index-BKETuM1m.js";const p=[["path",{d:"m12 19-7-7 7-7",key:"1l729n"}],["path",{d:"M19 12H5",key:"x3x0zl"}]],f=o("arrow-left",p);function j({icon:a,title:t,badges:s,meta:l}){const i=m(),{t:r}=c();return e.jsxs("div",{children:[e.jsxs("div",{className:"flex justify-between items-center",children:[e.jsxs("div",{className:"flex min-w-0 items-center gap-2",children:[e.jsx("span",{className:"shrink-0",children:a}),e.jsx("h1",{className:"min-w-0 break-all font-mono text-xl font-bold leading-none text-c4a-text-primary",children:t}),s&&s.length>0&&e.jsx("div",{className:"flex items-center gap-1.5 ml-2",children:s.map((n,x)=>e.jsx("span",{children:n},x))})]}),e.jsxs("button",{onClick:()=>i(-1),className:"flex items-center gap-1 text-c4a-text-muted hover:text-c4a-text-primary cursor-pointer transition-colors text-xs font-mono shrink-0 ml-4",children:[e.jsx(f,{size:14}),r("common.back")]})]}),l&&l.length>0&&e.jsx("div",{className:"mt-2 flex flex-wrap items-baseline gap-4 text-xs",children:l.map(n=>e.jsxs("span",{className:"text-c4a-text-muted",children:[n.label,"：",e.jsx("span",{className:"text-c4a-text-secondary",children:n.value})]},n.label))})]})}function N(){const{t:a}=c(),{hashId:t}=d();if(!t)return e.jsx("div",{className:"flex flex-1 items-center justify-center p-8",children:e.jsx("p",{className:"text-sm text-c4a-text-muted",children:a("common.loading")})});const s=t.length>16?t.slice(0,16)+"…":t;return e.jsxs("div",{className:"flex flex-1 flex-col p-4 md:p-6",children:[e.jsx(j,{icon:e.jsx("span",{children:"📄"}),title:`Content: ${s}`}),e.jsx(h,{hashId:t})]})}export{N as ContentDetail};

package/web/assets/EntityDetail-C9k4cMVL.js

@@ -0,0 +1 @@
+import{a as n,b as a,j as e,E as i}from"./index-BKETuM1m.js";function r(){const{t:s}=n(),{entityId:t}=a();return t?e.jsx("div",{className:"flex flex-1 flex-col p-4 md:p-6",children:e.jsx(i,{entityId:t})}):e.jsx("div",{className:"flex flex-1 items-center justify-center p-8",children:e.jsx("p",{className:"text-sm text-c4a-text-muted",children:s("common.loading")})})}export{r as EntityDetail};

package/web/assets/RelationDetail-BK8C5waL.js

@@ -0,0 +1 @@
+import{a,b as n,j as e,R as l}from"./index-BKETuM1m.js";function r(){const{t:s}=a(),{relationId:t}=n();return t?e.jsx("div",{className:"flex flex-1 flex-col p-4 md:p-6",children:e.jsx(l,{relationId:t})}):e.jsx("div",{className:"flex flex-1 items-center justify-center p-8",children:e.jsx("p",{className:"text-sm text-c4a-text-muted",children:s("common.loading")})})}export{r as RelationDetail};