Frontend FMIE Integration Handoff

Version: v0.1 Status: Ready Owners: Triton Front-end / Backend contract consumers Last Updated: 2026-03-26 Change Type: additive Migration Required: yes Depends On: foundation-v2-fmie-integration-audit-2026-03-26.md, Media Passport spec, Partner-Fit spec, Strategy Twin spec Supersedes: none Superseded By: none

Purpose

This handoff tells the Triton Front-end session which FMIE-backed surfaces are now stable enough to render, and which backend contracts it should insist on from Cortex/Foundation instead of accepting ad hoc fields.

Per house rules: - Triton Front-end owns Swift implementation - Cortex owns Python/backend changes - Codex/FMIE owns native runtime and artifact contracts

P0 UI Work

1. Media Passport trust panel

Frontend should render a stable trust/provenance card whenever passport data is present.

Contract sources: - summary.passport.json - backend passport validation result from cognition_gateway/passport.py

Render: - passport valid / invalid - native verification status - disclosure capabilities - partner-fit readiness - authenticity / deepfake summary - transform / proof availability

2. Partner-fit readiness surface

Frontend should surface FMIE readiness before any partner-fit flow starts.

Contract sources: - summary.json.partner_fit - summary.passport.json.partner_fit - summary.partner_fit_inputs.json - summary.meeting_need_vectors.json

Render: - ready / not ready - meeting signal count - meeting need vector count - document cue count - linked helper artifact availability

3. Meeting intelligence UX

Frontend should stop treating FMIE meeting output as plain transcript text only.

Contract sources: - meeting_signals - transcript[] - transcript quality assessment - highlights manifest

Render: - action items - decisions - blockers - deadlines - confidence / quality hints - jump-to-highlight playback when clip paths exist

4. Document intelligence UX

Frontend should render richer document results when the backend exposes them.

Contract sources: - pages[] - tables[] - charts[] - document regions / anchors

Render: - page/slide structure - detected tables and charts - anchored region overlays or structured summaries - explicit encrypted/scanned-PDF warnings when present

P1 UI Work

5. Clip and highlight UX

Contract sources: - summary.highlights.json - direct clip extraction paths from backend - thumbnail base URLs where available

Render: - top highlights - clip previews - deterministic share/playback windows

6. Authenticity and provenance UX

Contract sources: - authenticity_score - deepfake_score - passport authenticity block - manipulation details when backend exposes them

Render: - suspicion / authenticity labels - concise explanation of what raised the score - never overstate certainty beyond backend trust labels

7. Runtime / operator surfaces

Once Cortex exposes runtime and health status, frontend should render: - FMIE runtime ready / degraded / unavailable - last crash breadcrumb summary - model/cache health summary - queue/backpressure warning states for operations views

Frontend Dependency Rules

Frontend should ask Cortex/Foundation for explicit stable contracts, not infer them by scraping random JSON blobs.

Insist on backend endpoints or response fields for: - passport validation result - partner-fit readiness summary - meeting summary model - clip/highlight references - authenticity summary model - runtime / health summary model

What Frontend Should Not Do

• do not parse raw FMIE sidecar files directly from the client
• do not infer disclosure policy or trust state from low-level hashes
• do not claim content was safely transformed unless backend receipts and trust state say so
• do not treat raw FMIE scores as user-facing final truth without backend labels

Success Criteria

This handoff is complete when Triton can show: - a trustworthy Media Passport panel - partner-fit readiness without guessing - meeting/document intelligence beyond plain text blobs - clip/highlight playback on top of backend-provided paths - operational FMIE status in admin/operator contexts