Product portfolio overview
This overview maps the local product repositories discovered under projects/ and the supporting Meridian platform context inspected from the workspace root.
Portfolio map
| Product | Category | Apparent stage | Core value proposition | Reusable assets | Could support |
|---|---|---|---|---|---|
| SiteIntel | SaaS candidate, public/free tool, domain intelligence platform | Private alpha / active build | Turn a domain into an evidence-backed website health, monitoring, and change report. | Task registry, source adapters, domain registry, findings model, bulk ingest, report story pattern. | Trackpal website checks, agency tooling, public smoke-alarm tools, competitor monitoring, domain datasets. |
| DataStitcher | Data platform, public-data product factory, internal accelerator | Platform build | Turn messy public datasets into governed, searchable, dashboard-ready data products. | Monitored ingestion pattern, semantic registry, GCS/BigQuery pipeline, docs generator, data-product config model. | Public-good data products, Trackpal market context, SiteIntel enrichment, reusable ingestion packages. |
| BigQuery Atlas | Data product, developer/research tool, SaaS candidate | Catalogue build | Discover and monitor public BigQuery projects and dataset/schema changes without brute forcing. | Evidence-backed discovery, cautious validation, BigQuery catalogue model, D1/R2 read-cache pattern, rate-limit policy. | DataStitcher source discovery, SiteIntel bulk enrichment, public dataset alerts, BigQuery catalogue packages. |
| Bollocks Radar | Public/free tool, trust-signal product, possible SaaS/API/widget | MVP build | Help users search claims, see fact-check source evidence, and avoid treating no match as truth. | Google Fact Check ingestion, verdict normalisation, publisher sweeps, claim clustering, task locking pattern. | SiteIntel trust/reference signals, public-good fact-check widgets, evidence-first source ingestion patterns. |
| Trackpal | SaaS candidate, small-business/agency operations tool | Private-beta implementation slice; dossier metadata partly stale | Give agencies and small businesses template-driven KPI scorecards without making them build dashboards. | Template-driven dashboards, metric catalogue, provider registry, admin operations shell, sync health model. | SiteIntel agency offering, reusable dashboard renderer, provider/secret-status admin components. |
| Codex Sessions Analyser | Developer tool, internal accelerator | Local-first active tool | Analyse local Codex JSONL sessions for cost, timing, tool usage, reports, dashboards, and redacted sync exports. | JSONL parser, SQLite analysis cache, timeline model, local dashboard, pricing/cost estimation, redacted export. | AI-agent productivity analytics, Compass/Hub agent telemetry, local developer reports. |
Supporting platform context
Fact: Meridian core owns generic tooling, schemas, validation, shared packages, agent guidance, and the Meridian Hub app. It is not the place for private product strategy.
Fact: Meridian Hub is intended to own live operational visibility: provider status, sync logs, deployments, build state, repository analysis, and current health.
Fact: Product Compass owns synthesis: capability maps, reuse opportunities, product strategy, AI context, and portfolio knowledge.
Inference: Meridian Hub and Meridian Works should be treated as internal accelerators for this portfolio, not as ordinary product repositories in the portfolio map.
Strategic shape
The portfolio is not a random pile of apps. It is clustering around four useful product families:
- Evidence-backed intelligence products: SiteIntel, Bollocks Radar, BigQuery Atlas, and parts of DataStitcher all collect public evidence, normalise it, and present cautious interpretations.
- Governed data platforms: DataStitcher, BigQuery Atlas, and SiteIntel bulk ingest all need source registries, run state, artefact storage, data contracts, and generated documentation.
- Operational SaaS/admin shells: Trackpal, SiteIntel, DataStitcher, BigQuery Atlas, and Bollocks Radar all need protected admin surfaces, provider status, secret-status views, sync/run history, and bounded manual actions.
- AI/developer acceleration: Codex Sessions Analyser, Meridian CLI, Meridian Hub, generated docs, and Product Compass can compound by making future AI-agent work more observable and less duplicative.
Stage notes
Fact: Trackpal has conflicting source signals. Its generated project dossier still marks surfaces as planned, but the README and package manifests describe a first private-beta implementation slice with web/admin apps, sync worker, core package, migrations, demo data, and beta preflight scripts.
Inference: Trackpal should be treated as implemented-but-early, with its generated dossier marked stale until the Trackpal repo updates metadata/project-dossier.json.
Fact: Codex Sessions Analyser does not currently publish the same structured product dossier metadata as the other product repos.
Inference: Product Compass should either ask Codex Sessions Analyser to publish a dossier or keep its authored dossier clearly labelled as README/package-derived.
Sources consulted
projects/bollocks-radar/apps/websites/docs/metadata/project-dossier.jsonprojects/bq-atlas/apps/websites/docs/metadata/project-dossier.jsonprojects/data-stitcher/apps/websites/docs/metadata/project-dossier.jsonprojects/site-intel/apps/websites/docs/metadata/project-dossier.jsonprojects/trackpal/apps/websites/docs/metadata/project-dossier.jsonprojects/codex-sessions-analyser/README.mdprojects/trackpal/README.mdREADME.mddocs/architecture/meridian-compass-knowledge-space.mddocs/architecture/meridian-works-shared-platform.mdapps/websites/project-hub/README.md