{
  "id": "topic:gitops-transparency",
  "_kind": "Topic",
  "_file": "domain/products/krate.yaml",
  "_cluster": "domain",
  "attributes": {
    "displayName": "GitOps Transparency",
    "description": "The principle that every action performed through a graphical UI\nmust have an equivalent kubectl (or API) command, and every state\nmutation must be expressible as a declarative YAML manifest that\ncan be version-controlled in Git. This ensures that platform state\nis auditable, reproducible, and automatable. In Krate, creating a\nrepository via the web UI produces the same Repository CR that\ncould be applied via kubectl; reviewing a pull request sets the\nsame status conditions. The platform eats its own dog food — Krate\nitself is deployed and configured via its own GitOps pipeline.\n"
  },
  "outgoingEdges": [
    {
      "from": "topic:gitops-transparency",
      "to": "domain:devops",
      "kind": "applies_to"
    },
    {
      "from": "topic:gitops-transparency",
      "to": "domain:platform-engineering",
      "kind": "applies_to"
    },
    {
      "from": "topic:gitops-transparency",
      "to": "topic:gitops-principles",
      "kind": "related_to"
    }
  ],
  "incomingEdges": [
    {
      "from": "domain:devops",
      "to": "topic:gitops-transparency",
      "kind": "contains",
      "attributes": {
        "notes": "Every UI action has a kubectl equivalent"
      }
    }
  ]
}