{
  "context": "Tests that the agent traces all three INPUT tags (kube.app.*, kube.payment.*, host.systemd) through FILTER and OUTPUT Match patterns, identifies that kube.payment.* and host.systemd have no matching OUTPUT (causing silent log loss), and that the kube.infra.* OUTPUT has no matching INPUT.",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "kube.payment.* unmatched OUTPUT detected",
      "description": "routing-report.md (or equivalent) identifies that the kube.payment.* INPUT tag has a FILTER but no OUTPUT Match pattern covers it, meaning payment service logs are silently dropped",
      "max_score": 20
    },
    {
      "name": "host.systemd unmatched OUTPUT detected",
      "description": "routing-report.md identifies that the host.systemd INPUT tag has no FILTER or OUTPUT Match pattern, meaning systemd logs are silently dropped",
      "max_score": 15
    },
    {
      "name": "kube.infra.* orphaned OUTPUT detected",
      "description": "routing-report.md identifies that the kube.infra.* OUTPUT Match pattern has no corresponding INPUT that produces matching tags",
      "max_score": 15
    },
    {
      "name": "Real-world consequence explained for each gap",
      "description": "routing-report.md explains the consequence of each routing gap (e.g., payment service logs lost, systemd/kubelet events not forwarded)",
      "max_score": 10
    },
    {
      "name": "Tag flow documented for each INPUT",
      "description": "routing-report.md shows the full tag flow for each INPUT: tag produced -> FILTER(s) matched -> OUTPUT(s) matched",
      "max_score": 10
    },
    {
      "name": "kube.payment.* routing fixed in output",
      "description": "In the corrected fluent-bit.conf, an OUTPUT section with Match kube.payment.* (or a wildcard covering it) is added",
      "max_score": 15
    },
    {
      "name": "host.systemd routing fixed in output",
      "description": "In the corrected fluent-bit.conf, an OUTPUT section with Match host.systemd (or a wildcard covering it) is added",
      "max_score": 10
    },
    {
      "name": "Orphaned OUTPUT remediated or explained",
      "description": "In the corrected fluent-bit.conf, the kube.infra.* OUTPUT is either updated to match a real INPUT tag, given a corresponding INPUT, or removed with an explanation",
      "max_score": 5
    }
  ]
}