Skip to content

Phase 2 Build-Out Execution Roadmap

This document operationalizes Phase 2 delivery without modifying the original plan file.

Objectives

  • Complete RealOutcomes as the primary nonprofit intelligence surface.
  • Complete Last1 + RadioCheck as a production accountability and outcomes-certification loop.
  • Reconcile data models and migrations so runtime paths match schema reality.
  • Ship verifiable, versioned public registry and ecosystem admin controls.

Workstreams

1) RealOutcomes Graph Depth and Financial-Lever Analysis

  • Expand network ingestion beyond board/political edges:
  • IRS Schedule I grant flows (funder -> recipient).
  • Major donor/institutional relationships where available.
  • Multi-hop org-to-org governance and donation chains.
  • Promote graph-first UX:
  • Node/edge evidence cards with explicit source links.
  • Saved graph views and filter presets per user tier.
  • Geospatial lens (state/city overlays and regional concentration metrics).
  • Add explainability:
  • Plain-language findings for each score dimension.
  • Confidence labels and uncertainty indicators when evidence is thin.

2) Last1 Validation Engine and Certification State Machine

  • Formalize validation stages:
  • Draft -> Pending Review -> Conditional -> Active Standard -> Active High -> Suspended/Revoked.
  • Add policy checks:
  • Outcome evidence freshness, staff validity, and cross-source consistency.
  • Appeals/remediation workflows with auditable transitions.
  • Wire event-driven notifications:
  • Outcome verified/disputed.
  • Certification state change.
  • Escalation/on-call acknowledgments and overdue reminders.

3) RadioCheck Revenue Loop Hardening

  • Plan-gated enforcement:
  • Scheduled campaigns require paid tier.
  • Participant/campaign/history quotas enforced at write time.
  • Billing linkage:
  • Metered usage records for campaigns/check-ins/escalations.
  • Stripe reconciliation jobs and failure recovery.
  • Operational integrity:
  • Retry/backoff for outbound messaging.
  • Dead-letter handling and replay tooling.

4) Migration and Schema Reconciliation

  • Define canonical schema ownership and naming (avoid split-brain organizations vs last1_organizations semantics).
  • Add idempotent migrations for:
  • Bridge tables (org_bridge, user_identity_bridge) constraints and column compatibility.
  • Required indexes for RPC ON CONFLICT paths.
  • Backfills for legacy columns and null defaults.
  • Add migration validation CI step:
  • Apply all migrations to a clean DB.
  • Run schema assertions against expected constraints/functions.

5) Registry API Versioning and Public Surfaces

  • Ship /api/public/registry versioned contract:
  • v1 (current consumers) and v2 (extended validation metadata).
  • Backward-compatible fallback when optional columns are missing.
  • Add contract tests:
  • Snapshot response shape for both versions.
  • Verify resilient behavior with partially migrated DBs.
  • Add provenance fields:
  • Last review date, confidence band, evidence freshness band, verification links.

6) Ecosystem Admin / SSO / last1.id Alignment

  • Implement org-scoped admin controls:
  • Feature flags by tier and environment.
  • Audit trail viewer and remediation controls.
  • Complete identity coherence:
  • Stable link semantics across Last1, RadioCheck, and last1.id.
  • Admin tooling for safe relink/unlink with audit history.
  • Enforce role propagation:
  • Owner/admin/provider/member mappings across surfaces.

Release Plan

Milestone A: Schema and Bridge Reliability (1-2 weeks)

  • Finish migration reconciliation and RPC compatibility.
  • Run rollback-safe smoke tests for linking and campaign trigger paths.
  • Exit criteria: no 503/500 integration failures from missing schema assumptions.

Milestone B: Accountability Loop Integrity (2-3 weeks)

  • Complete outcome validation and notification pathways.
  • Add end-to-end tests for org -> program -> milestone -> member validation -> verified outcome.
  • Exit criteria: deterministic completion of the loop with auditable events.

Milestone C: RealOutcomes Intelligence Surface (2-4 weeks)

  • Graph-first cross-entity analysis and evidence explainability.
  • Tier-gated advanced filters and institutional views.
  • Exit criteria: production graph workflows usable by donors/funders/institutions.

Milestone D: Registry + Admin + Identity Completion (2-3 weeks)

  • Versioned registry API and admin controls.
  • SSO/identity coherence and operator workflows.
  • Exit criteria: stable public registry contract and internal governance tooling.

Validation and QA Gates

  • TypeScript checks green for touched packages.
  • Migration replay test on clean DB.
  • RPC smoke tests (transaction rollback and persisted staging checks).
  • API contract tests for registry and integration endpoints.
  • Manual E2E scripts for:
  • RadioCheck paid campaign flow.
  • Outcome verification to certification visibility.
  • RealOutcomes search -> profile -> graph investigation.