Migrate an AI-Agent Dataset to a Business Key

[gregagi]

Post

• Title: Migrate an AI-Agent Dataset to a Business Key
• Slug: /blog/migrate-agent-dataset-business-key
• Type: how-to / operational decision guide
• Target: business key database (DataForSEO: 10 US searches/month; KD unavailable)

Selection and research

The prior measured backlog entries are explicitly deferred for overlap, authority, or weak product fit. This post fills the coverage map’s highest-priority open product-native gap: generated-index migration patterns. Live SERP research for database primary-key migration found an AI Overview, primary vendor docs, forum answers, and PAA questions. Claims are traced to PostgreSQL, Google Cloud Spanner, Rowset live docs, and Rowset repository behavior in the committed SEO brief.

Information gain: a five-phase identity migration contract for agent-managed datasets: map → mirror → verify → cut over → retire. It covers durable key maps, deterministic mirroring, relationship translation, agent-configuration cutover, canary verification, and rollback.

Side checks

• ai-seo: pass — direct answer and liftable process at the top; self-contained claims; source attribution; entity and PAA coverage; published/updated dates; existing BlogPosting schema considered and verified.
• product-led-seo-strategy: pass — solves a real Rowset identity-migration job, uses Dataset API/MCP/schema/by-index surfaces honestly, adds two natural inbound links, and connects to setup and pricing paths.

Files changed

• New post and verified SEO brief
• Content ledger, keyword state, SERP snapshot, and link inventory
• Inbound links from schema docs and the index-column guide
• Changelog entry

Validation

• word_count.py: 1,559 words (1,200 minimum)
• New post: 6 in-body internal links and 2 inbound links
• link_audit.py --orphan-check: new slug passes; reports only three unrelated legacy placeholder routes
• JSON validation: .seo/config.json and .seo/keyword-research.json pass
• Django manage.py check: pass
• Blog frontmatter loader and BlogPosting schema: pass
• Local blog route render: 200, one H1, schema and required links present
• git diff --check: pass
• Full local pytest/sitemap: unavailable because this runtime lacks Make/Docker/PostgreSQL; GitHub CI is the broad validation gate

This daily content PR is exempt from Greptile, ReviewGate, CodeRabbit, and other automated review-bot gates.

[github-actions]

Review Gate Summary

All enabled ReviewGate review angles passed.

Confidence Score: 5/5

Review angle	Score	Findings
General	5/5	0
Adversarial	5/5	0

Runtime phase	Duration
Queue	0.00s
Startup	4.60s
Model review	132.24s
Publish	1.49s

Findings: 0 total, 0 blocking, 0 inline candidates
Notes: 7 note(s) in the JSON artifact.

No findings. Re-run ReviewGate if new commits land.

Important Files Changed

No files require special attention from this review.

Flowchart

flowchart TD
    A["Pull request update"] --> B["ReviewGate analyzes the latest commit"]
    B --> C["Model review stages"]
    C --> D["Structured JSON artifact"]
    D --> E["Confidence Score: 5/5"]
    D --> F["Canonical PR summary comment"]
    F --> G["Human or agent fixes findings"]
    E --> H["Status: passed"]

Loading

_{Reviews on this PR: 1 run. Changed lines analyzed: 403. Total cost: $0.02. Latest commit analyzed: ca3c55dd11aed43f5fdc8776ff6233429efae9e7.}