yugoo-design 0.1.2 → 0.2.2

package/payload/overlays/codex/authoring/studio-creators/source/packages/skills-web-app/bundles/business_data/panel.yaml

@@ -0,0 +1,145 @@
+version: 1
+panel_kind: capability_map
+i18n:
+  default_locale: zh-CN
+  locales: {zh-CN: locales/zh-CN.json, en-US: locales/en-US.json}
+initial_values: {schema_version: 3}
+empty_description: $t:empty
+sections:
+  - id: objects
+    form: {header: {variant: detail, title: {field: name, editable: true}}}
+    title: $t:objects
+    item_name: $t:object
+    order: object_order
+    create: {id_field: id, defaults: {name: '', description: ''}}
+    confirm_delete: true
+    delete_relations: [{section: relations, reference_fields: [source, target]}]
+  - id: relations
+    form: {header: {variant: detail, title: {field: name, editable: true}}}
+    title: $t:relations
+    item_name: $t:relation
+    add_mode: graph
+    create: {id_field: id, defaults: {kind: association, name: '', description: ''}}
+    confirm_delete: true
+fields:
+  - {key: id, control: text, hidden: true, readonly: true, applies_to: [objects, relations]}
+  - {key: name, label: '$t:name', control: text, required: true, applies_to: [objects, relations]}
+  - {key: description, label: '$t:meaning', control: textarea, required_in: [objects], applies_to: [objects, relations]}
+  - key: fields
+    label: $t:fields
+    row_name: $t:field
+    control: record_map
+    id_field: id
+    order_field: field_order
+    item_label_field: name
+    item_collapsible: true
+    item_defaults: {name: '', meaning: '', value_type: text, requirement: optional, required_when: '', example: '', options: []}
+    applies_to: [objects]
+    item_fields:
+      - {key: name, label: '$t:fieldName', control: text, required: true}
+      - {key: meaning, label: '$t:fieldMeaning', control: textarea}
+      - key: value_type
+        label: $t:valueType
+        control: select
+        options:
+          - {value: text, label: '$t:typeText'}
+          - {value: long_text, label: '$t:typeLongText'}
+          - {value: number, label: '$t:typeNumber'}
+          - {value: amount, label: '$t:typeAmount'}
+          - {value: date, label: '$t:typeDate'}
+          - {value: date_time, label: '$t:typeDateTime'}
+          - {value: single_choice, label: '$t:typeSingle'}
+          - {value: multiple_choice, label: '$t:typeMultiple'}
+          - {value: yes_no, label: '$t:typeBoolean'}
+          - {value: file, label: '$t:typeFile'}
+          - {value: other, label: '$t:typeOther'}
+      - key: requirement
+        label: $t:requirement
+        control: radio
+        choice_layout: row_wrap
+        options:
+          - {value: optional, label: '$t:optional'}
+          - {value: always, label: '$t:always'}
+          - {value: conditional, label: '$t:conditional'}
+      - {key: required_when, label: '$t:requiredWhen', control: textarea, visible_when: {field: requirement, in: [conditional]}, clear_when_hidden: true}
+      - {key: options, label: '$t:options', control: list, visible_when: {field: value_type, in: [single_choice, multiple_choice]}, clear_when_hidden: true}
+      - {key: example, label: '$t:example', control: text}
+  - key: states
+    label: $t:states
+    row_name: $t:state
+    control: record_map
+    id_field: id
+    order_field: state_order
+    item_label_field: name
+    item_defaults: {name: '', meaning: ''}
+    applies_to: [objects]
+    item_fields:
+      - {key: name, label: '$t:stateName', control: text, required: true}
+      - {key: meaning, label: '$t:stateMeaning', control: textarea}
+  - key: kind
+    label: $t:relationKind
+    control: select
+    applies_to: [relations]
+    options:
+      - {value: association, label: '$t:association'}
+      - {value: generalization, label: '$t:generalization'}
+  - {key: source, label: '$t:source', control: record_select, options_from_section: objects, required: true, applies_to: [relations]}
+  - {key: target, label: '$t:target', control: record_select, options_from_section: objects, required: true, applies_to: [relations]}
+  - key: source_count
+    label: $t:sourceCount
+    description: $t:unknownCount
+    control: select
+    applies_to: [relations]
+    visible_when: {field: kind, in: [association]}
+    clear_when_hidden: omit
+    options:
+      - {value: '1', label: '$t:countOne'}
+      - {value: '0..1', label: '$t:countOptional'}
+      - {value: '1..*', label: '$t:countMany'}
+      - {value: '0..*', label: '$t:countAny'}
+  - key: target_count
+    label: $t:targetCount
+    description: $t:unknownCount
+    control: select
+    applies_to: [relations]
+    visible_when: {field: kind, in: [association]}
+    clear_when_hidden: omit
+    options:
+      - {value: '1', label: '$t:countOne'}
+      - {value: '0..1', label: '$t:countOptional'}
+      - {value: '1..*', label: '$t:countMany'}
+      - {value: '0..*', label: '$t:countAny'}
+ui:
+  component: record_workspace
+  sidebar_icon: database
+  id: business-objects
+  title: $t:objects
+  guidance: "$t:guidance"
+  sources: [objects, relations]
+  workspace_view: switch
+  children:
+    - component: relation_graph
+      id: business-graph
+      title: $t:relations
+      description: $t:graphHint
+      graph:
+        nodes: objects
+        edges: relations
+        source_field: source
+        target_field: target
+        label_field: name
+        node_description_field: description
+        edge_kind_field: kind
+        source_annotation_field: source_count
+        target_annotation_field: target_count
+        edge_defaults: {kind: association}
+        hierarchy:
+          values: [generalization]
+          label: $t:parents
+          description: $t:parentHint
+          create:
+            edge_kind: generalization
+            create_label: $t:createSubtype
+            create_title: $t:createSubtypeTitle
+        reverse: {label: '$t:reverse', pairs: [[source_count, target_count]]}
+    - {component: record_inspector, id: business-inspector}

package/payload/overlays/codex/authoring/studio-creators/source/packages/skills-web-app/bundles/business_data/reference/artifact-contract.md

@@ -0,0 +1,151 @@
+# business_data output contract
+
+For canvas generation or revision, read [the canvas guide](canvas-guide.md).
+It supplements the existing methods and output contract; it applies to both
+new design and reconstruction without replacing domain-specific rules.
+
+## Source-to-business-object judgment
+
+For new design, derive information from the lasting business things required by
+the agreed scenarios, not a generic database template. For reconstruction,
+trace how the product creates, identifies, reads and changes those things.
+Tables, DTOs, caches and joins are implementation evidence, not a one-to-one
+business object list. Translate only supported user-meaningful information;
+a technical join does not by itself establish composition or inheritance.
+
+Verify field requirements against relevant behavior and conditions, not only
+a nullable column or a sample record. An enum does not prove every state is
+reachable. Check both directions of a relationship before assigning quantities;
+one observed example does not establish a maximum. Preserve evidence limits in
+existing descriptions or the handoff, without adding provenance/status fields
+outside the schema. When a required representation cannot faithfully express
+the source, report that limitation rather than inventing a value.
+
+For revisions, distinguish a source implementation change from a requested
+design change. Preserve unaffected saved vocabulary and IDs; explain conflicts
+with user decisions instead of silently importing a new database-shaped model.
+Check the result against a concrete source-backed usage situation, separately
+from schema validation.
+
+Canonical state is `business_data/business_data.json`. This contract is shared
+by ordinary design, saved-panel continuation and reconstruction. Read it through
+the installed Bundle resource root. Schema and validation are authoritative;
+examples are hypothetical, never user evidence.
+
+## Meaning and ownership
+
+A business object is a lasting, user-recognisable type of thing, not a database
+table, screen, action or report. Fields describe the information needed to
+recognize or use an instance. States name situations, not transitions.
+Relationships describe connections between those object types; they are not
+another collection of business objects. Workflow behavior, permission,
+calculation and storage design remain with their existing owners.
+
+Walk an established usage situation. Can the reader distinguish the intended
+instance when display names repeat or change? Use evidenced business information;
+do not invent foreign keys, audit columns or technical timestamps.
+For an association, explain what connects the instances, quantity in both
+directions when known, and any evidenced ownership/deletion implications.
+Missing evidence remains a named open decision.
+
+## Existing state
+
+Keep `schema_version: 3`; `web_app` and this Bundle remain version 1.0.
+`objects` is keyed by stable ID. `object_order` contains every object key once.
+Each object has `id`, `name`, `description`, `fields`, `field_order`,
+`states`, `state_order`. Keys equal nested IDs. Field/state order lists
+cover their own maps exactly once.
+
+Fields: `id`, `name`, `meaning`, `value_type`, `requirement`,
+`required_when`, `example`, `options`. Value types are `text`,
+`long_text`, `number`, `amount`, `date`, `date_time`, `single_choice`,
+`multiple_choice`, `yes_no`, `file`, `other`. Requirements are
+`optional`, `always`, `conditional`. Only conditional requirements use
+a nonempty `required_when`. Choice fields use unique visible `options`;
+other fields use `[]`. States contain only `id`, `name`, `meaning`.
+
+No approval flags, initial/terminal flags, technical storage or arbitrary keys.
+
+## Optional relationships
+
+`relations` is an optional stable-key map. Existing v3 files without it remain
+valid and need no migration. Omit it or use `{}` when no relations are known.
+There is no `relation_order`: relations are not a sequence, and views derive a
+deterministic display by stable ID. Do not introduce order as a second fact.
+
+Each closed relation record has:
+
+| Field | Meaning |
+| --- | --- |
+| `id` | Equals its map key; rename does not change it. |
+| `kind` | `association` or `generalization`. |
+| `name` | User-readable relationship verb, such as 引用 or 是一种. |
+| `source` | Stable ID of an existing object in this same file. |
+| `target` | Stable ID of an existing object in this same file. |
+| `description` | Optional plain-language meaning, constraints and uncertainty. |
+| `source_count` | Association only: number of source instances for one target. |
+| `target_count` | Association only: number of target instances for one source. |
+
+Association quantities use `1` (exactly one), `0..1` (none or one),
+`1..*` (one or more), `0..*` (none or more). A missing quantity means
+undecided; do not store an empty string, a UI label, or a fabricated default.
+For “project references paper”, `target_count` describes papers per project;
+`source_count` describes projects per paper. The panel renders Chinese
+sentences rather than symbols. A same-type association can be valid
+(e.g. task depends on task); do not apply inheritance restrictions to it.
+
+Generalization connects subtype `source` to parent `target` and contains
+no quantity fields. It means “an experimental project is a kind of project”.
+It does not mean “a project contains an experimental project”, a concrete
+instance belonging to a class, or provenance “generated from”.
+Self-inheritance and any inheritance cycle are invalid. Multiple parents are
+permitted; a diamond is not a cycle. Store coherent evidence, not an OWL
+reasoner or an unbounded relation inventory.
+
+Inherited definitions, fields and states remain at their parent. A subtype
+stores its own additions and may have no local fields; never copy parent
+fields just to satisfy a field-count check. The form displays local fields
+and links to parent definitions. It does not compute a merged effective-field
+schema. If multiple parents define conflicting information or requirements,
+report the conflict and obtain a product decision; do not silently choose
+one or overwrite definitions. Downstream rule/access/PRD consumers continue
+to read explicitly declared records and relationships; they must not assume
+a computed inheritance closure or generate duplicate field IDs.
+
+## Editing and consumers
+
+Form and canvas share this one canonical file. Renaming keeps stable endpoints.
+Removing an object removes all incident relationships in the same state edit;
+removing an edge preserves the endpoint objects. Preserve unaffected fields,
+states, quantities, names and relations on partial revisions. Splitting or
+merging a type requires deliberate repair of its endpoints.
+A panel save already persisted the edits: never replay that diff.
+
+Canvas coordinates, hover state, selection, collapsed branches and viewport
+are presentation state and never written into Design Files. The canvas shows
+object summaries and relationships. Node hover offers details that return to
+the selected object's existing form, revealing its parent branches. Line
+Chevron toggles and controls reuse the native Panel style.
+
+Reference annotations on `source`/`target` let the existing KAG projection
+resolve exact endpoints. Relation names, descriptions and quantities remain
+source evidence for GRA. An identifier/reference edge alone does not declare
+a new business inference; read the owning relation. The native generic
+summary reports collection counts; read canonical records for substantive
+reasoning. PRD assembly explains declared relationships in ordinary language,
+including unknown quantities, instead of inferring unsupported inheritance.
+
+## Example and checks
+
+Read [the complete example](example.json): Project, Experimental Project and
+Paper, including inheritance and a many-to-many association. It is not a
+proposal for the user's scope.
+
+Validate shape, map-key identity, object order, endpoint resolution, absence
+of quantities on inheritance, and inheritance cycles through the Host's
+actual checkpoint. At completion every present relation has a nonempty name.
+Root objects should have the grounded information needed by current usage;
+subtypes may inherit it without local copies. Professional self-checks:
+distinct meanings; field/state names and meanings; visible unique options;
+conditional requirements; exact local orders; no unsupported relations.
+Preserve intentional unknowns instead of manufacturing a complete ontology.

package/payload/overlays/codex/authoring/studio-creators/source/packages/skills-web-app/bundles/business_data/reference/canvas-guide.md

@@ -0,0 +1,40 @@
+# Business object relationship canvas
+
+This is the shared design/reconstruction reading entry, not a new data model.
+Read [the output contract](artifact-contract.md) for complete field meaning,
+association quantities, subtype inheritance, examples and validation. Ordinary
+design also follows the existing Bundle SKILL; reconstruction preserves source
+facts rather than applying new modeling preferences.
+
+## Facts and meaning
+
+`business_data/business_data.json` owns objects and named relationships. Stable
+object/relation IDs bind the graph and form. Nodes are durable business types,
+not pages, actions, database tables or concrete instances. Association and
+generalization are distinct. Subtype source points to parent target; composition,
+instance membership and provenance are not inheritance. Preserve quantities and
+unknowns; parent fields remain at the parent, not copied onto child records.
+
+## Layout, routing and unknowns
+
+The declaration uses the shared `relation_graph`, with object summaries and
+selection returning to the original object form. Placement/grouping is a view,
+not a new business fact. Coordinates, viewport and collapsed branches are not
+saved here. The installed renderer owns layout, ports and label avoidance;
+do not generate private diagram coordinates or apply AI's three-layer layout.
+Readable association/generalization labels and their direction must follow the
+actual relationship. Genuine density is not evidence that a relation is wrong.
+Missing/conflicting facts stay explicit; never infer quantities or effective
+multiple-inheritance conflict resolution from visual proximity.
+
+## Interaction, saving and examples
+
+Use the existing same-source editor/atomic save path. Renaming preserves IDs;
+removing a relation preserves objects; removing an object repairs its incident
+relations in the same state edit. Do not reapply an accepted Panel diff.
+Read [the existing synthetic example](example.json), not a second preview.
+Check association versus inheritance, both quantity directions, unresolved
+endpoints, cycles/self-inheritance and allowed multiple-parent diamonds.
+Review labels, resize/long text/narrow canvas and selected-record identity with
+a real view when available; report schema, rendering and save/reopen separately.
+No existing example or written rule establishes actual rendered acceptance.

package/payload/overlays/codex/authoring/studio-creators/source/packages/skills-web-app/bundles/business_data/reference/example.json

@@ -0,0 +1,24 @@
+{
+  "schema_version": 3,
+  "object_order": ["project", "experimental-project", "paper"],
+  "objects": {
+    "project": {
+      "id": "project", "name": "项目", "description": "围绕研究目标组织任务和参考资料的工作单元。",
+      "fields": {"title": {"id": "title", "name": "项目名称", "meaning": "用于识别和查找项目的名称。", "value_type": "text", "requirement": "always", "required_when": "", "example": "开放数据分析", "options": []}},
+      "field_order": ["title"], "states": {}, "state_order": []
+    },
+    "experimental-project": {
+      "id": "experimental-project", "name": "实验项目", "description": "通过实验推进研究的项目类型，沿用项目的通用定义与信息。",
+      "fields": {}, "field_order": [], "states": {}, "state_order": []
+    },
+    "paper": {
+      "id": "paper", "name": "文献", "description": "独立保存且可被不同项目引用的学术资料。",
+      "fields": {"title": {"id": "title", "name": "文献标题", "meaning": "用户阅读和查找文献时看到的标题。", "value_type": "text", "requirement": "always", "required_when": "", "example": "开放科研实践", "options": []}},
+      "field_order": ["title"], "states": {}, "state_order": []
+    }
+  },
+  "relations": {
+    "inherits-project": {"id": "inherits-project", "kind": "generalization", "name": "是一种", "source": "experimental-project", "target": "project", "description": "实验项目是项目的一种，不是项目中的一个实例。"},
+    "references-paper": {"id": "references-paper", "kind": "association", "name": "引用", "source": "project", "target": "paper", "source_count": "0..*", "target_count": "0..*", "description": "项目可引用多篇文献，文献可被多个项目引用。移除引用不删除文献。"}
+  }
+}

package/payload/overlays/codex/authoring/studio-creators/source/packages/skills-web-app/bundles/business_data/reference/preview.json

@@ -0,0 +1,24 @@
+{
+  "schema_version": 3,
+  "object_order": ["project", "experimental-project", "paper"],
+  "objects": {
+    "project": {
+      "id": "project", "name": "项目", "description": "合成预览示例：围绕研究目标组织任务和参考资料的工作单元，不是用户事实。",
+      "fields": {"title": {"id": "title", "name": "项目名称", "meaning": "用于识别和查找项目的名称。", "value_type": "text", "requirement": "always", "required_when": "", "example": "开放数据分析", "options": []}},
+      "field_order": ["title"], "states": {}, "state_order": []
+    },
+    "experimental-project": {
+      "id": "experimental-project", "name": "实验项目", "description": "合成预览示例：通过实验推进研究的项目类型，沿用项目的通用定义与信息。",
+      "fields": {}, "field_order": [], "states": {}, "state_order": []
+    },
+    "paper": {
+      "id": "paper", "name": "文献", "description": "合成预览示例：独立保存且可被不同项目引用的学术资料。",
+      "fields": {"title": {"id": "title", "name": "文献标题", "meaning": "用户阅读和查找文献时看到的标题。", "value_type": "text", "requirement": "always", "required_when": "", "example": "开放科研实践", "options": []}},
+      "field_order": ["title"], "states": {}, "state_order": []
+    }
+  },
+  "relations": {
+    "inherits-project": {"id": "inherits-project", "kind": "generalization", "name": "是一种", "source": "experimental-project", "target": "project", "description": "实验项目是项目的一种，不是项目中的一个实例。"},
+    "references-paper": {"id": "references-paper", "kind": "association", "name": "引用", "source": "project", "target": "paper", "source_count": "0..*", "target_count": "0..*", "description": "示例中项目可引用多篇文献，文献可被多个项目引用。移除引用不删除文献。"}
+  }
+}

package/payload/overlays/codex/authoring/studio-creators/source/packages/skills-web-app/bundles/business_data/schema.yaml

@@ -0,0 +1,67 @@
+# business_data Design Files contract, translated from BusinessDataState v3.
+type: object
+additional_properties: false
+required: [schema_version, objects, object_order]
+properties:
+  skill_name: { knowledge: { role: metadata }, type: string }
+  schema_version: { knowledge: { role: metadata }, type: enum, values: [3] }
+  object_order: { knowledge: { role: metadata }, type: array, items: { type: string } }
+  relations:
+    type: map
+    value:
+      type: object
+      additional_properties: false
+      knowledge: { role: content, granularity: unit, label: 对象关系 }
+      required: [id, kind, name, source, target]
+      properties:
+        id: { knowledge: { role: metadata }, type: string }
+        kind: { type: enum, values: [association, generalization] }
+        name: { type: string }
+        source:
+          type: string
+          knowledge: { role: reference, target: "business_data/business_data.json#/objects" }
+        target:
+          type: string
+          knowledge: { role: reference, target: "business_data/business_data.json#/objects" }
+        description: { type: string }
+        source_count: { type: enum, values: ["1", "0..1", "1..*", "0..*"] }
+        target_count: { type: enum, values: ["1", "0..1", "1..*", "0..*"] }
+  objects:
+    type: map
+    value:
+      type: object
+      additional_properties: false
+      required: [id, name]
+      properties:
+        id: { type: string }
+        name: { type: string }
+        description: { type: string }
+        fields:
+          type: map
+          value:
+            type: object
+            additional_properties: false
+            required: [id, name]
+            properties:
+              id: { type: string }
+              name: { type: string }
+              meaning: { type: string }
+              value_type:
+                type: enum
+                values: [text, long_text, number, amount, date, date_time, single_choice, multiple_choice, yes_no, file, other]
+              requirement: { type: enum, values: [optional, always, conditional] }
+              required_when: { type: string }
+              example: { type: string }
+              options: { type: array, items: { type: string } }
+        field_order: { knowledge: { role: metadata }, type: array, items: { type: string } }
+        states:
+          type: map
+          value:
+            type: object
+            additional_properties: false
+            required: [id, name]
+            properties:
+              id: { type: string }
+              name: { type: string }
+              meaning: { type: string }
+        state_order: { knowledge: { role: metadata }, type: array, items: { type: string } }

package/payload/overlays/codex/authoring/studio-creators/source/packages/skills-web-app/bundles/business_data/validation.yaml

@@ -0,0 +1,92 @@
+# business_data semantic validation translated from schema.py and deliverables.py.
+skill: business_data
+
+rules:
+  - id: empty
+    scope: [state]
+    code: business_data.empty
+    message: "objects has no business things"
+    check: { non_empty_map: objects }
+
+  - id: empty_order
+    scope: [state]
+    code: business_data.empty_order
+    message: "object_order is empty, so no business thing can render."
+    check: { non_empty_list: object_order }
+
+  - id: object_key_mismatch
+    scope: [state]
+    code: business_data.object_key_mismatch
+    message: "business object mapping key {key} must equal its id"
+    check: { map_keys_match_field: { map: objects, field: id } }
+
+  - id: invalid_object_order
+    scope: [state]
+    code: business_data.invalid_object_order
+    message: "object_order must contain business object {key} exactly once"
+    check: { order_exactly_covers_map: { order: object_order, map: objects } }
+
+  - id: empty_name
+    scope: [completion]
+    code: business_data.empty_name
+    message: "business object {key} has no name"
+    check:
+      for_each_in_order: { order: object_order, map: objects }
+      non_empty_string: name
+
+  - id: empty_description
+    scope: [completion]
+    code: business_data.empty_description
+    message: "business object {key} has no description"
+    check:
+      for_each_in_order: { order: object_order, map: objects }
+      non_empty_string: description
+
+  - id: relation_key_mismatch
+    scope: [state]
+    code: business_data.relation_key_mismatch
+    message: "relation mapping key {key} must equal its id"
+    check: { map_keys_match_field: { map: relations, field: id } }
+
+  - id: relation_source
+    scope: [state]
+    code: business_data.relation_source
+    message: "relation {key} source must identify an existing business object"
+    check:
+      for_each_in_map: relations
+      member_of_map: { value: source, map: objects }
+
+  - id: relation_target
+    scope: [state]
+    code: business_data.relation_target
+    message: "relation {key} target must identify an existing business object"
+    check:
+      for_each_in_map: relations
+      member_of_map: { value: target, map: objects }
+
+  - id: inheritance_cycle
+    scope: [state]
+    code: business_data.inheritance_cycle
+    message: "inheritance relation {key} creates a cycle; a type cannot be its own ancestor"
+    check:
+      acyclic_record_edges:
+        map: relations
+        source: source
+        target: target
+        where: { field: kind, equals: generalization }
+
+  - id: relation_name
+    scope: [completion]
+    code: business_data.relation_name
+    message: "relation {key} needs a user-readable name"
+    check: { for_each_in_map: relations, non_empty_string: name }
+
+  - id: inheritance_counts
+    scope: [state]
+    code: business_data.inheritance_counts
+    message: "inheritance relation {key} must not declare instance quantities"
+    check:
+      for_each_in_map: relations
+      fields_absent_when: { field: kind, equals: generalization, fields: [source_count, target_count] }
+
+  # Rich design-quality checks remain executor self-checks in SKILL.md.