Foundation-V2 FMIE Full Sweep

Version: v0.1 Status: Review Owners: FMIE / Foundation / Cortex / Frontend Last Updated: 2026-03-26 Change Type: additive Migration Required: yes Depends On: foundation-v2-fmie-integration-audit-2026-03-26.md, fmie-gap-audit-2026-03-25.md Supersedes: none Superseded By: none

Bottom Line

No: Foundation-V2 does not have all FMIE features implemented.

It has strong production use of FMIE for: - local extraction via process_document() - core meeting signal capture - passport validation - Scout-side batch wrappers

But large FMIE capability families remain only partially consumed, wrapped-only, or entirely unused: - partner-fit helper artifacts - clip / highlight workflows - runtime / health / telemetry contracts - matcher / identity APIs - session / live ingest / sync-group APIs - cross-camera continuity - deeper passport proof-material anchoring

Coverage By Capability Family

Capability Family	Status	Read
Document extraction	IMPLEMENTED	Haystack ingest uses `process_document()` and captures text/pages/tables/charts/entities
Meeting signals	IMPLEMENTED	meeting signal arrays are captured and passed through ingest
Audio ASR routing	IMPLEMENTED	auto language + translation + speaker tracking are used
Image/OCR extraction	IMPLEMENTED	implicit through `process_document()`
Media Passport validation	PARTIAL	validation is live, but full proof-material anchoring is not
Authenticity / manipulation scores	PARTIAL	top-level scores are captured; detailed sub-signals are mostly ignored
Partner-fit artifacts	WRAPPED ONLY	wrappers exist; runtime consumption is not wired end-to-end
Clip extraction / highlights	WRAPPED ONLY	code exists; no clear product workflow uses it end-to-end
Document regions	WRAPPED ONLY	parser exists; no production caller found
Entity matcher / identity APIs	WRAPPED ONLY	native wrapper exists; no production caller found
Runtime status / health / telemetry	NOT IMPLEMENTED	no consumer found
Progress / phase callbacks	NOT IMPLEMENTED	no consumer found
Library info / capabilities / build profile	NOT IMPLEMENTED	no consumer found
Live ingest / session APIs	NOT IMPLEMENTED	no consumer found
Session linking / sync groups	NOT IMPLEMENTED	no consumer found
Cross-camera continuity	NOT IMPLEMENTED	no consumer found
Enricher plugin registration	NOT IMPLEMENTED	no consumer found
Strategy Twin inputs from FMIE	NOT IMPLEMENTED	Strategy Twin not yet built

What Is Truly End-To-End Today

1. Ingest path

Haystack ingests PDFs, PPTX, DOCX, images, audio, and video through FMIE local extraction.
Transcript, tables, charts, pages, meeting signals, and top-level authenticity fields make it into Foundation ingest structures.

2. Passport validation path

Foundation can parse and validate summary.passport.json.
Native FMIE verification is called when the shared library is available.

3. Scout wrapper layer

Scout Fleet has a real FMIE wrapper with text extraction, structured extraction, transcription, batch processing, clip extraction, and helper-artifact readers.

What Is Only Partially There

1. Media Passport to Midnight path

Foundation validates the passport.
Foundation does not yet anchor the full FMIE proof-material set.
request/response receipt commitments are still weaker than the locked Midnight model expects.

2. Meeting and partner-fit path

meeting signals are captured
helper artifacts now exist in FMIE and Scout-side readers exist
but higher-order consumption still does not drive partner-fit or strategy state in production

3. Authenticity path

top-level scores are captured
detailed explanations, proof blocks, and UI/operator uses are still thin

What Is Present But Dormant

Document regions

services/haystack-pipeline/src/haystack_pipeline/document_regions.py
good local parser, no production call path found

Entity matcher

services/haystack-pipeline/src/haystack_pipeline/entity_matcher.py
FMIE matcher/index family is wrapped, no production usage found

Scout FMIE enrichment

services/scout-fleet/src/scout_fleet/fmie_enrichment.py
reads partner-fit inputs, meeting need vectors, highlights, passport, evidence
no production call path found in Scout runtime

Clip extraction

services/haystack-pipeline/src/haystack_pipeline/clip_extractor.py
works as a wrapper/fallback module
no clear product or API path using it end-to-end was found in the sweep

Highest-Value Missing Implementations

P0

full FMIE passport proof-material anchoring into Midnight
full-length receipt commitments
universal Gateway routing for sensitive external-model calls
production consumption of summary.partner_fit_inputs.json and summary.meeting_need_vectors.json

P1

runtime status / health / telemetry integration for Cortex
document region integration into ingest and retrieval payloads
matcher/index integration for cross-asset identity continuity
clip/highlight consumption in actual UX or APIs

P2

live session APIs
sync groups and cross-camera continuity
plugin/enricher extensions
build/runtime capability surfaces

Practical Answer To "Are All FMIE Features Implemented?"

If "implemented" means "exists somewhere in Foundation-V2 code", the answer is: many are wrapped.

If "implemented" means "wired through a real production path and actually consumed", the answer is: no.

Foundation-V2 currently has: - strong FMIE extraction integration - partial passport/trust integration - broad but mostly dormant advanced FMIE wrappers

Recommended Closure Order

trust-path correctness
partner-fit helper artifact consumption
runtime / health observability
document regions and matcher activation
clip/highlight workflows
live/session/cross-camera features