RGP Traceability Matrix: Constitution & Requirements v8.0 vs Current Build

Date: 2026-04-03
Purpose: Map the current implementation to the constitutional and requirements surface so the remaining remediation work is explicit and actionable.

Status Legend

• Implemented: present in code, exposed through live API/UI, and covered by tests
• Partial: present in code and/or data model, but not fully exposed, enforced, or tested
• Spec Only: defined in constitution/requirements, but not meaningfully integrated into the live product path

Traceability Matrix

Integration Reality Check

The recent external-agent/backend expansion materially improved the codebase, but most of the new capability sits in one of four states:

1. Integrated into live product
   • request lifecycle
   • template workbench
   • org administration
   • reviews/promotions
   • analytics
   • agent sessions
2. Backend-scaffolded but not routed
   • domain packs
   • planning constructs
   • knowledge artifacts
   • saga orchestration
   • queue routing
   • SLA enforcement
3. Modeled and migrated but not yet productized
   • editorial/content workflows
   • billing/quota enforcement
   • data governance
   • multi-view board/graph/roadmap projections
4. Specified but still weakly expressed in live runtime behavior
   • policy-driven collaboration mode changes beyond the request agent journey

Actionable Remediation Plan

Track 1: Make the New Backend Real

These areas already have enough backend structure that the next step should be product integration, not more domain scaffolding.

1. Federation / Projection / Reconciliation
   • Add admin/API surfaces for projection mappings and reconciliation conflicts
   • Expose reconciliation status in integration drill-down pages
   • Add live workflows that project canonical entities into at least one external substrate and reconcile them back
     • Status: first operator-facing slice is implemented on admin integrations; remaining gap is richer conflict handling and broader cross-system visibility
2. Planning / Knowledge / Domain Packs
   • Add first-class routes and pages
   • Move these from pure backend capability into user-operable product flows

Track 2: Convert Partial Control Logic into Active Governance

1. Queue Routing
   • Promote generalized assignment queues beyond review queue only
   • Expose routing basis: skill, workload, SLA, policy domain
2. SLA Enforcement
   • Move from analytics/risk visibility into active escalation and blocking behavior
3. Workflow Engine
   • Bind more request execution through the new workflow engine rather than primarily repository-driven hard-coded transitions

Track 3: Close Spec/Product Drift

1. Add routed/API/UI traceability for:
   • FR-DOM-*
   • FR-PLAN-*
   • FR-KNOW-*
   • FR-FED-*
   • FR-PROJ-*
   • FR-SYNC-*
   • FR-CONF-*
2. Extend the compliance suite so it checks not only document presence, but also:
   • route exposure for major implemented capabilities
   • service-to-endpoint integration for major new backend modules
   • browser/API journeys for any area claimed as Implemented

Recommended Next Milestone

The most leverage comes from treating this as an integration milestone, not another modeling milestone:

• Milestone A: Agent Context + MCP productization
  • Status: materially complete for the current request agent journey
• Milestone B: Federated projection/reconciliation productization
• Milestone C: Planning + knowledge + domain pack productization

If those three are completed, the build will begin to match the expanded v8.0 constitutional surface rather than merely anticipating it.