Learn · TrustedAIGov® Enterprise Knowledge Platform
Informational Fresh jira_story: GOV-212

Lesson 3 of 4 — Migrate Intelligence off per-tenant JSON

Data Platform Hardening · Source: Jira Story GOV-212 (13 pts) · Authority: Informational (the Jira story is authoritative).

Purpose

Move Intelligence data from per-tenant JSON to relational storage.

Why it matters

Relational storage removes a fragile seam and enables joins, queries, and audit.

Where this lives

Runs in the Customer AI Governance platform (components: intelligence). Discovery/classification persist to relational tables; the JSON seam is retired. Learn teaches this read-only.

Workflow

  1. Given discovery and classification data
  2. When it is persisted
  3. Then it is stored relationally and the JSON seam is removed

Worked example

Intelligence stores each tenant's classifications in a JSON blob. Why migrate to relational?

To remove the fragile seam and enable joins, queries, and audit — the JSON seam is retired.

Acceptance criteria (authoritative — GOV-212)

Given discovery and classification data, when it is persisted, then it is stored relationally and the JSON seam is removed.

Common pitfalls

  • Leaving the per-tenant JSON seam in place, blocking real querying.

Knowledge check

  • Scenario: Intelligence stores each tenant's classifications in a JSON blob. Why migrate to relational?
  • Look for: To remove the fragile seam and enable joins, queries, and audit — the JSON seam is retired.

Key concepts

  • relational persistence
  • JSON seam removal
  • Intelligence data

For the AI Tutor

  • Summary: Move Intelligence data from per-tenant JSON to relational storage.
  • When to use: teaching or answering questions about "migrate intelligence off per-tenant json".
  • When NOT to use: the classification step itself (that is GOV-115).
  • Key concepts: relational persistence, JSON seam removal, Intelligence data.

Completion criteria

Learner passes the scenario knowledge check and can point to the system state that satisfies GOV-212's acceptance criterion.

  • Module: LEARN-MOD-007 (Data Platform Hardening)
  • Provenance: LEARN-MAP-001 · Generation standard: LEARN-STD-002
  • Next: LEARN-LSN-038
← PreviousNext →