CDP Repository Portfolio
This review uses GitHub pushedAt as the signal for code changes. As of 2026-07-02, the CDPworldwide organization exposes seven repositories to the current GitHub token.
July 2026 Code Activity
Only one repository has had code pushed in July 2026 so far.
| Rank | Repository | Last push | Visibility | Language | Assessment |
|---|---|---|---|---|---|
| 1 | CDPworldwide/cdp-adapt-ex | 2026-07-01 18:18 UTC | Public | Python | Already the reference implementation for project docs, product analytics, feedback loops, AI observability, and deploy tracking. |
There are not ten July-changed repositories visible in the organization. The nearest recent repositories are below so they can still be triaged for portfolio tracking.
Recent Repository Queue
| Repository | Last push | Current fit | Recommendation |
|---|---|---|---|
CDPworldwide/cdp-adapt-ex | 2026-07-01 | Public product with frontend, backend, AI server, data pipeline, Cloud Run deployment, PostHog, GA4, Sentry, Typeform, Slack, and Trigger.dev automation. | Keep as the template. Continue maintaining projects/adapt-action-explorer/analytics.md, feedback triage, Google/Looker access notes, and scheduled Slack summaries. |
CDPworldwide/cdp-geospatial-ops | 2026-06-10 | Private data-ops repo for Overture/GERS geometry resolution, area audits, overrides, GeoJSON/data outputs, and CDPJL/spatial logs that support the existing Adapt Explorer project. | Keep under the existing Adapt Explorer/geospatial operating context. Do not create a separate product project unless the workstream gains its own delivery surface; track data-quality metrics, run outputs, source freshness, geometry coverage, override decisions, and Slack/report automation from the Adapt project docs. |
CDPworldwide/pac-api | 2026-04-20 | Private older version of the Adapt Explorer architecture: frontend, backend, generated client, docs, Terraform, and GitHub Actions. | Treat as Adapt Explorer historical/legacy context, not a new project. Capture only migration lessons, old deployment references, and any reusable setup that differs from cdp-adapt-ex. |
CDPworldwide/cdp-discloser-profille-service | 2026-03-31 | Private internal API for CRM profiles, Overture entities, managed lists, hierarchy links, Neon/Postgres, and geometry coverage. | Already has projects/discloser-profiles/. Add an operations/analytics handoff: API health, endpoint usage, ingest batch freshness, geometry/profile coverage, deploy workflow status, and data-quality exceptions. |
CDPworldwide/paperclip-azure | 2021-08-18 | Stale Ruby storage adapter. | Inventory only. Consider archiving or marking maintenance/no-active-tracking. |
CDPworldwide/captchah | 2020-08-24 | Stale Rails captcha gem. | Inventory only. Consider archiving or marking maintenance/no-active-tracking. |
CDPworldwide/TROPICS-regression | 2020-06-01 | Stale R analysis script repository. | Preserve as historical research context if relevant, but do not add Adapt-style analytics or automation. |
What Should Get Adapt-Style Setup
Use Adapt Explorer as the full pattern only for products or services with active users, deployments, feedback, and measurable behavior.
| Setup area | Adapt Explorer pattern | Reuse for |
|---|---|---|
| Project page | index.md with components, repo refs, status, product surface, and start-here links. | Existing Adapt Explorer page should reference cdp-adapt-ex, legacy pac-api, and geospatial support repos where relevant; continue refining discloser-profiles. |
| Analytics handoff | Dashboard links, implemented events, PostHog/GA4/Looker status, known gaps, and success-metric mapping. | Adapt Explorer remains the product-funnel analytics home; discloser-profiles should use API/data-quality analytics rather than product-funnel analytics. |
| Automation docs | Local commands, secrets, Slack routing, Trigger.dev schedules, dry-run commands, and ownership notes. | Adapt Explorer docs should include geometry audit/report jobs where they support Explorer; discloser-profiles should document ingest/coverage jobs. |
| Feedback loop | Typeform plus Slack triage for user-facing feedback. | Keep this on Adapt Explorer unless another CDP product has its own active user feedback surface. |
| Observability | PostHog, Sentry, AI observability, Langfuse where applicable. | Adapt Explorer remains the full observability template; discloser-profiles should start with API health/error/usage and ingest quality. |
| Deployment tracking | GitHub Actions, Cloud Run URLs, environment variables, smoke checks, and production/preview surfaces. | Adapt Explorer and discloser-profiles; geospatial support repos only if they have scheduled jobs or published data artifacts. |
Where To Add Information In CDP Index
- Extend
projects/adapt-action-explorer/with a repository map that separates the current source repo, legacy PAC API history, Ask CDP AI, and geospatial support/log repositories. - Keep
partners/geospatial-ops/as the workstream entry point unless it needs independent project governance. It should track geometry coverage, override workflow, area audit outputs, data freshness, CDPJL/spatial logs, and outstanding upstream fixes. - Add a
projects/discloser-profiles/operations.mdhandoff covering API health, endpoint usage, deployment URL, Neon/Postgres ownership, ingest batches, missing geometry/profile counts, and workflow status. - Maintain the project-level repository registry at
projects/cdp-repository-portfolio/repos/index.json.index.jsonpoints MCP generation at that path so repository intelligence stays owned by this project rather than by a top-level registry folder. - Run the recurring GitHub inventory automation to record
pushedAt, default branch, workflows, open PRs/issues, deployment workflows, and whether each repo has a matching CDP Index project/workstream page. - Keep stale repositories in a separate maintenance/archive section rather than giving them full project pages.
MCP Tools
The CDP Index MCP exposes read-only repository portfolio tools backed by the project-level registry and generated inventory:
| Tool | Purpose |
|---|---|
list_cdp_repositories | List registered CDP repositories, filtered by project or tracking level. |
find_unlinked_repositories | Show visible GitHub repositories not linked in the registry, plus registered access-check gaps. |
get_project_code_links | Return current, legacy, support, and referenced repositories for a project. |
summarize_recent_repo_activity | Summarize recent pushed repositories by project from generated inventory. |
get_repository_operations_context | Return docs, surfaces, tracking level, analytics level, workflows, PRs, issues, and notes for one repository. |
Open Checks
- Verify whether
CDPworldwide/cdp-ai-enginestill exists, moved, or is inaccessible to the current token. CDP Index references it for Ask CDP AI, but it was not returned by the visible organization repository list. - Confirm which legacy
pac-apidetails still matter for Adapt Explorer history, migration decisions, or old deployment references. - Decide whether GitHub
pushedAtor broaderupdatedAtshould be the monthly activity metric for future portfolio reviews. UsepushedAtfor code activity andupdatedAtonly for broader repository activity.