Skip to main content

Product Compass briefing

What Product Compass is​

Product Compass is the curated synthesis layer for Scott's product ecosystem. It explains what product ideas exist, what has been built, what capabilities repeat across repos, what could be reused, and what future products can be built from current work.

The operating rule is:

Repositories own facts. Meridian core owns tooling. Meridian Hub owns live operational visibility. Meridian Product Compass owns synthesis.

What to read first​

For a cross-project task, read in this order:

  1. docs/compass/repository-boundaries.md
  2. docs/sources/local-source-inventory.md
  3. docs/projects/portfolio-overview.md
  4. The relevant project dossier under docs/projects/<project-id>/overview.md
  5. docs/capabilities/capability-map.md
  6. docs/reusable-components/extraction-candidates.md
  7. Relevant opportunity, integration, and tracing-board docs.

Fact, inference, opportunity​

Use these labels strictly:

  • Fact: Directly supported by source docs, package metadata, generated project dossiers, or code/config inspected.
  • Inference: A reasoned conclusion from multiple facts, such as reuse potential across two products.
  • Opportunity: A future product, tool, extraction, or improvement that is not yet implemented.

Do not turn an opportunity into a fact. Do not present an inference as repository truth.

Current portfolio​

  • SiteIntel: domain intelligence and website monitoring SaaS candidate.
  • DataStitcher: governed public-data ingestion, registry, marts, and product platform.
  • BigQuery Atlas: public BigQuery discovery, validation, catalogue, and change-intelligence candidate.
  • Bollocks Radar: claim search and fact-check evidence product.
  • Trackpal: private-beta template-driven KPI monitoring and scorecards.
  • Codex Sessions Analyser: local-first AI session analytics developer tool.

Important current gaps​

  • No product repo published capabilities.inventory.json or reuse-candidates.json during this pass.
  • Codex Sessions Analyser did not publish a Product Compass-compatible project dossier.
  • Trackpal's generated dossier is stale relative to README/package evidence.
  • Product Compass source generation currently covers the five projects that publish structured dossiers.

Client/private information rule​

Client-specific information does not belong in Product Compass. Generic patterns learned from client work can be described only when sanitised and without naming or leaking client details.

AI assistant rule​

When asked to work from Product Compass, use it as a map, not as the source of truth for repository facts. If implementation depends on a product's current code or docs, read the owning product repository before editing anything.

Sources consulted​

  • docs/compass/repository-boundaries.md
  • docs/sources/local-source-inventory.md
  • docs/projects/portfolio-overview.md
  • docs/capabilities/capability-map.md