Skip to content

Rename InterventionStatus → ProjectStatus + retire "intervention" prose#14

Merged
ProfessorPolymorphic merged 1 commit into
mainfrom
rename-intervention-status-to-project-status
May 3, 2026
Merged

Rename InterventionStatus → ProjectStatus + retire "intervention" prose#14
ProfessorPolymorphic merged 1 commit into
mainfrom
rename-intervention-status-to-project-status

Conversation

@ProfessorPolymorphic
Copy link
Copy Markdown
Contributor

Summary

  • Rename Value_Group: "InterventionStatus""ProjectStatus" in vocabularies/iids-portfolio/allowed_values.json. Five internal references in PublicStage and ProductionScope verification rules updated to match.
  • Replace "intervention" with "project" in 11 prose descriptions across the IIDS Portfolio domain catalog.
  • Bump version 1.0.0 → 2.0.0 (renaming a Value_Group is breaking for any string-matching consumer).

Why

Stakeholder feedback on the consuming site (May 2026): "intervention" reads as harsh and clinical for an institutional audience. "Project" is the term the audience already uses, matches the language on /builder-guide ("Submit a Project") on the consuming site, and lets the IIDS Portfolio voice match the brand brief's quietly-confident register.

This is the upstream half of a coordinated rename. See ui-insight/AISPEG#189 for the epic and ui-insight/AISPEG#190 for this slice's tracking issue.

Scope

Single file: vocabularies/iids-portfolio/allowed_values.json. 18 line changes (18+/18−). Only string substitutions; no structural changes to the JSON schema.

Verified:

  • python3 -c "import json; json.load(...)" — JSON valid.
  • grep -ri "intervention" . — no remaining occurrences anywhere in the repo (other domain catalogs, scripts, README, and docs/ carry no references).
  • scripts/check_governance_drift.py does not string-match InterventionStatus, so the upstream drift check is unaffected by the rename.

Sequencing

Once this lands, ui-insight/AISPEG#191 follows immediately to bump the AISPEG submodule pointer and regenerate the local typed catalogs. The drift CI on AISPEG will be red on unrelated PRs in the interim — closing that gap is the rename epic's known sequencing risk.

Test plan

  • Upstream Governance Drift CI green on this PR.
  • After merge, AISPEG submodule bump (#191) regenerates lib/governance/{catalog,vocabularies}.ts cleanly with no drift.

🤖 Generated with Claude Code

Stakeholder feedback (May 2026): "intervention" reads as harsh and
clinical for an institutional audience. "Project" is the term the
audience already uses, matches the language on /builder-guide ("Submit
a Project") on the consuming site, and lets the IIDS Portfolio voice
match its brand brief's "quietly-confident" register.

Changes to vocabularies/iids-portfolio/allowed_values.json:

- Value_Group "InterventionStatus" → "ProjectStatus" (5 internal refs in
  PublicStage and ProductionScope verification rules updated to match)
- Prose substitutions: "AI interventions" → "AI projects", "an
  intervention" → "a project", "the intervention's" → "the project's",
  "successor intervention slug" → "successor project slug",
  "Externally-owned intervention" → "Externally-owned project", "One
  intervention can sit in" → "One project can sit in", "other
  interventions" → "other projects".
- Bumped version 1.0.0 → 2.0.0 (renaming a Value_Group is breaking for
  any string-matching consumer).
- Updated last_updated to 2026-05-03.

JSON validated. No structural changes. Other domain catalogs and the
drift-check script (scripts/check_governance_drift.py) carry no
references to the old name.

Coordinated with the consuming site rename: see ui-insight/AISPEG#189.
The AISPEG submodule bump + drift-CI fix-ups follow immediately in
ui-insight/AISPEG#191.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@ProfessorPolymorphic ProfessorPolymorphic merged commit 902b73a into main May 3, 2026
1 check passed
@ProfessorPolymorphic ProfessorPolymorphic deleted the rename-intervention-status-to-project-status branch May 3, 2026 21:29
ProfessorPolymorphic added a commit to ui-insight/AISPEG that referenced this pull request May 3, 2026
…tatus (#194)

Picks up the upstream rename from ui-insight/data-governance#14 and
threads the new vocabulary group identifier through every consumer.
This is slice 2 of epic #189 (rename "intervention" → "project");
upstream PR slice was #190.

Changes:

- vendor/data-governance pointer: f6afe34 → 902b73a (the upstream
  rename PR's merge commit).
- lib/governance/vocabularies.ts: regenerated via npm run
  build:governance. Auto-generated; do not hand-edit.
- TypeScript type and guard renames across consumers:
    InterventionStatus     → ProjectStatus
    isInterventionStatus() → isProjectStatus()
  Touched: lib/portfolio.ts (definitions), lib/portfolio-verification.ts,
  lib/lifecycle-display.ts, lib/governance/types.ts (comment),
  app/portfolio/page.tsx, app/admin/registry/new/page.tsx (comment),
  components/PortfolioCard.tsx, components/PortfolioFilters.tsx.

Verified:

- npm run build:governance — clean; emits ProjectStatus.
- npm run build — clean (no type errors, all 80+ static paths
  prerendered).
- npm run verify:portfolio — passes.
- grep -rn "InterventionStatus" — zero matches outside vendor and
  build artifacts.
- scripts/governance-drift.py / governance-pr-summary.ts /
  governance-freshness.ts carry no string references to the renamed
  group; CI logic is unaffected.

Out of scope for this slice (handled in the remaining slices):

- Component file rename InterventionDetail.tsx → ProjectDetail.tsx and
  the broader Intervention type rename — slice #192.
- User-facing JSX copy ("intervention" prose) and docs (CLAUDE.md,
  REFACTOR.md, ADR 0001, etc.) — slice #193.

Closes #191. Refs #189.

Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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.

1 participant