# ─────────────────────────────────────────────────────────────────────────────
# ORG ROOT — example-org
#
# This is the top-level holding entity for one organisation. Everything else in
# this folder hangs off it, so "what belongs to this org?" is answered by a
# single directory.
#
# TO CREATE A NEW ORG:
#   1. cp -r content/orgs/example-org content/orgs/acme-corp
#   2. Find/replace `example-org` -> `acme-corp` inside the new folder
#   3. Set ENABLE_BACKSTAGE_ORGS="example-org,acme-corp" in .env
#   4. task backstage:deploy
#
# The Group below is the org's root OWNER. It is deliberately a `type: organization`
# group with no parent, so every team in groups/ can declare it as their parent
# and ownership always resolves upward to a real, current set of people.
#
# ⚠️  `spec.children` must list the team groups, and each child must declare
#     `spec.parent`. Backstage does NOT infer one from the other for Groups.
# ─────────────────────────────────────────────────────────────────────────────
---
apiVersion: backstage.io/v1alpha1
kind: Group
metadata:
  annotations:
    backstage.io/managed-by-location: url:https://static-ai-stack.dc7.io/catalog/example-org/org.yaml
  name: example-org
  title: Example Org
  description: >-
    Root organisation. Copy this folder to stand up a new org with the same
    conventions already wired.
spec:
  type: organization
  profile:
    displayName: Example Org
  children:
    # Every team group in groups/ must appear here AND set spec.parent below.
    - platform-team