{
  "counts": {
    "done": 35,
    "open": 1,
    "partial": 0
  },
  "done_items": [
    {
      "acceptance": "PDF/MD ist als Quelle referenziert und die V1-Produktprinzipien sind in ROADMAP_STATUS sichtbar.",
      "area": "Produktstrategie",
      "gate": "roadmap-contract",
      "id": "v1-enterprise-analysis",
      "next_step": "Analyse in Roadmap, MVP-Scope und Akzeptanzkriterien uebersetzen.",
      "owner": "Product Strategy Agent",
      "priority": "P0",
      "status": "done",
      "title": "Version 1 Enterprise-Analyse aus PDF/MD uebernommen",
      "workstream": "product-revenue"
    },
    {
      "acceptance": "scripts/roadmap-contract-check.py laeuft lokal und in tests/test_roadmap_contract_check.py.",
      "area": "Roadmap Governance",
      "gate": "roadmap-contract",
      "id": "roadmap-contract-foundation",
      "next_step": "Roadmap-Contract in Security-Check und Tests halten.",
      "owner": "Programming Agent",
      "priority": "P0",
      "status": "done",
      "title": "Pruefbarer Roadmap-Vertrag im Repository",
      "workstream": "ops-compliance-runtime"
    },
    {
      "acceptance": "Bestehende Tests fuer Draft-Erzeugung bleiben gruen; neuer No-AI-Creative-Guard folgt als P0.",
      "area": "Planning Engine",
      "gate": "unit-tests",
      "id": "planner-draft-generation",
      "next_step": "Planner als Blueprint Engine statt Content-Generator weiterentwickeln.",
      "owner": "Programming Agent",
      "priority": "P1",
      "status": "done",
      "title": "Bestehender Campaign Planner erzeugt Meta-Entwuerfe",
      "workstream": "planning-blueprints"
    },
    {
      "acceptance": "Policy-Test blockiert Budgets ueber dem konfigurierten Limit.",
      "area": "Policy",
      "gate": "unit-tests",
      "id": "budget-guardrails",
      "next_step": "Budgetlogik um Monatsbudget, Pacing und Budget-Split-Regeln erweitern.",
      "owner": "Compliance Agent",
      "priority": "P0",
      "status": "done",
      "title": "Budget-Guardrails blockieren zu hohe Tagesbudgets",
      "workstream": "planning-blueprints"
    },
    {
      "acceptance": "Riskante Claim-Phrasen werden aktuell blockiert; Erweiterung ist als P0 sichtbar.",
      "area": "Policy",
      "gate": "policy-tests",
      "id": "meta-policy-validation",
      "next_step": "Policy in versionierte Governance mit Housing-Gate und PII-Scan ueberfuehren.",
      "owner": "Compliance Agent",
      "priority": "P0",
      "status": "done",
      "title": "Lokale Meta-Policy-Validation fuer riskante Claims",
      "workstream": "ops-compliance-runtime"
    },
    {
      "acceptance": "MetaAdsClient(dry_run=True) erzeugt nur Preview; Live-Adapter ist nicht implementiert.",
      "area": "Meta API",
      "gate": "human-approval",
      "id": "dry-run-publishing",
      "next_step": "Dry-run-Verhalten bei jedem spaeteren API-Ausbau als Default erzwingen.",
      "owner": "Meta API Agent",
      "priority": "P0",
      "status": "done",
      "title": "Meta Client bleibt dry-run-first und blockiert Live-Writes",
      "workstream": "ops-compliance-runtime"
    },
    {
      "acceptance": "README, Roadmap und UX-Dokumente nennen Demand OS, Premium Ads Control Room, menschliche Creatives und Data Trust als Kern.",
      "area": "Produktstrategie",
      "gate": "product-review",
      "id": "colbec-product-framing",
      "next_step": "Produktnarrativ in spaeteren UI- und Report-Oberflaechen konsequent halten.",
      "owner": "Product Strategy Agent",
      "priority": "P0",
      "status": "done",
      "title": "Produktnarrativ auf Colbec Demand OS umstellen",
      "workstream": "product-revenue"
    },
    {
      "acceptance": "docs/PILOT_OFFER.md wird aus PilotOfferPackage V1 generiert und enthaelt Zielkunde, Scope, Preisanker, Zahlungslogik, Nicht-Ziele, No-AI-Creative und Real-Data-Gates.",
      "area": "Revenue",
      "gate": "pilot-offer-review",
      "id": "pilot-offer-packaging",
      "next_step": "Pilot-Angebot in Sales-Prozess, dev-meta und spaetere Angebots-PDFs einbetten.",
      "owner": "Product Strategy Agent",
      "priority": "P0",
      "status": "done",
      "title": "Paid Audit und 90-Day Premium Demand Pilot paketieren",
      "workstream": "product-revenue"
    },
    {
      "acceptance": "docs/SALES_DEMO_KIT.md wird aus SalesDemoKit V1 generiert und fuehrt dev-meta, Boardroom, Decision Dashboard, Lead Quality, Grenzen, Talk Track und Paid-Audit-Abschluss zusammen.",
      "area": "Revenue",
      "gate": "pilot-offer-review",
      "id": "sales-demo-kit",
      "next_step": "Demo Kit in Kundengespraechen validieren und Einwandbehandlung ausbauen.",
      "owner": "Product Strategy Agent",
      "priority": "P1",
      "status": "done",
      "title": "Sales Demo Kit mit dev-meta, Boardroom und Decision Dashboard",
      "workstream": "product-revenue"
    },
    {
      "acceptance": "Planner erzeugt keine Headline/Primary-Text-Vorschlaege mehr; Tests pruefen menschliche Creative-Slots.",
      "area": "Creative Governance",
      "gate": "creative-approval",
      "id": "no-ai-creative-guardrail",
      "next_step": "Manuelle Creative-Slots in spaeteren Blueprints und Reports als feste Produktregel halten.",
      "owner": "Compliance Agent",
      "priority": "P0",
      "status": "done",
      "title": "Keine Tool-Copy und keine KI-Creatives im Enterprise-MVP",
      "workstream": "planning-blueprints"
    },
    {
      "acceptance": "Vier versionierte Blueprint-Registry-Eintraege sind testbar, budgetplausibel, Real-Estate-aware und ohne KI-Copy.",
      "area": "Planning Engine",
      "gate": "blueprint-review",
      "id": "blueprint-library-v1",
      "next_step": "Blueprints spaeter in Planner-UI und Kundenbriefing-Ausgabe anzeigen.",
      "owner": "Programming Agent",
      "priority": "P1",
      "status": "done",
      "title": "Hospitality- und Real-Estate-Blueprint Library V1",
      "workstream": "planning-blueprints"
    },
    {
      "acceptance": "ApprovalRequest, AuditEvent und Publishing Policy erzwingen explizite Freigabe fuer Live-Writes.",
      "area": "Governance",
      "gate": "human-approval",
      "id": "human-approval-gate",
      "next_step": "Approval-Events spaeter persistent speichern und in UI/Stage-Gate anzeigen.",
      "owner": "Compliance Agent",
      "priority": "P0",
      "status": "done",
      "title": "Human Approval Gate fuer Publishing und Budgetaenderungen",
      "workstream": "ops-compliance-runtime"
    },
    {
      "acceptance": "docs/DOKPLOY_DEPLOYMENT.md und ops/dokploy Beispiele beschreiben dev-meta synthetic-only, stage-meta guarded und konkrete Compose-Pfade.",
      "area": "Deployment",
      "gate": "dokploy-readiness",
      "id": "dokploy-dev-stage-plan",
      "next_step": "Runtime Compose, Healthchecks und Smoke-Gates im Roadmap-Vertrag halten.",
      "owner": "DevOps Agent",
      "priority": "P0",
      "status": "done",
      "title": "Dokploy-Plan fuer dev-meta und stage-meta dokumentieren",
      "workstream": "ops-compliance-runtime"
    },
    {
      "acceptance": "docs/COLBEC_UX_DIRECTION.md und roadmap-dashboard.html beschreiben Tonalitaet, Layoutprinzipien und No-Growth-Hype-Regeln.",
      "area": "UX",
      "gate": "ux-review",
      "id": "colbec-ux-direction",
      "next_step": "Designsystem und erste Dashboard-Wireframes in die spaetere Web-App ueberfuehren.",
      "owner": "UX Agent",
      "priority": "P1",
      "status": "done",
      "title": "Colbec UX Richtung fuer Control Room und Reports festlegen",
      "workstream": "ux-boardroom"
    },
    {
      "acceptance": "Tenant-ID ist in Client, Brand und AdAccount Pflicht; Tests pruefen Isolation und Cross-Tenant-Blocker.",
      "area": "Data Model",
      "gate": "data-model-review",
      "id": "tenant-domain-model",
      "next_step": "Persistenzschicht spaeter auf Postgres/Dokploy uebertragen.",
      "owner": "Data Platform Agent",
      "priority": "P0",
      "status": "done",
      "title": "Tenant-, Client-, Brand- und Ad-Account-Domainmodell",
      "workstream": "data-trust-integrations"
    },
    {
      "acceptance": "Import prueft Pflichtfelder, Zahlenformate, Duplikate, PII, Spend/Impression-Plausibilitaet und gibt Quality Score aus.",
      "area": "Data Trust",
      "gate": "import-quality",
      "id": "data-trust-import-pipeline",
      "next_step": "XLSX und Report-Snapshot-Persistenz spaeter ergaenzen; CSV-Kern ist vorhanden.",
      "owner": "Data Platform Agent",
      "priority": "P0",
      "status": "done",
      "title": "CSV/XLSX Import Pipeline mit Mapping und Quality Score",
      "workstream": "data-trust-integrations"
    },
    {
      "acceptance": "RealCustomerDataContext blockiert echte Daten ohne DPA/AVV, Zweck, Datenklasse, Retention, Zugriff, Backup, Secrets und Human Approval.",
      "area": "Data Trust",
      "gate": "real-data-approval",
      "id": "real-customer-data-gate",
      "next_step": "Gate in spaeteren CLI/UI-Upload-Pfaden verpflichtend verdrahten.",
      "owner": "Data Platform Agent",
      "priority": "P0",
      "status": "done",
      "title": "Real Customer Data Gate vor echten Kundendaten",
      "workstream": "data-trust-integrations"
    },
    {
      "acceptance": "ImportManifest V1 kann append-only ohne Rohdaten gespeichert, im ReportSnapshot verlinkt und im Boardroom Contract sichtbar gemacht werden.",
      "area": "Data Trust",
      "gate": "data-lineage-review",
      "id": "import-history-persistence",
      "next_step": "Append-only JSONL spaeter auf Postgres oder privates Volume mit Locking migrieren.",
      "owner": "Data Platform Agent",
      "priority": "P0",
      "status": "done",
      "title": "Import-Historie und ReportSnapshot-Persistenz",
      "workstream": "data-trust-integrations"
    },
    {
      "acceptance": "Reconciliation-Gate blockiert CPQL/Revenue-Ausgabe bei zu kleiner Aggregation, Perioden- oder Waehrungs-Mismatch.",
      "area": "Data Trust",
      "gate": "data-reconciliation",
      "id": "minimum-aggregation-reconciliation",
      "next_step": "Channel-Taxonomie spaeter kundenkonfigurierbar machen.",
      "owner": "Data Platform Agent",
      "priority": "P0",
      "status": "done",
      "title": "Mindestaggregation, Perioden- und Channel-Abgleich",
      "workstream": "data-trust-integrations"
    },
    {
      "acceptance": "KPI-Formeln fuer Spend, CPM, CTR, CPC, LPV, CVR, CPA/CPL und Frequency sind zentral versioniert und getestet.",
      "area": "Reporting",
      "gate": "kpi-tests",
      "id": "semantic-kpi-layer",
      "next_step": "Pacing und Source-Separation in Report-Snapshots erweitern.",
      "owner": "Data Platform Agent",
      "priority": "P0",
      "status": "done",
      "title": "Semantischer KPI-Layer fuer Meta-, Site- und CRM-Daten",
      "workstream": "reporting-intelligence"
    },
    {
      "acceptance": "Decision Dashboard, Boardroom HTML/Markdown und JSON koennen DecisionItemV1 mit Owner, Due Date, Impact, Risiko, Status und Evidence sichtbar ausgeben.",
      "area": "Reporting",
      "gate": "decision-intelligence-review",
      "id": "pacing-decision-intelligence",
      "next_step": "Segment-Rollups erst mit Taxonomie, Mindestvolumen und echten Zielwerten ergaenzen.",
      "owner": "Data Platform Agent",
      "priority": "P1",
      "status": "done",
      "title": "Pacing Engine und Decision Intelligence Layer",
      "workstream": "reporting-intelligence"
    },
    {
      "acceptance": "Boardroom PDF wird als echter PDF-Binary ueber CLI und /boardroom-report.pdf erzeugt, enthaelt Contract-Version, Snapshot-ID, KPI-Version, Draft/Ready-Status, Source Separation und Decision Intelligence.",
      "area": "Client Deliverables",
      "gate": "report-review",
      "id": "boardroom-pdf-export",
      "next_step": "PDF-Layout spaeter mit Typografie, Pagination und signiertem Exportpfad veredeln.",
      "owner": "UX Agent",
      "priority": "P0",
      "status": "done",
      "title": "Premium Boardroom PDF fuer Monatsentscheidungen",
      "workstream": "ux-boardroom"
    },
    {
      "acceptance": "BoardroomReportV1 definiert Contract-Version, Snapshot-ID, Pflichtsektionen, KPI-Version, Source-Status, Approval-Status, Compliance Note und Exportstatus.",
      "area": "Client Deliverables",
      "gate": "report-review",
      "id": "boardroom-report-contract-v1",
      "next_step": "Contract-Banner und Draft/Ready-Status im Boardroom-HTML sichtbar machen.",
      "owner": "UX Agent",
      "priority": "P0",
      "status": "done",
      "title": "Boardroom Report Contract V1 mit Pflichtsektionen",
      "workstream": "ux-boardroom"
    },
    {
      "acceptance": "CLI und Web-Preview zeigen Readiness, Data Quality, Source Notes, Entscheidungs-Lanes und naechste Massnahmen aus ReportSnapshot.",
      "area": "UX",
      "gate": "ux-review",
      "id": "decision-dashboard",
      "next_step": "Dashboard spaeter um Pacing, Verantwortliche, Faelligkeiten und persistente Decision Logs erweitern.",
      "owner": "UX Agent",
      "priority": "P1",
      "status": "done",
      "title": "Decision Dashboard statt Vanity-Metric-Dashboard",
      "workstream": "ux-boardroom"
    },
    {
      "acceptance": "Riskante Targeting-Felder und enge Geo-Radien werden fuer Housing blockiert oder hart gewarnt.",
      "area": "Compliance",
      "gate": "compliance-review",
      "id": "housing-compliance-gate",
      "next_step": "Audit-Event-Persistenz und Policy-Versionierung spaeter ergaenzen.",
      "owner": "Compliance Agent",
      "priority": "P0",
      "status": "done",
      "title": "Housing-/Real-Estate-Compliance-Gate",
      "workstream": "ops-compliance-runtime"
    },
    {
      "acceptance": "MVP blockiert E-Mail, Telefon, IP, Lead IDs, Name-/Adress-Header und erlaubt nur aggregierte Reporting-Exports.",
      "area": "Privacy",
      "gate": "privacy-review",
      "id": "pii-upload-scanner",
      "next_step": "Scanner bei XLSX und spaeteren UI-Uploads wiederverwenden.",
      "owner": "Security Agent",
      "priority": "P0",
      "status": "done",
      "title": "PII Upload Scanner fuer Meta-Exports und spaetere Lead-Dateien",
      "workstream": "data-trust-integrations"
    },
    {
      "acceptance": "Aggregat-CSV fuer qualifizierte Leads, Termine, Buchungen und Umsatz wird PII-geprueft, blockiert Rohdaten und speist CPQL/Booking Quality in Report und Dashboard.",
      "area": "Revenue Intelligence",
      "gate": "privacy-review",
      "id": "lead-booking-quality-import",
      "next_step": "Periodenabgleich, Channel-Mapping und Mindestaggregation vor echten Kundendaten ergaenzen.",
      "owner": "Data Platform Agent",
      "priority": "P2",
      "status": "done",
      "title": "Lead-/Booking-Qualitaetsimport fuer CPQL und Booking Intent",
      "workstream": "reporting-intelligence"
    },
    {
      "acceptance": "Benchmark Vault V1 startet im Reference Mode, erzwingt Mindestkohorte fuer Network Mode, blockiert Identifier/PII-Risiken und zeigt extern nur aggregierte Vergleichswerte ohne interne Notizen.",
      "area": "Moat",
      "gate": "benchmark-governance",
      "id": "benchmark-vault",
      "next_step": "Observed Network Mode erst nach Mandanten-Consent, Auth, DPA, Mindestkohorte und Contributor-Dominance-Gate aktivieren.",
      "owner": "Product Strategy Agent",
      "priority": "P2",
      "status": "done",
      "title": "Benchmark Vault fuer Hospitality und Real Estate",
      "workstream": "product-revenue"
    },
    {
      "acceptance": "/pilot-offer rendert eine browserfaehige Kaeuferseite; /pilot-offer.md bleibt als Markdown-Artefakt erhalten.",
      "area": "Revenue",
      "gate": "pilot-offer-review",
      "id": "pilot-offer-html-page",
      "next_step": "Pilot Offer spaeter um Angebots-PDF und CRM-CTA erweitern.",
      "owner": "Product Strategy Agent",
      "priority": "P0",
      "status": "done",
      "title": "Buyer-ready Pilot Offer HTML fuer Sales-Gespraeche",
      "workstream": "product-revenue"
    },
    {
      "acceptance": "/status-board und /status-board.json zeigen sechs Workstreams, Zaehler und Meta-Write-Lock ohne Owner, Gates, Abnahme oder Next-Step-Details.",
      "area": "UX",
      "gate": "ux-review",
      "id": "public-status-board",
      "next_step": "Status Board spaeter als client-safe Demo-Einstieg fuer Sales Calls nutzen.",
      "owner": "UX Agent",
      "priority": "P0",
      "status": "done",
      "title": "Public Status Board ohne interne Roadmap-Details",
      "workstream": "ux-boardroom"
    },
    {
      "acceptance": "dev-meta ist live erreichbar, nutzt keine echten Kundendaten, zeigt die Roadmap und Meta-Writes sind false.",
      "area": "Deployment",
      "gate": "dev-meta-smoke",
      "id": "dokploy-dev-meta-deploy",
      "next_step": "dev-meta nach jedem main-Deploy mit Runtime Doctor und Public Smoke pruefen.",
      "owner": "DevOps Agent",
      "priority": "P1",
      "status": "done",
      "title": "dev-meta Dokploy Runtime mit synthetischen Daten",
      "workstream": "ops-compliance-runtime"
    },
    {
      "acceptance": "GitHub-App sieht rb007x75/meta-ads; lokales git remote -v zeigt origin; Dokploy General/GitHub kann main auswaehlen.",
      "area": "Deployment",
      "gate": "dokploy-readiness",
      "id": "github-repo-dokploy-link",
      "next_step": "main pushen und Dokploy-Provider auf docker-compose.yml ausrichten.",
      "owner": "DevOps Agent",
      "priority": "P0",
      "status": "done",
      "title": "GitHub Repo fuer Dokploy sichtbar machen",
      "workstream": "ops-compliance-runtime"
    },
    {
      "acceptance": "scripts/stage-meta-release-gate.sh prueft Roadmap, generierte Artefakte, Stage Compose, Runtime Doctor und optional Public Smoke samt /readyz Safety JSON.",
      "area": "Deployment",
      "gate": "stage-promotion",
      "id": "stage-meta-gate",
      "next_step": "Stage-Public-Smoke nach erstem stage-meta Deploy mit STAGE_PUBLIC_URL regelmaessig ausfuehren.",
      "owner": "DevOps Agent",
      "priority": "P1",
      "status": "done",
      "title": "stage-meta Gate fuer pilotfaehige Demo",
      "workstream": "ops-compliance-runtime"
    },
    {
      "acceptance": "INTERNAL_ROADMAP_TOKEN schuetzt Roadmap, Audit- und Workstream-JSON-Routen; stage-meta /readyz bleibt ohne aktiven Schutz rot.",
      "area": "Security",
      "gate": "dokploy-stage",
      "id": "internal-roadmap-protection",
      "next_step": "Dokploy-Token fuer stage-meta vor erster Kundendemo setzen und Browser-Auth-Option bewerten.",
      "owner": "Security Agent",
      "priority": "P0",
      "status": "done",
      "title": "Interne Roadmap-Routen optional schuetzen",
      "workstream": "ops-compliance-runtime"
    },
    {
      "acceptance": "scripts/dev-meta-postdeploy-gate.sh prueft Roadmap, Generatoren, Compose, Runtime Doctor, Public Smoke, /readyz und public status JSON.",
      "area": "Deployment",
      "gate": "dev-meta-smoke",
      "id": "dev-meta-postdeploy-gate",
      "next_step": "Gate nach jedem Dokploy-Deploy ausfuehren und spaeter als GitHub Actions Workflow automatisieren.",
      "owner": "DevOps Agent",
      "priority": "P1",
      "status": "done",
      "title": "dev-meta Postdeploy Gate fuer dauerhafte Pruefbarkeit",
      "workstream": "ops-compliance-runtime"
    }
  ],
  "meta_write_lock_visible": true,
  "open_items": [
    {
      "acceptance": "Keine Kampagne, kein Budget, keine Audience und kein Pixel wird ohne explizites Gate geaendert.",
      "area": "Meta API",
      "gate": "meta-write-lock",
      "id": "live-meta-api-writes",
      "next_step": "Erst nach Data Trust, Approval, Audit, Stage und Kundenfreigabe erneut bewerten.",
      "owner": "Meta API Agent",
      "priority": "P3",
      "status": "open",
      "title": "Live Meta API Writes bleiben bewusst offen/deferred",
      "workstream": "ops-compliance-runtime"
    }
  ],
  "progress_percent": 97,
  "service": "colbec-demand-os",
  "title": "Colbec Demand OS Workstream Cockpit",
  "workstreams": [
    {
      "counts": {
        "done": 6,
        "open": 0,
        "partial": 0
      },
      "done": [
        {
          "acceptance": "PDF/MD ist als Quelle referenziert und die V1-Produktprinzipien sind in ROADMAP_STATUS sichtbar.",
          "area": "Produktstrategie",
          "gate": "roadmap-contract",
          "id": "v1-enterprise-analysis",
          "next_step": "Analyse in Roadmap, MVP-Scope und Akzeptanzkriterien uebersetzen.",
          "owner": "Product Strategy Agent",
          "priority": "P0",
          "status": "done",
          "title": "Version 1 Enterprise-Analyse aus PDF/MD uebernommen",
          "workstream": "product-revenue"
        },
        {
          "acceptance": "README, Roadmap und UX-Dokumente nennen Demand OS, Premium Ads Control Room, menschliche Creatives und Data Trust als Kern.",
          "area": "Produktstrategie",
          "gate": "product-review",
          "id": "colbec-product-framing",
          "next_step": "Produktnarrativ in spaeteren UI- und Report-Oberflaechen konsequent halten.",
          "owner": "Product Strategy Agent",
          "priority": "P0",
          "status": "done",
          "title": "Produktnarrativ auf Colbec Demand OS umstellen",
          "workstream": "product-revenue"
        },
        {
          "acceptance": "docs/PILOT_OFFER.md wird aus PilotOfferPackage V1 generiert und enthaelt Zielkunde, Scope, Preisanker, Zahlungslogik, Nicht-Ziele, No-AI-Creative und Real-Data-Gates.",
          "area": "Revenue",
          "gate": "pilot-offer-review",
          "id": "pilot-offer-packaging",
          "next_step": "Pilot-Angebot in Sales-Prozess, dev-meta und spaetere Angebots-PDFs einbetten.",
          "owner": "Product Strategy Agent",
          "priority": "P0",
          "status": "done",
          "title": "Paid Audit und 90-Day Premium Demand Pilot paketieren",
          "workstream": "product-revenue"
        },
        {
          "acceptance": "docs/SALES_DEMO_KIT.md wird aus SalesDemoKit V1 generiert und fuehrt dev-meta, Boardroom, Decision Dashboard, Lead Quality, Grenzen, Talk Track und Paid-Audit-Abschluss zusammen.",
          "area": "Revenue",
          "gate": "pilot-offer-review",
          "id": "sales-demo-kit",
          "next_step": "Demo Kit in Kundengespraechen validieren und Einwandbehandlung ausbauen.",
          "owner": "Product Strategy Agent",
          "priority": "P1",
          "status": "done",
          "title": "Sales Demo Kit mit dev-meta, Boardroom und Decision Dashboard",
          "workstream": "product-revenue"
        },
        {
          "acceptance": "Benchmark Vault V1 startet im Reference Mode, erzwingt Mindestkohorte fuer Network Mode, blockiert Identifier/PII-Risiken und zeigt extern nur aggregierte Vergleichswerte ohne interne Notizen.",
          "area": "Moat",
          "gate": "benchmark-governance",
          "id": "benchmark-vault",
          "next_step": "Observed Network Mode erst nach Mandanten-Consent, Auth, DPA, Mindestkohorte und Contributor-Dominance-Gate aktivieren.",
          "owner": "Product Strategy Agent",
          "priority": "P2",
          "status": "done",
          "title": "Benchmark Vault fuer Hospitality und Real Estate",
          "workstream": "product-revenue"
        },
        {
          "acceptance": "/pilot-offer rendert eine browserfaehige Kaeuferseite; /pilot-offer.md bleibt als Markdown-Artefakt erhalten.",
          "area": "Revenue",
          "gate": "pilot-offer-review",
          "id": "pilot-offer-html-page",
          "next_step": "Pilot Offer spaeter um Angebots-PDF und CRM-CTA erweitern.",
          "owner": "Product Strategy Agent",
          "priority": "P0",
          "status": "done",
          "title": "Buyer-ready Pilot Offer HTML fuer Sales-Gespraeche",
          "workstream": "product-revenue"
        }
      ],
      "focus": "Paid Audit, Pilot-Angebot, Packaging, Positionierung und Benchmark-Moat fuer zahlbare Retainer.",
      "id": "product-revenue",
      "open": [],
      "partial": [],
      "title": "Liste 1: Produkt und Revenue"
    },
    {
      "counts": {
        "done": 5,
        "open": 0,
        "partial": 0
      },
      "done": [
        {
          "acceptance": "docs/COLBEC_UX_DIRECTION.md und roadmap-dashboard.html beschreiben Tonalitaet, Layoutprinzipien und No-Growth-Hype-Regeln.",
          "area": "UX",
          "gate": "ux-review",
          "id": "colbec-ux-direction",
          "next_step": "Designsystem und erste Dashboard-Wireframes in die spaetere Web-App ueberfuehren.",
          "owner": "UX Agent",
          "priority": "P1",
          "status": "done",
          "title": "Colbec UX Richtung fuer Control Room und Reports festlegen",
          "workstream": "ux-boardroom"
        },
        {
          "acceptance": "CLI und Web-Preview zeigen Readiness, Data Quality, Source Notes, Entscheidungs-Lanes und naechste Massnahmen aus ReportSnapshot.",
          "area": "UX",
          "gate": "ux-review",
          "id": "decision-dashboard",
          "next_step": "Dashboard spaeter um Pacing, Verantwortliche, Faelligkeiten und persistente Decision Logs erweitern.",
          "owner": "UX Agent",
          "priority": "P1",
          "status": "done",
          "title": "Decision Dashboard statt Vanity-Metric-Dashboard",
          "workstream": "ux-boardroom"
        },
        {
          "acceptance": "Boardroom PDF wird als echter PDF-Binary ueber CLI und /boardroom-report.pdf erzeugt, enthaelt Contract-Version, Snapshot-ID, KPI-Version, Draft/Ready-Status, Source Separation und Decision Intelligence.",
          "area": "Client Deliverables",
          "gate": "report-review",
          "id": "boardroom-pdf-export",
          "next_step": "PDF-Layout spaeter mit Typografie, Pagination und signiertem Exportpfad veredeln.",
          "owner": "UX Agent",
          "priority": "P0",
          "status": "done",
          "title": "Premium Boardroom PDF fuer Monatsentscheidungen",
          "workstream": "ux-boardroom"
        },
        {
          "acceptance": "BoardroomReportV1 definiert Contract-Version, Snapshot-ID, Pflichtsektionen, KPI-Version, Source-Status, Approval-Status, Compliance Note und Exportstatus.",
          "area": "Client Deliverables",
          "gate": "report-review",
          "id": "boardroom-report-contract-v1",
          "next_step": "Contract-Banner und Draft/Ready-Status im Boardroom-HTML sichtbar machen.",
          "owner": "UX Agent",
          "priority": "P0",
          "status": "done",
          "title": "Boardroom Report Contract V1 mit Pflichtsektionen",
          "workstream": "ux-boardroom"
        },
        {
          "acceptance": "/status-board und /status-board.json zeigen sechs Workstreams, Zaehler und Meta-Write-Lock ohne Owner, Gates, Abnahme oder Next-Step-Details.",
          "area": "UX",
          "gate": "ux-review",
          "id": "public-status-board",
          "next_step": "Status Board spaeter als client-safe Demo-Einstieg fuer Sales Calls nutzen.",
          "owner": "UX Agent",
          "priority": "P0",
          "status": "done",
          "title": "Public Status Board ohne interne Roadmap-Details",
          "workstream": "ux-boardroom"
        }
      ],
      "focus": "Premium Control Room, Decision Dashboard, Boardroom-HTML/PDF und Colbec-Designqualitaet.",
      "id": "ux-boardroom",
      "open": [],
      "partial": [],
      "title": "Liste 2: UX und Boardroom"
    },
    {
      "counts": {
        "done": 4,
        "open": 0,
        "partial": 0
      },
      "done": [
        {
          "acceptance": "Bestehende Tests fuer Draft-Erzeugung bleiben gruen; neuer No-AI-Creative-Guard folgt als P0.",
          "area": "Planning Engine",
          "gate": "unit-tests",
          "id": "planner-draft-generation",
          "next_step": "Planner als Blueprint Engine statt Content-Generator weiterentwickeln.",
          "owner": "Programming Agent",
          "priority": "P1",
          "status": "done",
          "title": "Bestehender Campaign Planner erzeugt Meta-Entwuerfe",
          "workstream": "planning-blueprints"
        },
        {
          "acceptance": "Policy-Test blockiert Budgets ueber dem konfigurierten Limit.",
          "area": "Policy",
          "gate": "unit-tests",
          "id": "budget-guardrails",
          "next_step": "Budgetlogik um Monatsbudget, Pacing und Budget-Split-Regeln erweitern.",
          "owner": "Compliance Agent",
          "priority": "P0",
          "status": "done",
          "title": "Budget-Guardrails blockieren zu hohe Tagesbudgets",
          "workstream": "planning-blueprints"
        },
        {
          "acceptance": "Planner erzeugt keine Headline/Primary-Text-Vorschlaege mehr; Tests pruefen menschliche Creative-Slots.",
          "area": "Creative Governance",
          "gate": "creative-approval",
          "id": "no-ai-creative-guardrail",
          "next_step": "Manuelle Creative-Slots in spaeteren Blueprints und Reports als feste Produktregel halten.",
          "owner": "Compliance Agent",
          "priority": "P0",
          "status": "done",
          "title": "Keine Tool-Copy und keine KI-Creatives im Enterprise-MVP",
          "workstream": "planning-blueprints"
        },
        {
          "acceptance": "Vier versionierte Blueprint-Registry-Eintraege sind testbar, budgetplausibel, Real-Estate-aware und ohne KI-Copy.",
          "area": "Planning Engine",
          "gate": "blueprint-review",
          "id": "blueprint-library-v1",
          "next_step": "Blueprints spaeter in Planner-UI und Kundenbriefing-Ausgabe anzeigen.",
          "owner": "Programming Agent",
          "priority": "P1",
          "status": "done",
          "title": "Hospitality- und Real-Estate-Blueprint Library V1",
          "workstream": "planning-blueprints"
        }
      ],
      "focus": "Zielgruppen-, Kampagnen- und Budget-Blueprints ohne KI-Copy oder generierte Creatives.",
      "id": "planning-blueprints",
      "open": [],
      "partial": [],
      "title": "Liste 3: Planning und Blueprint Engine"
    },
    {
      "counts": {
        "done": 6,
        "open": 0,
        "partial": 0
      },
      "done": [
        {
          "acceptance": "Tenant-ID ist in Client, Brand und AdAccount Pflicht; Tests pruefen Isolation und Cross-Tenant-Blocker.",
          "area": "Data Model",
          "gate": "data-model-review",
          "id": "tenant-domain-model",
          "next_step": "Persistenzschicht spaeter auf Postgres/Dokploy uebertragen.",
          "owner": "Data Platform Agent",
          "priority": "P0",
          "status": "done",
          "title": "Tenant-, Client-, Brand- und Ad-Account-Domainmodell",
          "workstream": "data-trust-integrations"
        },
        {
          "acceptance": "Import prueft Pflichtfelder, Zahlenformate, Duplikate, PII, Spend/Impression-Plausibilitaet und gibt Quality Score aus.",
          "area": "Data Trust",
          "gate": "import-quality",
          "id": "data-trust-import-pipeline",
          "next_step": "XLSX und Report-Snapshot-Persistenz spaeter ergaenzen; CSV-Kern ist vorhanden.",
          "owner": "Data Platform Agent",
          "priority": "P0",
          "status": "done",
          "title": "CSV/XLSX Import Pipeline mit Mapping und Quality Score",
          "workstream": "data-trust-integrations"
        },
        {
          "acceptance": "RealCustomerDataContext blockiert echte Daten ohne DPA/AVV, Zweck, Datenklasse, Retention, Zugriff, Backup, Secrets und Human Approval.",
          "area": "Data Trust",
          "gate": "real-data-approval",
          "id": "real-customer-data-gate",
          "next_step": "Gate in spaeteren CLI/UI-Upload-Pfaden verpflichtend verdrahten.",
          "owner": "Data Platform Agent",
          "priority": "P0",
          "status": "done",
          "title": "Real Customer Data Gate vor echten Kundendaten",
          "workstream": "data-trust-integrations"
        },
        {
          "acceptance": "ImportManifest V1 kann append-only ohne Rohdaten gespeichert, im ReportSnapshot verlinkt und im Boardroom Contract sichtbar gemacht werden.",
          "area": "Data Trust",
          "gate": "data-lineage-review",
          "id": "import-history-persistence",
          "next_step": "Append-only JSONL spaeter auf Postgres oder privates Volume mit Locking migrieren.",
          "owner": "Data Platform Agent",
          "priority": "P0",
          "status": "done",
          "title": "Import-Historie und ReportSnapshot-Persistenz",
          "workstream": "data-trust-integrations"
        },
        {
          "acceptance": "Reconciliation-Gate blockiert CPQL/Revenue-Ausgabe bei zu kleiner Aggregation, Perioden- oder Waehrungs-Mismatch.",
          "area": "Data Trust",
          "gate": "data-reconciliation",
          "id": "minimum-aggregation-reconciliation",
          "next_step": "Channel-Taxonomie spaeter kundenkonfigurierbar machen.",
          "owner": "Data Platform Agent",
          "priority": "P0",
          "status": "done",
          "title": "Mindestaggregation, Perioden- und Channel-Abgleich",
          "workstream": "data-trust-integrations"
        },
        {
          "acceptance": "MVP blockiert E-Mail, Telefon, IP, Lead IDs, Name-/Adress-Header und erlaubt nur aggregierte Reporting-Exports.",
          "area": "Privacy",
          "gate": "privacy-review",
          "id": "pii-upload-scanner",
          "next_step": "Scanner bei XLSX und spaeteren UI-Uploads wiederverwenden.",
          "owner": "Security Agent",
          "priority": "P0",
          "status": "done",
          "title": "PII Upload Scanner fuer Meta-Exports und spaetere Lead-Dateien",
          "workstream": "data-trust-integrations"
        }
      ],
      "focus": "Mandantenmodell, sichere Uploads, Importqualitaet, PII-Blocker und spaetere XLSX/CRM-Anbindung.",
      "id": "data-trust-integrations",
      "open": [],
      "partial": [],
      "title": "Liste 4: Data Trust und Integrationen"
    },
    {
      "counts": {
        "done": 3,
        "open": 0,
        "partial": 0
      },
      "done": [
        {
          "acceptance": "KPI-Formeln fuer Spend, CPM, CTR, CPC, LPV, CVR, CPA/CPL und Frequency sind zentral versioniert und getestet.",
          "area": "Reporting",
          "gate": "kpi-tests",
          "id": "semantic-kpi-layer",
          "next_step": "Pacing und Source-Separation in Report-Snapshots erweitern.",
          "owner": "Data Platform Agent",
          "priority": "P0",
          "status": "done",
          "title": "Semantischer KPI-Layer fuer Meta-, Site- und CRM-Daten",
          "workstream": "reporting-intelligence"
        },
        {
          "acceptance": "Decision Dashboard, Boardroom HTML/Markdown und JSON koennen DecisionItemV1 mit Owner, Due Date, Impact, Risiko, Status und Evidence sichtbar ausgeben.",
          "area": "Reporting",
          "gate": "decision-intelligence-review",
          "id": "pacing-decision-intelligence",
          "next_step": "Segment-Rollups erst mit Taxonomie, Mindestvolumen und echten Zielwerten ergaenzen.",
          "owner": "Data Platform Agent",
          "priority": "P1",
          "status": "done",
          "title": "Pacing Engine und Decision Intelligence Layer",
          "workstream": "reporting-intelligence"
        },
        {
          "acceptance": "Aggregat-CSV fuer qualifizierte Leads, Termine, Buchungen und Umsatz wird PII-geprueft, blockiert Rohdaten und speist CPQL/Booking Quality in Report und Dashboard.",
          "area": "Revenue Intelligence",
          "gate": "privacy-review",
          "id": "lead-booking-quality-import",
          "next_step": "Periodenabgleich, Channel-Mapping und Mindestaggregation vor echten Kundendaten ergaenzen.",
          "owner": "Data Platform Agent",
          "priority": "P2",
          "status": "done",
          "title": "Lead-/Booking-Qualitaetsimport fuer CPQL und Booking Intent",
          "workstream": "reporting-intelligence"
        }
      ],
      "focus": "Semantische KPIs, Lead-/Booking-Qualitaet, CPQL, Booking Intent und entscheidungsfaehige Reports.",
      "id": "reporting-intelligence",
      "open": [],
      "partial": [],
      "title": "Liste 5: Reporting und Intelligence"
    },
    {
      "counts": {
        "done": 11,
        "open": 1,
        "partial": 0
      },
      "done": [
        {
          "acceptance": "scripts/roadmap-contract-check.py laeuft lokal und in tests/test_roadmap_contract_check.py.",
          "area": "Roadmap Governance",
          "gate": "roadmap-contract",
          "id": "roadmap-contract-foundation",
          "next_step": "Roadmap-Contract in Security-Check und Tests halten.",
          "owner": "Programming Agent",
          "priority": "P0",
          "status": "done",
          "title": "Pruefbarer Roadmap-Vertrag im Repository",
          "workstream": "ops-compliance-runtime"
        },
        {
          "acceptance": "Riskante Claim-Phrasen werden aktuell blockiert; Erweiterung ist als P0 sichtbar.",
          "area": "Policy",
          "gate": "policy-tests",
          "id": "meta-policy-validation",
          "next_step": "Policy in versionierte Governance mit Housing-Gate und PII-Scan ueberfuehren.",
          "owner": "Compliance Agent",
          "priority": "P0",
          "status": "done",
          "title": "Lokale Meta-Policy-Validation fuer riskante Claims",
          "workstream": "ops-compliance-runtime"
        },
        {
          "acceptance": "MetaAdsClient(dry_run=True) erzeugt nur Preview; Live-Adapter ist nicht implementiert.",
          "area": "Meta API",
          "gate": "human-approval",
          "id": "dry-run-publishing",
          "next_step": "Dry-run-Verhalten bei jedem spaeteren API-Ausbau als Default erzwingen.",
          "owner": "Meta API Agent",
          "priority": "P0",
          "status": "done",
          "title": "Meta Client bleibt dry-run-first und blockiert Live-Writes",
          "workstream": "ops-compliance-runtime"
        },
        {
          "acceptance": "ApprovalRequest, AuditEvent und Publishing Policy erzwingen explizite Freigabe fuer Live-Writes.",
          "area": "Governance",
          "gate": "human-approval",
          "id": "human-approval-gate",
          "next_step": "Approval-Events spaeter persistent speichern und in UI/Stage-Gate anzeigen.",
          "owner": "Compliance Agent",
          "priority": "P0",
          "status": "done",
          "title": "Human Approval Gate fuer Publishing und Budgetaenderungen",
          "workstream": "ops-compliance-runtime"
        },
        {
          "acceptance": "docs/DOKPLOY_DEPLOYMENT.md und ops/dokploy Beispiele beschreiben dev-meta synthetic-only, stage-meta guarded und konkrete Compose-Pfade.",
          "area": "Deployment",
          "gate": "dokploy-readiness",
          "id": "dokploy-dev-stage-plan",
          "next_step": "Runtime Compose, Healthchecks und Smoke-Gates im Roadmap-Vertrag halten.",
          "owner": "DevOps Agent",
          "priority": "P0",
          "status": "done",
          "title": "Dokploy-Plan fuer dev-meta und stage-meta dokumentieren",
          "workstream": "ops-compliance-runtime"
        },
        {
          "acceptance": "Riskante Targeting-Felder und enge Geo-Radien werden fuer Housing blockiert oder hart gewarnt.",
          "area": "Compliance",
          "gate": "compliance-review",
          "id": "housing-compliance-gate",
          "next_step": "Audit-Event-Persistenz und Policy-Versionierung spaeter ergaenzen.",
          "owner": "Compliance Agent",
          "priority": "P0",
          "status": "done",
          "title": "Housing-/Real-Estate-Compliance-Gate",
          "workstream": "ops-compliance-runtime"
        },
        {
          "acceptance": "dev-meta ist live erreichbar, nutzt keine echten Kundendaten, zeigt die Roadmap und Meta-Writes sind false.",
          "area": "Deployment",
          "gate": "dev-meta-smoke",
          "id": "dokploy-dev-meta-deploy",
          "next_step": "dev-meta nach jedem main-Deploy mit Runtime Doctor und Public Smoke pruefen.",
          "owner": "DevOps Agent",
          "priority": "P1",
          "status": "done",
          "title": "dev-meta Dokploy Runtime mit synthetischen Daten",
          "workstream": "ops-compliance-runtime"
        },
        {
          "acceptance": "GitHub-App sieht rb007x75/meta-ads; lokales git remote -v zeigt origin; Dokploy General/GitHub kann main auswaehlen.",
          "area": "Deployment",
          "gate": "dokploy-readiness",
          "id": "github-repo-dokploy-link",
          "next_step": "main pushen und Dokploy-Provider auf docker-compose.yml ausrichten.",
          "owner": "DevOps Agent",
          "priority": "P0",
          "status": "done",
          "title": "GitHub Repo fuer Dokploy sichtbar machen",
          "workstream": "ops-compliance-runtime"
        },
        {
          "acceptance": "scripts/stage-meta-release-gate.sh prueft Roadmap, generierte Artefakte, Stage Compose, Runtime Doctor und optional Public Smoke samt /readyz Safety JSON.",
          "area": "Deployment",
          "gate": "stage-promotion",
          "id": "stage-meta-gate",
          "next_step": "Stage-Public-Smoke nach erstem stage-meta Deploy mit STAGE_PUBLIC_URL regelmaessig ausfuehren.",
          "owner": "DevOps Agent",
          "priority": "P1",
          "status": "done",
          "title": "stage-meta Gate fuer pilotfaehige Demo",
          "workstream": "ops-compliance-runtime"
        },
        {
          "acceptance": "INTERNAL_ROADMAP_TOKEN schuetzt Roadmap, Audit- und Workstream-JSON-Routen; stage-meta /readyz bleibt ohne aktiven Schutz rot.",
          "area": "Security",
          "gate": "dokploy-stage",
          "id": "internal-roadmap-protection",
          "next_step": "Dokploy-Token fuer stage-meta vor erster Kundendemo setzen und Browser-Auth-Option bewerten.",
          "owner": "Security Agent",
          "priority": "P0",
          "status": "done",
          "title": "Interne Roadmap-Routen optional schuetzen",
          "workstream": "ops-compliance-runtime"
        },
        {
          "acceptance": "scripts/dev-meta-postdeploy-gate.sh prueft Roadmap, Generatoren, Compose, Runtime Doctor, Public Smoke, /readyz und public status JSON.",
          "area": "Deployment",
          "gate": "dev-meta-smoke",
          "id": "dev-meta-postdeploy-gate",
          "next_step": "Gate nach jedem Dokploy-Deploy ausfuehren und spaeter als GitHub Actions Workflow automatisieren.",
          "owner": "DevOps Agent",
          "priority": "P1",
          "status": "done",
          "title": "dev-meta Postdeploy Gate fuer dauerhafte Pruefbarkeit",
          "workstream": "ops-compliance-runtime"
        }
      ],
      "focus": "Roadmap-Vertrag, Dokploy, Stage-Gates, Approval, Housing, Meta Write Lock und Live-Betrieb.",
      "id": "ops-compliance-runtime",
      "open": [
        {
          "acceptance": "Keine Kampagne, kein Budget, keine Audience und kein Pixel wird ohne explizites Gate geaendert.",
          "area": "Meta API",
          "gate": "meta-write-lock",
          "id": "live-meta-api-writes",
          "next_step": "Erst nach Data Trust, Approval, Audit, Stage und Kundenfreigabe erneut bewerten.",
          "owner": "Meta API Agent",
          "priority": "P3",
          "status": "open",
          "title": "Live Meta API Writes bleiben bewusst offen/deferred",
          "workstream": "ops-compliance-runtime"
        }
      ],
      "partial": [],
      "title": "Liste 6: Ops, Compliance und Runtime"
    }
  ]
}