Profile contract
archimate.basic@1
Fixed nine-kind business/application/technology vocabulary; family-palette layer colours; viewpoints as named views; serving links upward only. Profile-level coverage, not ArchiMate conformance.
graph projectionLayered enterprise-architecture overview
Open this profile in the gallery
Primary palette
Relationship roles
Legal endpoints
| Relation | Source roles | Target roles | Self relation |
|---|---|---|---|
archi.rel | archi.application_component, archi.application_service, archi.business_actor, archi.business_interface, archi.business_process, archi.business_role, archi.business_service, archi.technology_node, archi.technology_service | archi.application_component, archi.application_service, archi.business_actor, archi.business_interface, archi.business_process, archi.business_role, archi.business_service, archi.technology_node, archi.technology_service | Not allowed |
Profile verification
- Keep the nine implemented business/application/technology roles and their silhouettes.
- Relations obey the implemented fixed three-by-three legal layer-pair table; this is a bounded subset, not the full derivation calculus.
- The fixed legal direction is same-layer or upward serving: technology→application/business, application→business, and each layer→itself. Downward layer pairs reject.
Profile defaults
Explicit file settings override eligible CSS, then these profile defaults and the common standard apply. Unspecified semantic facts remain unspecified.
{
"projection.kind": "graph",
"projection.profile": "archimate.basic@1"
}Projection properties
kind, profile, inputs, analysis_budget, traces, iso, depth
Design operations
- Select layer-specific role; connect relation; verify layer pair and edit label.
Bounded analysis
Structural verification and display only; no execution or implied process engine.
Outside this profile
- ArchiMate exchange format
- relationship derivation machinery
- full ArchiMate conformance