Skip to content

feat(resources): add Grouping, the ArchiMate composite element - #253

Merged
ionos-landgraf-vin merged 1 commit into
mainfrom
feat/grouping-kind
Nov 13, 2026
Merged

ionos-landgraf-vin merged 1 commit into
mainfrom
feat/grouping-kind

Conversation

@ionos-landgraf-vin

Copy link
Copy Markdown
Collaborator

Summary

Adds Grouping (layer other, ArchiMate composite element). A grouping holds resources of every kind, other groupings included, so groups nest:

kind: Grouping
metadata:
  name: Domain:Payments
spec:
  aggregates:
    strategyCapabilities: [Payment Processing]
    groupings: [Domain:Payments:Refunds]
  composedOf:
    applicationComponents: [Payments:API, CardVault:API]
  • aggregates: the member belongs to the group and can be in several groups; composedOf: the member is part of this whole only.
  • Members are listed on the grouping only. No other kind changes; a member's page shows its groups as incoming relations.
  • Kinds load alphabetically, so the relations are declared by Grouping.declare_members! once all kinds are loaded. New kinds are covered automatically.
  • Resources.relation_key gives the spec key of a kind (applicationComponents, goals, technologyEquipment, ...). A test checks it matches the keys the model already uses.
  • The template shows three member kinds instead of ~90 empty lists (Base.template_relations).
  • MCP summary: a grouping lists its members, and members name their groups ("Groups" / "Part of").
  • Lint: a grouping that contains itself through others is reported by the existing hierarchy cycle check.
  • Docs: archimate.md now marks Grouping as supported, modeling.md has a new "Grouping" section, index.md.erb and icons.md list the kind; new example in examples/archsight/groupings/payments.yaml.

Notes

  • For a grouping the editor's relation picker has ~90 options, and the form gets the names of every resource. That's fine for normal models; loading names per kind would be a follow-up if needed.

Test plan

  • bundle exec rake (tests, steep, rubocop)
  • archsight lint -r examples/archsight
  • test/grouping_test.rb: relations to every kind, key names, resolution and nesting, cycle lint, summary, template, API
  • Manual check in the UI: grouping page, member page, editor

🤖 Generated with Claude Code

A Grouping aggregates or composes resources of every kind, groupings
included, so groups nest. Members are listed on the grouping only, one
key per kind under `aggregates` or `composedOf`; members show their
groups as incoming relations.

- Grouping.declare_members! declares both verbs towards every kind once
  all kinds are loaded; Resources.relation_key gives the spec key of a
  kind, matching the keys the model already uses
- template shows a few member kinds instead of ~90 empty lists
  (Base.template_relations)
- summary lens: Grouping lists its members, members name their groups
- linter reports nesting cycles (existing hierarchy cycle check)
- docs (archimate, modeling, index, icons) and a payments example

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@ionos-landgraf-vin
ionos-landgraf-vin merged commit a485bc6 into main Nov 13, 2026
8 checks passed
@ionos-landgraf-vin
ionos-landgraf-vin deleted the feat/grouping-kind branch November 13, 2026 08:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant