archgraph-argo 0.6.5 → 0.6.7
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
|
Binary file
|
|
@@ -1,207 +1,83 @@
|
|
|
1
|
-
{
|
|
2
|
-
"name": "System",
|
|
3
|
-
"description": "Exported from EA package System",
|
|
4
|
-
"elements": [
|
|
5
|
-
{
|
|
6
|
-
"id": "
|
|
7
|
-
"name": "
|
|
8
|
-
"
|
|
9
|
-
"
|
|
10
|
-
"
|
|
11
|
-
{
|
|
12
|
-
"
|
|
13
|
-
"
|
|
14
|
-
}
|
|
15
|
-
]
|
|
16
|
-
|
|
17
|
-
|
|
18
|
-
|
|
19
|
-
|
|
20
|
-
|
|
21
|
-
|
|
22
|
-
|
|
23
|
-
|
|
24
|
-
|
|
25
|
-
|
|
26
|
-
|
|
27
|
-
|
|
28
|
-
|
|
29
|
-
|
|
30
|
-
|
|
31
|
-
|
|
32
|
-
|
|
33
|
-
|
|
34
|
-
|
|
35
|
-
|
|
36
|
-
|
|
37
|
-
|
|
38
|
-
|
|
39
|
-
|
|
40
|
-
|
|
41
|
-
|
|
42
|
-
"
|
|
43
|
-
"
|
|
44
|
-
|
|
45
|
-
|
|
46
|
-
|
|
47
|
-
|
|
48
|
-
|
|
49
|
-
|
|
50
|
-
|
|
51
|
-
|
|
52
|
-
"
|
|
53
|
-
|
|
54
|
-
|
|
55
|
-
|
|
56
|
-
|
|
57
|
-
|
|
58
|
-
|
|
59
|
-
|
|
60
|
-
"
|
|
61
|
-
"
|
|
62
|
-
|
|
63
|
-
|
|
64
|
-
"
|
|
65
|
-
|
|
66
|
-
|
|
67
|
-
|
|
68
|
-
|
|
69
|
-
]
|
|
70
|
-
|
|
71
|
-
|
|
72
|
-
|
|
73
|
-
|
|
74
|
-
|
|
75
|
-
|
|
76
|
-
|
|
77
|
-
|
|
78
|
-
"
|
|
79
|
-
|
|
80
|
-
|
|
81
|
-
|
|
82
|
-
|
|
83
|
-
{
|
|
84
|
-
"name": "modelingSkillPaths",
|
|
85
|
-
"value": ".argo/skills/modeling/project-viewpoint/SKILL.md; .argo/skills/modeling/migration-viewpoint/SKILL.md; .argo/skills/modeling/implementation-migration-viewpoint/SKILL.md; .argo/skills/modeling/layered-viewpoint/SKILL.md; .argo/skills/modeling/physical-viewpoint/SKILL.md"
|
|
86
|
-
}
|
|
87
|
-
],
|
|
88
|
-
"subdiagram_views": [
|
|
89
|
-
{
|
|
90
|
-
"view_id": "163",
|
|
91
|
-
"view_name": "AcceptanceDeliveryViewpoint"
|
|
92
|
-
}
|
|
93
|
-
]
|
|
94
|
-
}
|
|
95
|
-
],
|
|
96
|
-
"relationships": [
|
|
97
|
-
{
|
|
98
|
-
"id": "3001",
|
|
99
|
-
"name": "Baseline viewpoint association",
|
|
100
|
-
"type": "Association",
|
|
101
|
-
"source_id": "1207",
|
|
102
|
-
"target_id": "1208",
|
|
103
|
-
"source_name": "StakeholderIntentViewpoint",
|
|
104
|
-
"target_name": "OutcomeCapabilityViewpoint",
|
|
105
|
-
"description": "Baseline navigation from stakeholder intent to outcome and capability scope.",
|
|
106
|
-
"statement": "StakeholderIntentViewpoint --(Association)--> OutcomeCapabilityViewpoint"
|
|
107
|
-
},
|
|
108
|
-
{
|
|
109
|
-
"id": "3002",
|
|
110
|
-
"name": "Baseline viewpoint association",
|
|
111
|
-
"type": "Association",
|
|
112
|
-
"source_id": "1208",
|
|
113
|
-
"target_id": "1209",
|
|
114
|
-
"source_name": "OutcomeCapabilityViewpoint",
|
|
115
|
-
"target_name": "BusinessBehaviorViewpoint",
|
|
116
|
-
"description": "Baseline navigation from outcome and capability scope to observable business behavior.",
|
|
117
|
-
"statement": "OutcomeCapabilityViewpoint --(Association)--> BusinessBehaviorViewpoint"
|
|
118
|
-
},
|
|
119
|
-
{
|
|
120
|
-
"id": "3003",
|
|
121
|
-
"name": "Baseline viewpoint association",
|
|
122
|
-
"type": "Association",
|
|
123
|
-
"source_id": "1209",
|
|
124
|
-
"target_id": "1210",
|
|
125
|
-
"source_name": "BusinessBehaviorViewpoint",
|
|
126
|
-
"target_name": "CapabilityRealizationViewpoint",
|
|
127
|
-
"description": "Baseline navigation from business behavior to capability realization responsibilities.",
|
|
128
|
-
"statement": "BusinessBehaviorViewpoint --(Association)--> CapabilityRealizationViewpoint"
|
|
129
|
-
},
|
|
130
|
-
{
|
|
131
|
-
"id": "3004",
|
|
132
|
-
"name": "Baseline viewpoint association",
|
|
133
|
-
"type": "Association",
|
|
134
|
-
"source_id": "1210",
|
|
135
|
-
"target_id": "1211",
|
|
136
|
-
"source_name": "CapabilityRealizationViewpoint",
|
|
137
|
-
"target_name": "AcceptanceDeliveryViewpoint",
|
|
138
|
-
"description": "Baseline navigation from realization responsibilities to acceptance and delivery sequencing.",
|
|
139
|
-
"statement": "CapabilityRealizationViewpoint --(Association)--> AcceptanceDeliveryViewpoint"
|
|
140
|
-
}
|
|
141
|
-
],
|
|
142
|
-
"views": [
|
|
143
|
-
{
|
|
144
|
-
"view_id": "159",
|
|
145
|
-
"view_name": "StakeholderIntentViewpoint",
|
|
146
|
-
"parent_element_id": "1207",
|
|
147
|
-
"parent_element_name": "StakeholderIntentViewpoint",
|
|
148
|
-
"description": "ArchiMate-inspired motivation viewpoint for framing stakeholder concerns before modeling solution details. Stakeholders: business partners, business managers, requirements owners, enterprise architects, and acceptors. Concerns: architecture mission, drivers for change, assessments, high-level goals, desired outcomes, value, principles, and hard constraints. Purpose: designing, deciding, and informing. Scope: motivation and strategy context. Use this view to answer who cares, why the change matters, what success means, and which constraints cannot be violated. Typical elements: Stakeholder, Driver, Assessment, Goal, Outcome, Value, Meaning, Principle, Requirement, Constraint, Course of Action. Do not place implementation components here unless they are needed only as evidence for a stakeholder concern.",
|
|
149
|
-
"included_elements": [],
|
|
150
|
-
"included_relationships": []
|
|
151
|
-
},
|
|
152
|
-
{
|
|
153
|
-
"view_id": "160",
|
|
154
|
-
"view_name": "OutcomeCapabilityViewpoint",
|
|
155
|
-
"parent_element_id": "1208",
|
|
156
|
-
"parent_element_name": "OutcomeCapabilityViewpoint",
|
|
157
|
-
"description": "ArchiMate-inspired strategy viewpoint combining Strategy, Capability Map, Value Stream, and Outcome Realization concerns. Stakeholders: business managers, product owners, enterprise architects, business architects, and portfolio decision-makers. Concerns: business-oriented results, capability boundaries, value streams, resources, investment focus, and capability-to-outcome coverage. Purpose: designing and deciding. Scope: strategy with links to motivation and core elements when needed. Use this view to answer what business outcomes are in scope, which capabilities create or support them, and where value is produced. Typical elements: Outcome, Capability, Value Stream, Resource, Course of Action, Product, Value, Meaning, and selectively core elements that realize outcomes. Do not decompose detailed workflows or technical implementation here.",
|
|
158
|
-
"included_elements": [],
|
|
159
|
-
"included_relationships": []
|
|
160
|
-
},
|
|
161
|
-
{
|
|
162
|
-
"view_id": "161",
|
|
163
|
-
"view_name": "BusinessBehaviorViewpoint",
|
|
164
|
-
"parent_element_id": "1209",
|
|
165
|
-
"parent_element_name": "BusinessBehaviorViewpoint",
|
|
166
|
-
"description": "ArchiMate-inspired business behavior viewpoint drawing from Organization, Product, and Business Process Cooperation viewpoints. Stakeholders: process owners, domain experts, operational managers, business analysts, and product managers. Concerns: responsibilities, authority, business process dependencies, business services, product composition, contracts, shared information, and observable business events. Purpose: designing, deciding, and informing. Scope: mainly Business layer, with application links only when they explain business process support. Use this view to answer how the business works, who performs behavior, what events trigger it, what business objects are used, and what services or products are exposed. Typical elements: Business Actor, Business Role, Business Collaboration, Business Process, Business Function, Business Interaction, Business Event, Business Service, Business Object, Contract, Product, Representation. Do not turn this view into an application structure or code module map.",
|
|
167
|
-
"included_elements": [],
|
|
168
|
-
"included_relationships": []
|
|
169
|
-
},
|
|
170
|
-
{
|
|
171
|
-
"view_id": "162",
|
|
172
|
-
"view_name": "CapabilityRealizationViewpoint",
|
|
173
|
-
"parent_element_id": "1210",
|
|
174
|
-
"parent_element_name": "CapabilityRealizationViewpoint",
|
|
175
|
-
"description": "ArchiMate-inspired realization and usage viewpoint combining Requirements Realization, Application Usage, Service Realization, Application Cooperation, and Implementation and Deployment concerns. Stakeholders: enterprise architects, application architects, solution architects, process architects, and implementation designers. Concerns: how requirements, capabilities, business processes, and business services are realized by application services, components, data objects, and supporting technology; consistency, completeness, dependency visibility, and service orchestration. Purpose: designing and deciding. Scope: multiple layers and multiple aspects, but only along business-to-system realization paths. Use this view to answer how a business capability is carried by system responsibilities and which application or technology elements are relevant to that realization. Typical elements: Requirement, Constraint, Capability, Business Service, Business Process, Application Service, Application Component, Application Interface, Application Function or Process, Data Object, Technology Service, Node, Artifact. Do not include low-level implementation detail unless it changes a business-visible responsibility or dependency.",
|
|
176
|
-
"included_elements": [],
|
|
177
|
-
"included_relationships": []
|
|
178
|
-
},
|
|
179
|
-
{
|
|
180
|
-
"view_id": "163",
|
|
181
|
-
"view_name": "AcceptanceDeliveryViewpoint",
|
|
182
|
-
"parent_element_id": "1211",
|
|
183
|
-
"parent_element_name": "AcceptanceDeliveryViewpoint",
|
|
184
|
-
"description": "ArchiMate-inspired implementation and migration viewpoint extended with ARGO acceptance semantics. Stakeholders: business acceptors, project managers, operational managers, enterprise architects, delivery owners, and downstream agents. Concerns: acceptance control points, observation points, risk, work package scope, deliverables, plateaus, gaps, migration order, cross-cutting concerns, and consistency between delivery dependencies and architecture dependencies. Purpose: deciding and informing, with enough design detail to plan delivery. Scope: implementation and migration plus explicit business acceptance semantics. Use this view to answer how the change will be accepted, what must be observed, which work packages or plateaus are involved, what depends on what, and what risks could invalidate delivery. Typical elements: Goal, Outcome, Requirement, Constraint, Work Package, Deliverable, Implementation Event, Plateau, Gap, Business Actor, Business Role, and core elements affected by delivery. Do not use this view as a backlog dump; every item must affect acceptance, sequencing, or risk.",
|
|
185
|
-
"included_elements": [],
|
|
186
|
-
"included_relationships": []
|
|
187
|
-
},
|
|
188
|
-
{
|
|
189
|
-
"view_id": "158",
|
|
190
|
-
"view_name": "SystemArchitecture",
|
|
191
|
-
"description": "Top-level baseline architecture map governed by five universal business viewpoints. It follows the ArchiMate viewpoint mechanism: select content by stakeholder concerns, purpose, and scope, not by layer folders. The five child viewpoints provide the default AI navigation path from stakeholder intent to outcomes and capabilities, business behavior, capability realization, and acceptance-delivery sequencing. ArchiMate layers remain implicit in element types and may be used by validators or specialized sub-views, but they are not the default modeling entry point.",
|
|
192
|
-
"included_elements": [
|
|
193
|
-
"1207",
|
|
194
|
-
"1208",
|
|
195
|
-
"1209",
|
|
196
|
-
"1210",
|
|
197
|
-
"1211"
|
|
198
|
-
],
|
|
199
|
-
"included_relationships": [
|
|
200
|
-
"3001",
|
|
201
|
-
"3002",
|
|
202
|
-
"3003",
|
|
203
|
-
"3004"
|
|
204
|
-
]
|
|
205
|
-
}
|
|
206
|
-
]
|
|
1
|
+
{
|
|
2
|
+
"name": "System",
|
|
3
|
+
"description": "Exported from EA package System\r\n\r\nImported from: D:\\Projects\\Argo\\design\\KG\\SystemArchitecture.json\r\nSchema: .argo/schema/SystemArchitecture.schema.json",
|
|
4
|
+
"elements": [
|
|
5
|
+
{
|
|
6
|
+
"id": "1240",
|
|
7
|
+
"name": "Application Cooperation Viewpoint",
|
|
8
|
+
"alias": "1211",
|
|
9
|
+
"type": "Grouping",
|
|
10
|
+
"subdiagram_views": [
|
|
11
|
+
{
|
|
12
|
+
"view_id": "169",
|
|
13
|
+
"view_name": "Application Cooperation"
|
|
14
|
+
}
|
|
15
|
+
]
|
|
16
|
+
},
|
|
17
|
+
{
|
|
18
|
+
"id": "1249",
|
|
19
|
+
"name": "Implementation and Migration Viewpoint",
|
|
20
|
+
"alias": "1211",
|
|
21
|
+
"type": "Grouping",
|
|
22
|
+
"subdiagram_views": [
|
|
23
|
+
{
|
|
24
|
+
"view_id": "176",
|
|
25
|
+
"view_name": "AgentCapabilities"
|
|
26
|
+
},
|
|
27
|
+
{
|
|
28
|
+
"view_id": "174",
|
|
29
|
+
"view_name": "Implementation and Migration"
|
|
30
|
+
}
|
|
31
|
+
]
|
|
32
|
+
}
|
|
33
|
+
],
|
|
34
|
+
"relationships": [
|
|
35
|
+
{
|
|
36
|
+
"id": "1161",
|
|
37
|
+
"statement": "Implementation and Migration Viewpoint --(Association)--> Application Cooperation Viewpoint",
|
|
38
|
+
"name": "Association",
|
|
39
|
+
"type": "Association",
|
|
40
|
+
"source_id": "1249",
|
|
41
|
+
"target_id": "1240",
|
|
42
|
+
"source_name": "Implementation and Migration Viewpoint",
|
|
43
|
+
"target_name": "Application Cooperation Viewpoint"
|
|
44
|
+
}
|
|
45
|
+
],
|
|
46
|
+
"views": [
|
|
47
|
+
{
|
|
48
|
+
"view_id": "176",
|
|
49
|
+
"view_name": "AgentCapabilities",
|
|
50
|
+
"parent_element_id": "1249",
|
|
51
|
+
"parent_element_name": "Implementation and Migration Viewpoint",
|
|
52
|
+
"included_elements": [],
|
|
53
|
+
"included_relationships": []
|
|
54
|
+
},
|
|
55
|
+
{
|
|
56
|
+
"view_id": "174",
|
|
57
|
+
"view_name": "Implementation and Migration",
|
|
58
|
+
"parent_element_id": "1249",
|
|
59
|
+
"parent_element_name": "Implementation and Migration Viewpoint",
|
|
60
|
+
"included_elements": [],
|
|
61
|
+
"included_relationships": []
|
|
62
|
+
},
|
|
63
|
+
{
|
|
64
|
+
"view_id": "169",
|
|
65
|
+
"view_name": "Application Cooperation",
|
|
66
|
+
"parent_element_id": "1240",
|
|
67
|
+
"parent_element_name": "Application Cooperation Viewpoint",
|
|
68
|
+
"included_elements": [],
|
|
69
|
+
"included_relationships": []
|
|
70
|
+
},
|
|
71
|
+
{
|
|
72
|
+
"view_id": "170",
|
|
73
|
+
"view_name": "SystemArchitecture",
|
|
74
|
+
"included_elements": [
|
|
75
|
+
"1249",
|
|
76
|
+
"1240"
|
|
77
|
+
],
|
|
78
|
+
"included_relationships": [
|
|
79
|
+
"1161"
|
|
80
|
+
]
|
|
81
|
+
}
|
|
82
|
+
]
|
|
207
83
|
}
|
|
@@ -5,9 +5,9 @@ applyTo: "**"
|
|
|
5
5
|
---
|
|
6
6
|
|
|
7
7
|
<Ontology>
|
|
8
|
-
你的认知体系结构是基于Archimate3.2
|
|
9
|
-
1.
|
|
10
|
-
2.
|
|
8
|
+
你的认知体系结构是基于Archimate3.2及其扩展元素构成。以下参考文件位于全局 Argo 安装根目录 ~/.argo（~ 为用户主目录，Windows 上即 %USERPROFILE%\.argo）：
|
|
9
|
+
1. 如果你想知道知识图谱的合法结构，请参考：~/.argo/schema/SystemArchitecture.schema.json
|
|
10
|
+
2. 如果你想查询某类元素或关系的定义，请参考：~/.argo/schema/archimate3.2.md
|
|
11
11
|
</Ontology>
|
|
12
12
|
|
|
13
13
|
<ArmingBeforeImplementation>
|
package/install-argo.ps1
CHANGED
|
@@ -67,11 +67,11 @@ function Add-AgentsRule {
|
|
|
67
67
|
)
|
|
68
68
|
|
|
69
69
|
New-Item -ItemType Directory -Force -Path (Split-Path $AgentsPath) | Out-Null
|
|
70
|
-
$ruleContent = Get-Content $RulePath -Raw
|
|
70
|
+
$ruleContent = Get-Content $RulePath -Raw -Encoding UTF8
|
|
71
71
|
$marker = 'ArchGraph ARGO Workflow Rules'
|
|
72
72
|
|
|
73
73
|
if (Test-Path $AgentsPath) {
|
|
74
|
-
$existing = Get-Content $AgentsPath -Raw
|
|
74
|
+
$existing = Get-Content $AgentsPath -Raw -Encoding UTF8
|
|
75
75
|
if ($existing -like "*$marker*") {
|
|
76
76
|
return
|
|
77
77
|
}
|
package/package.json
CHANGED