Skip to content

Move data product registry into Semantic module#7

Draft
earthshiner wants to merge 1 commit into
mainfrom
feat/semantic-registry-location
Draft

Move data product registry into Semantic module#7
earthshiner wants to merge 1 commit into
mainfrom
feat/semantic-registry-location

Conversation

@earthshiner
Copy link
Copy Markdown
Collaborator

@earthshiner earthshiner commented May 31, 2026

Summary

  • replace governance.data_product_registry with {{DB_SEMANTIC_STD_T}}.data_product_registry in the Semantic standard introduced by PR Add data product orientation layer #6
  • update registry comments and module lists to describe the registry as part of the Semantic module
  • update the Memory design-decision seed and agent lifecycle reference
  • update the access prompt fallback to query {SemanticDatabase}.data_product_registry

Rationale

PR #6 added the Data Product Orientation Layer, but it placed the registry in governance.data_product_registry. governance is not a database defined by the AI-native data product standard. The registry is product orientation metadata and should live inside the Semantic module, alongside data_product_map and the other metadata surfaces agents use for discovery.

This keeps the standard self-contained: agents discover the product manifest first, then use the Semantic module registry and metadata map before navigating to data.

Verification

  • rg confirmed no remaining governance.data_product_registry references in the updated standards, prompts, or lifecycle doc.

@earthshiner earthshiner self-assigned this May 31, 2026
@earthshiner earthshiner added the bug Something isn't working label May 31, 2026
@earthshiner earthshiner assigned NathanG-TD and unassigned NathanG-TD May 31, 2026
@earthshiner earthshiner marked this pull request as draft June 1, 2026 05:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants