Frontend Delta 2026-03-26

Version: v0.1 Status: Active Owners: Triton Front-end / Cortex / Foundation backend Last Updated: 2026-03-26

Purpose

This page tracks what changed after the original frontend handoff was fully implemented.

It separates three things:

• frontend work already shipped
• backend work still required for frontend-visible completeness
• next-gen FMIE artifacts that should become future UI surfaces

Already Shipped In Frontend

The following handoff-spec components are implemented:

• MediaPassportTrustPanel
• PartnerFitReadinessView
• MeetingIntelligenceView
• DocumentViewerOverlay
• HighlightReelView
• ProvenanceChainView
• FMIEHealthDashboard
• StrategyTwinView
• DisclosureApprovalView

Backend Still Owes Frontend

These are no longer missing UI components. They are missing or incomplete backend contract depth.

P0

• complete FMIE passport proof-material anchoring and expose it through stable backend trust models
• universal Gateway routing so disclosure, receipt, and trust states are complete everywhere
• full-length receipt commitments and stable receipt/trust fields for operator views
• consistent partner-fit readiness payloads driven by FMIE helper artifacts, not reconstructed ad hoc

P1

• richer FMIE runtime/health rollups for dashboard and operator surfaces
• stable clip/highlight response models with durable playback/share references
• clearer provenance explanations backed by backend trust state instead of raw FMIE fields

P2

• richer Strategy Twin backend state for contradiction history, review status, and recommendation lifecycle
• disclosure-mode and approval-receipt models for operator overlays

Next-Gen FMIE Surfaces Frontend Should Expect

When backend begins exposing them, frontend should plan surfaces for:

• summary.sensitivity_tags.json
• sensitivity labels by span/region/entity
• summary.disclosure_transforms.json
• transform availability and disclosure mode summaries
• summary.document_need_vectors.json
• richer document-derived partner-fit and need views
• summary.claim_blocks.json
• claim/action/decision/blocker/deadline cards with anchors
• summary.authenticity_regions.json
• region-level authenticity indicators
• summary.lineage_graph.json
• provenance chain detail and evidence lineage
• summary.challenge_bundle.json
• proof/challenge availability state
• summary.abstract_packets.json
• operator-only disclosure and external-cognition traces

Recommended UI Evolution

Reuse Existing Views First

Do not build entirely new primitives unless backend state requires it.

Existing views can absorb most of the next-gen artifacts:

• MediaPassportTrustPanel can absorb challenge bundle, disclosure transform, and lineage availability
• ProvenanceChainView can absorb lineage graph and transform history
• PartnerFitReadinessView can absorb document need vectors and claim-block summaries
• MeetingIntelligenceView can absorb claim blocks and richer anchors
• FMIEHealthDashboard can absorb runtime events and structured degradation state
• DisclosureApprovalView can absorb disclosure transforms and receipt states

Add New Dedicated Views Only If Needed

Likely future dedicated additions:

• DisclosureTransformInspector
• ClaimBlockExplorer
• AuthenticityRegionOverlay
• ChallengeBundlePanel

Canonical References

• Frontend Handoff
• Backend Handoff
• Consolidated Handoff
• FMIE Next-Gen v2 Spec
• Partner-Fit Engine Spec
• Strategy Twin Spec