Intersection
Look through the closet — MI surfaces trends as outfits. Select one to see what connects.
Trends MI made from your data
Flip through outfits — each one is a pattern across 360s, SharePoint, and Automate. Click a trend or a hanger to see the family.
Outfit
Maps to GET /v1/intersection/themes proposed — trend clusters + member UMO ids
Maps to POST /v1/memories/query hanger click → related memories
Home
Find records or get an answer — same memories underneath.
Ranked UMOs with scores and receipts.
Maps to POST /v1/memories/query · POST /v1/ask
Answer
Activity
Intersection
Browse before you query.
UMOs
All records in one shape — searchable, readable, provable.
Sources
What feeds this workspace. Connectors run in the background.
Data in
Maps to POST /v1/process via Automate HTTP
LLM
Optional — your model policy for answers.
Wear
Same SPACE — different customer skin.
Story mode is for demos and buyers — not what operators see every day. Switch back to Product tabs on the left for the real app shell.
What you pay for
No maintenance. No pivot tables. No “export and reconcile.”
UMOs — Unified Memory Objects you can read, search, and prove. Different systems in; one human-readable object out, with receipt-style trust (pills on every card).
Intersection (closet + outfits)
Operators browse a closet of UMOs on hangers. MI surfaces outfits — trend families (Communication, Leadership watch list, September policy, hiring). Flip the carousel, click a hanger, see what connects; open the full family on UMOs.
Sources vs LLM
- Sources = where data enters (SharePoint, Automate, forms).
- MI = normalize into UMOs — the filter, not the connector.
- LLM = optional layer; MI supplies memories, you pick the model.
Wear
One component tree — D5 HR, Lincoln school, default MI branding. Operators don’t see “dev portal.”
Engineering map — toggle Dev notes on any product screen to see API mapping under each component.