Skip to content

fix(seed): assign TOGAF Architecture Domain to Riverdale capabilities#585

Merged
roballred merged 1 commit into
mainfrom
fix/togaf-seed-coverage
May 20, 2026
Merged

fix(seed): assign TOGAF Architecture Domain to Riverdale capabilities#585
roballred merged 1 commit into
mainfrom
fix/togaf-seed-coverage

Conversation

@roballred
Copy link
Copy Markdown
Owner

Summary

Before / after

total mapped derived unmapped
Before 7 0 0 7
After 7 0 7 0

After this change the report exercises the capability-derived inference path for every Riverdale application — direct-mapped applications can be demonstrated with a small follow-up if useful, but the derived path is the one practitioners use day-to-day.

Test plan

  • pnpm --filter govea db:seed reports ✓ 13 TOGAF domain mappings (capabilities) on first run, ✓ 0 on idempotent re-run.
  • DB verification: SELECT concept_label, count(*) FROM framework_mappings WHERE framework='togaf' AND entity_type='capability' GROUP BY concept_label returns Application=7, Business=3, Data=2, Technology=1.
  • Browser walk on /reports/togaf/application-landscape as carol@govea.dev shows derived mappings for all 7 applications.

Capability: fd-portfolio-views
Closes #582

🤖 Generated with Claude Code

The TOGAF Application Landscape report (/reports/togaf/application-
landscape) was showing 7 / 7 applications "Not yet mapped" on a fresh
seed because no framework_mappings rows existed. The field exists on
capabilities and applications; the seed simply didn't populate it.

Surfaced by the Domain Architect persona walk (#580) — the natural
landing page for a domain specialist (Business / Application / Data /
Technology) was empty out of the box.

Adds DEV_CAPABILITY_TOGAF_DOMAINS — an illustrative capabilityName →
TogafDomain map covering all 13 Riverdale capabilities — and seeds
framework_mappings rows for each one in run.ts. The assignments are
demonstrative (not authoritative TOGAF classification); orgs are
expected to assign their own mappings in practice.

After this change, the report renders 7 derived / 0 unmapped, exercising
both the direct-mapping panel (none for Riverdale capabilities) and the
capability-derived inference path the report supports.

Capability: fd-portfolio-views
Closes #582
@roballred roballred merged commit 5cf1957 into main May 20, 2026
6 checks passed
@roballred roballred deleted the fix/togaf-seed-coverage branch May 20, 2026 02:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

fix(seed): assign TOGAF Architecture Domain to seed capabilities so Application Landscape report renders non-empty

1 participant