Glossary
Aiffinities
The compatibility signal between two Individual Prints, used to suggest meetups, introductions, and shared moments.
An Aiffinity is a composite score produced by comparing two Individual Prints — overlap in values, interests, preferences, and day-to-day routines. Aiffinities power opt-in introductions, shared playlists, and the "you should reach out" nudges Aiven surfaces in Relationships. Scores are always read-only and never shared without the consent of both users.
AI Agent
A goal-directed model loop that can read, plan, and act across the user's connected apps with approval gates.
An AI Agent in Aiffinity is a constrained, tool-using model loop that takes a goal from the user and executes steps across connected apps — data fetches, drafts, writes. Every side-effect that changes the outside world (sending a message, booking a slot, creating an issue) pauses for a single-tap approval. Agents inherit the user's Individual Print for tone and preferences, and run inside scopes the user has explicitly granted.
Aiven
Each Aiffinity user's personal AI — adaptive, voice-consistent, and wired to the apps they already use.
Aiven is the name of every user's personal AI inside Aiffinity. Aiven reads from the user's Individual Print, draws on the connected Providers the user has approved, and acts through capabilities the user has authorised. No two Aivens are the same — each one is shaped by the specific person's signals over time. Aiven replies, drafts, schedules, and quietly tidies context so the user doesn't have to.
Capability Package
A reviewed bundle of Data, Action, State, and Event contracts that extends what Aiven can do.
A Capability Package is how third-party builders plug into Aiffinity. Each package declares four surfaces:
- Data — inbound reads that contribute signals to the Individual Print.
- Action — outbound writes Aiven can invoke with user approval.
- State — long-lived context the capability keeps on the user's behalf.
- Event — webhook-style pushes that wake Aiven when something relevant happens.
Every package goes through review before publication, and users grant or revoke scopes individually. See Capability Model for the developer contract.
Hot Replies
Aiven-drafted reply options that already sound like the user — one-tap sends, zero "AI voice".
Hot Replies are quick, one-tap replies generated by Aiven in the flow of a chat. They aren't generic — each reply is grounded in the user's Individual Print and the relationship context, so the draft feels authentic enough to send without editing. Users can tap send, tap edit, or regenerate.
Hot Takes
A social micro-game whose reactions feed structured personalization signals into the Individual Print.
Hot Takes are crowd-sourced opinions users react to inside Aiffinity. The reactions are light entertainment on the surface, but under the hood they become structured signals the Individual Print absorbs — effectively a game-shaped calibration loop for personalization signals, values, and humour.
Individual Print (IP)
A portable personalization profile grounded in Aiffinity, exportable anywhere.
The Individual Print (IP) is the canonical record of who a user is, structured enough for machines to act on. It layers profile signals and preference context used for personalization. The IP is portable: a user can export it or grant scoped access to compatible apps via IP Grants, so every new AI starts with relevant context. Users can delete the IP at any time.
IP Grant
A scoped, revocable permission for a third-party app to read part of the user's Individual Print.
An IP Grant is how a user lets an external app personalise to them without handing over raw data. The grant is OAuth-based, the scope is explicit (e.g. "tone and values, no calendar"), and the user can revoke it any time from Aiffinity. Granted apps get short-lived access tokens and receive webhook notifications when the user's IP updates.
Model Context Protocol (MCP)
An open standard for exposing tools, resources, and prompts to language models — how Aiffinity stays model-agnostic.
The Model Context Protocol (MCP) is an open, JSON-RPC–based protocol for exposing tools, resources, and prompts to language models. Aiffinity uses MCP internally so Aiven's tool surface is portable across model providers, and externally so other AI clients can ground on a user-granted slice of their Individual Print.
Profile Signals
Internal, high-level indicators used for personalization.
Profile Signals are internal indicators derived from product usage and approved integrations. They help Aiven personalize responses and actions. Detailed model dimensions and scoring internals are intentionally not exposed in the app or website UI.
Persona
A named variant of Aiven — work, casual, rehearsal — that scopes which parts of the IP are active.
A Persona is a user-authored variant of Aiven. Each persona selects which slices of the Individual Print are in scope — a "work" persona may silence humour and casual style; a "rehearsal" persona may sandbox outbound actions to drafts only. Personas are a safety and tone tool: the same Aiven, explicit about which version of the user is speaking right now.
Provider
An external app connected to Aiffinity that contributes signals inbound and/or executes actions outbound.
A Provider is an external app (Gmail, Notion, Strava, Slack, etc.) connected to an Aiffinity account. Providers contribute inbound signal to the Individual Print and/or accept outbound actions drafted by Aiven. Every provider connection is scoped, encrypted, and revocable. The full catalogue lives on Integrations.
Space
Aiffinity's AI-native app surface — composable widgets Aiven assembles around what the user is doing.
Space is Aiffinity's composable app surface. Instead of static screens, Aiven builds context-aware layouts from widgets emitted by capability packages. Space reflects what the user is actually doing — a travel plan, a project kickoff, a shared playlist — and dissolves when it's no longer relevant.
Widget
The first-party UI primitive a capability emits — a chart, list, form, or action button Aiven can compose.
A Widget is the rendered, interactive unit of a capability — a chart, list, form, action button, or media preview — specified by a capability package and rendered by first-party Aiffinity code so designs stay consistent and safe. Widgets are the building blocks of Space and inline Aiven replies.