Epic: Refactor Cascade to extend journalism-investigation base typesbacklog_item

refactoringjournalisminvestigationcascadeepic
1 min read · Edit on Pyrite

Overview

Refactor the Cascade plugin to inherit from journalism-investigation base types instead of duplicating them. Currently Cascade defines its own actor (extends PersonEntry), cascade_org (extends OrganizationEntry), and cascade_event/timeline_event (extends EventEntry). After this epic, Cascade extends the journalism-investigation versions of these types, gaining financial tracking, claims, and evidence chains for free.

Inheritance Plan

``` journalism-investigation ├── person → actor (adds: tier, era, capture_lanes, chapters) ├── organization → cascade_org (adds: capture_lanes, chapters) ├── investigation_event → cascade_event (adds: era, capture_lanes, chapters) ├── investigation_event → timeline_event (adds: capture_lanes, actors, capture_type, connections, patterns) ├── investigation_event → solidarity_event (adds: infrastructure_types, lineage, legacy, capture_response, outcome) └── (cascade-only) mechanism, scene, victim, statistic, theme ```

Subtasks

1. Entry type inheritance — Cascade types extend journalism-investigation types instead of core types 2. MCP tool delegation — Cascade MCP tools delegate to journalism-investigation base where possible 3. Migration and compatibility — existing Cascade KBs continue to work, migration path for frontmatter changes

Success Criteria

  • Cascade plugin depends on journalism-investigation plugin
  • All existing Cascade tests pass without modification
  • Cascade KBs gain access to transaction, ownership, claim types via journalism-investigation
  • No breaking changes to existing KB data