Build a complete standalone public GitHub-ready repository named ComplyWatch-KE from this specification. Owner: Joseph Macibi Njoroge, Nairobi-based Senior Software Engineer transitioning into technical compliance. Credential anchor: Governance, Risk and Compliance Certification from Strathmore University, completed with Distinction in 2024. Use the attached compliance portfolio brief as the requirements source, especially Prompt 2 (Automated Regulatory Reporting & Compliance Telemetry Dashboard: AML + incident readiness). Improve it into an executable implementation plan: full directory tree; Python 3.12 FastAPI service; PostgreSQL; seeded synthetic generator for approximately 5,000 customers and 500,000 transactions with labelled scenarios and benign look-alikes; config-driven explainable rules; detection-quality evaluation; case/SAR workflow with legal-source caveats; four-eyes approval; tamper-evident chained audit trail; Prometheus metrics; Grafana dashboards as versioned JSON; monthly HTML/PDF report reconciliation; RBAC, auth, rate limiting, validation, non-root containers, secret scanning, dependency audit, threat model, optional mock-only AI explainer; docs/SOURCES.md, docs/DETECTION_QUALITY.md, docs/THREAT_MODEL.md, architecture diagram, demo script, .env.example, Makefile, Docker Compose, CI and PROGRESS.md. Do not fabricate legal claims or thresholds: all thresholds are config-driven with source URLs/access dates and [UNVERIFIED] warnings when not confirmed. Synthetic data only, no real PII. Work in numbered gates, run each verification, record exact evidence and PASS/FAIL. Ensure fresh clone can run the demo. At completion summarize files, verification results, limitations and unverified items.