[{"data":1,"prerenderedAt":1364},["ShallowReactive",2],{"search":3,"content-guide\u002Fknowledge-graph":442,"surround-\u002Fguide\u002Fknowledge-graph":1359},[4,8,12,16,20,24,28,32,36,40,44,48,52,56,60,64,68,72,76,80,84,88,92,96,100,104,108,112,116,120,124,128,132,136,140,144,148,152,156,160,164,168,172,176,180,184,188,192,196,200,204,208,212,216,220,224,228,232,236,240,244,248,252,256,260,264,268,272,276,280,284,288,292,296,300,304,308,312,316,320,323,327,331,335,339,343,347,351,355,359,363,367,371,375,379,383,387,391,395,399,403,407,411,415,419,423,426,430,434,438],{"path":5,"title":6,"description":7},"\u002Fguide","Guide","Product guides for Owlat — a modular, self-hosted email platform. Learn how to send campaigns, run a personal mailbox, manage a team inbox, and more.",{"path":9,"title":10,"description":11},"\u002Fguide\u002Fgetting-started","Welcome to Owlat","Set up your Owlat workspace and send your first email — from deploying the stack to verifying a domain, building your audience, and launching a campaign.",{"path":13,"title":14,"description":15},"\u002Fguide\u002Fcontact-properties","Contact Properties","Custom fields that extend built-in contact data with your own values for segmentation.",{"path":17,"title":18,"description":19},"\u002Fguide\u002Ftopics","Topics","Topics are explicit audience groups you manage by hand — ideal for opt-in subscribers, imported cohorts, and organized contact buckets you target with campaigns.",{"path":21,"title":22,"description":23},"\u002Fguide\u002Fsegments","Segments","Build dynamic, rule-based contact groups from properties, email activity, and topic membership, re-evaluated from current data each time they're used.",{"path":25,"title":26,"description":27},"\u002Fguide\u002Fforms","Forms","Form Endpoints collect new contacts from your website or landing pages by exposing a public endpoint that accepts submissions and feeds them into a topic.",{"path":29,"title":30,"description":31},"\u002Fguide\u002Fcampaigns","Campaigns & Reporting","Build and send marketing campaigns to a topic or segment with the five-step wizard, optional A\u002FB testing, and full delivery reporting.",{"path":33,"title":34,"description":35},"\u002Fguide\u002Fab-testing","A\u002FB Testing","Compare two variants of a campaign on a test group, then automatically or manually send the winning version to the rest of your audience.",{"path":37,"title":38,"description":39},"\u002Fguide\u002Fautomations","Automations","Send emails automatically based on triggers, delays, and conditions — build welcome series, trial flows, and follow-ups once and let Owlat run them.",{"path":41,"title":42,"description":43},"\u002Fguide\u002Ftransactional","Transactional Emails","One-to-one emails your application triggers in response to a user action — password resets, order confirmations, welcome emails, and similar notifications.",{"path":45,"title":46,"description":47},"\u002Fguide\u002Fcreate-campaign","Create a Campaign","Walk through Owlat's five-step campaign wizard: Basics, Audience, Content, A\u002FB Test, and Review & Send.",{"path":49,"title":50,"description":51},"\u002Fguide\u002Fsend-campaign","Send & Monitor a Campaign","How to send your campaign and track its performance with real-time metrics.",{"path":53,"title":54,"description":55},"\u002Fguide\u002Fquick-start","Quick Start","The fastest path from a blank Owlat workspace to a live email campaign, from your first template through sending and reviewing results.",{"path":57,"title":58,"description":59},"\u002Fguide\u002Ftransactional-setup","Transactional Email Setup","Set up and send transactional emails like password resets and order confirmations via the Owlat API and SDKs.",{"path":61,"title":62,"description":63},"\u002Fguide\u002Fdeliverability","Deliverability","Verify sending domains, manage your blocklist, monitor sending reputation, and stay compliant so your emails reach the inbox.",{"path":65,"title":66,"description":67},"\u002Fguide\u002Fapi-keys-webhooks","API Keys & Webhooks","Create API keys for programmatic access and set up outbound webhooks to receive real-time notifications for email and contact events.",{"path":69,"title":70,"description":71},"\u002Fguide\u002Ffeature-flags","Feature flags","Owlat is modular — every feature listed in this guide can be turned on or off. This page is the user-facing overview of how to do it.",{"path":73,"title":74,"description":75},"\u002Fguide\u002Fteam-permissions","Team & Permissions","Use role-based access to control what each member of your organization can do, with Owner, Admin, and Editor roles.",{"path":77,"title":78,"description":79},"\u002Fguide\u002Faudit-logs","Audit Logs","A chronological record of significant actions in your Owlat organization, so you can see who did what and when.",{"path":81,"title":82,"description":83},"\u002Fguide\u002Fshare-links","Share Links","Create temporary preview links to share email designs with stakeholders who don't have dashboard access.",{"path":85,"title":86,"description":87},"\u002Fguide\u002Fpostbox","Postbox — Personal Email","Per-user mailboxes with a webmail interface and native IMAP\u002FSMTP support. Run your own Gmail-equivalent personal mailbox on your Owlat instance.",{"path":89,"title":90,"description":91},"\u002Fguide\u002Fmigrate-from-google","Migrate from Google","Import your full Gmail history into Owlat over IMAP, and let your AI assistant learn from every imported conversation.",{"path":93,"title":94,"description":95},"\u002Fguide\u002Fteam-inbox","Team Inbox","Triage inbound email as a team: read AI-classified threads, approve, edit or reject agent drafts, work the review queue, and manage quarantine.",{"path":97,"title":98,"description":99},"\u002Fguide\u002Femail-editor","Email Editor","A block-based visual editor for building responsive emails that render consistently across desktop, mobile, Outlook, Gmail, and Apple Mail.",{"path":101,"title":102,"description":103},"\u002Fguide\u002Fai-agent","AI Agent & Autonomy","Configure the AI agent that classifies and drafts replies to inbound mail: auto-reply settings, the health dashboard, circuit breakers, autonomy rules, and the knowledge backfill.",{"path":105,"title":106,"description":107},"\u002Fguide\u002Fknowledge-graph","Knowledge Graph","Browse, search, and manage Owlat's typed organizational knowledge — the 7 entry types, source attribution, confidence decay, relations, and how entries are extracted from mail.",{"path":109,"title":110,"description":111},"\u002Fguide\u002Ffiles","Files","Upload, browse, search, tag, and version documents in the file library.",{"path":113,"title":114,"description":115},"\u002Fguide\u002Fchat","Team Chat","Use Owlat's built-in team chat: public and private channels, direct messages, mentions, attachments, and channels linked to an inbox conversation.",{"path":117,"title":118,"description":119},"\u002Fguide\u002Fcode-tasks","Code Tasks","Queue coding-agent tasks, watch them move from queued through review, and run the code-worker sidecar that opens the pull requests.",{"path":121,"title":122,"description":123},"\u002Fguide\u002Faudience-data","Audience Data: Identities, Relationships & Timeline","Unify a contact across email, phone, and messaging channels, merge duplicates, map relationships, and read the cross-channel interaction timeline.",{"path":125,"title":126,"description":127},"\u002Fguide\u002Fimporting-contacts","Importing & Exporting Contacts","Bring contacts into Owlat from a CSV or from Mailchimp and Stripe, export them back out, and run bulk operations on your audience.",{"path":129,"title":130,"description":131},"\u002Fguide\u002Faccount","Your Account & Data","Export your data as JSON or CSV, request account deletion with a 30-day grace period, and use the onboarding checklist and the public preference center.",{"path":133,"title":134,"description":135},"\u002Fguide\u002Fchannels","Communication Channels","Configure SMS, WhatsApp, and generic-webhook channels, monitor channel health, and understand which channels are fully live today.",{"path":137,"title":138,"description":139},"\u002Fguide\u002Fdesktop-app","Desktop App","Install the Owlat desktop app, connect one or more workspaces, switch between them, and use native notifications, tray badges, shortcuts, and deep links.",{"path":141,"title":142,"description":143},"\u002Fguide\u002Femail-templates","Email Templates","Reusable email designs that define the structure, content, and personalization of every campaign and transactional message you send in Owlat.",{"path":145,"title":146,"description":147},"\u002Fguide\u002Fai-assistant","AI Assistant","Owlat's multi-turn, streaming, tool-calling AI assistant — a private chat surface that can search your workspace and draft copy, plus @assistant replies inside team chat.",{"path":149,"title":150,"description":151},"\u002Fguide\u002Fsecurity-scanning","Sending Security & Scanning","Owlat's security scanning: a content check for spam and phishing, an attachment scan for malware, and a Google Safe Browsing URL check. Suspicious content goes to a review queue.",{"path":153,"title":154,"description":155},"\u002Fguide\u002Fsystem-updates","System & Updates","The owner-only System & Updates screen: your current Owlat version, container health, LLM spend, and the in-app one-click updater with history.",{"path":157,"title":158,"description":159},"\u002Fguide\u002Foperating-modes","Operating Modes","The different ways to run Owlat at a company — read external mailboxes over IMAP, send transactional or marketing email through a delivery provider, host your own mail server, or run a team inbox with AI — and the rules that keep each combination coherent.",{"path":161,"title":162,"description":163},"\u002Fguide\u002Fsaved-blocks","Saved Blocks","Create reusable, linked content blocks you can drop into any email — edit one and every email that uses it updates automatically.",{"path":165,"title":166,"description":167},"\u002Fguide\u002Fmedia-library","Media Library","Manage, organize, search, and reuse images and files across your emails from one centralized hub.",{"path":169,"title":170,"description":171},"\u002Fguide\u002Femail-theme","Email Theme","Set your organization's default colors, font, and email width so every new template starts from a consistent baseline.",{"path":173,"title":174,"description":175},"\u002Fguide\u002Ftranslations","Translations","Send one email in multiple languages: add per-language translations to a single template and Owlat picks the right version for each recipient.",{"path":177,"title":178,"description":179},"\u002Fguide\u002Fcontacts","Contacts","How to add, view, organize, and manage contacts in Owlat, including sources, the contact detail tabs, and subscription compliance.",{"path":181,"title":182,"description":183},"\u002Fapi","API Overview","Owlat exposes authenticated API endpoints under your Convex site URL.",{"path":185,"title":186,"description":187},"\u002Fapi\u002Fwebhooks","Webhooks","Owlat supports both outbound customer webhooks and inbound provider webhooks.",{"path":189,"title":190,"description":191},"\u002Fapi\u002Fpublic-endpoints","Public Endpoints","These routes are public-facing and usually accessed from email links or embedded forms.",{"path":193,"title":194,"description":195},"\u002Fapi\u002Fwebhook-payloads","Webhook Payloads","The authoritative wire contract for outbound webhooks: envelope, signature headers, per-event data shapes, and payload versioning.",{"path":197,"title":198,"description":199},"\u002Fapi\u002Finbound-channels","Inbound Channel Webhooks","Provider webhook reference for inbound SMS, WhatsApp, and generic-channel messages, plus the MTA mailbox and credential callbacks.",{"path":201,"title":202,"description":203},"\u002Fapi\u002Fauthentication","Authentication","Secure API access with organization-scoped API keys.",{"path":205,"title":206,"description":207},"\u002Fapi\u002Fsdk","TypeScript SDK","Typed client for the Owlat API, usable from Node.js, Bun, Deno, or any server-side JavaScript runtime.",{"path":209,"title":210,"description":211},"\u002Fapi\u002Fsdk-java","Java SDK","The official `owlat-sdk` package provides a typed client for interacting with the Owlat API from any JVM application. Requires Java 11+.",{"path":213,"title":214,"description":215},"\u002Fapi\u002Fcontacts","Contacts API","Manage contacts for your organization.",{"path":217,"title":218,"description":219},"\u002Fapi\u002Ftopics","Topics API","Manage topic membership through authenticated endpoints.",{"path":221,"title":222,"description":223},"\u002Fapi\u002Fevents","Events API","Send contact events to drive segmentation and automation triggers.",{"path":225,"title":226,"description":227},"\u002Fapi\u002Ftransactional","Transactional API","Send published transactional templates to a recipient.",{"path":229,"title":230,"description":231},"\u002Fapi\u002Fforms","Forms API","Capture subscribers through public form endpoints.",{"path":233,"title":234,"description":235},"\u002Fdeveloper","Developer Guide","Technical architecture, feature-flag model, and provider abstractions used by Owlat.",{"path":237,"title":238,"description":239},"\u002Fdeveloper\u002Fmta-system","MTA System","Owlat's custom Mail Transfer Agent for direct SMTP delivery with intelligent rate limiting, bounce processing, and IP warming.",{"path":241,"title":242,"description":243},"\u002Fdeveloper\u002Ffeature-flags","Feature flags — developer reference","How the Owlat feature flag system works: single source of truth, dependency resolution, docker profile mapping, and how to add a new flag.",{"path":245,"title":246,"description":247},"\u002Fdeveloper\u002Fhow-email-works","How Email Works","A technical deep-dive into how email actually works — from SMTP and DNS to authentication, deliverability, and the differences between marketing and private email.",{"path":249,"title":250,"description":251},"\u002Fdeveloper\u002Femail-security","Email Security","Content scanning, attachment validation, URL reputation checking, and malware detection for outbound emails.",{"path":253,"title":254,"description":255},"\u002Fdeveloper\u002Fpostbox-architecture","Postbox Architecture","How the Postbox personal-mail feature is wired — schema, IMAP server, app-password auth, outbound relay, inbound delivery, and external mailboxes.",{"path":257,"title":258,"description":259},"\u002Fdeveloper\u002Fproviders","Providers","Pluggable provider abstractions for LLM, email sending, notifications, vector stores, and analytics, selected per-deployment so self-hosters can swap implementations without code changes.",{"path":261,"title":262,"description":263},"\u002Fdeveloper\u002Fcampaign-internals","Campaign Internals","How the campaign backend works: two status machines, send pre-flight, the send orchestrator, emailSends records, and the priority workpools.",{"path":265,"title":266,"description":267},"\u002Fdeveloper\u002Faudience-internals","Audience Internals","Backend reference for contact resolution, the double opt-in lifecycle, topic subscription, the conditions registry, and segment evaluation.",{"path":269,"title":270,"description":271},"\u002Fdeveloper\u002Fautomation-internals","Automation Internals","How the automation run engine works: the step walker, the lifecycle state machine, trigger fanout, the three step types, and the resilience cron.",{"path":273,"title":274,"description":275},"\u002Fdeveloper\u002Fdeliverability-infrastructure","Deliverability Infrastructure","The Convex-side deliverability backend: provider routing, health-aware failover, sending reputation with auto-enforcement, IP warming cache, the blocklist, and the content-scan gate.",{"path":277,"title":278,"description":279},"\u002Fdeveloper\u002Farchitecture","Architecture Overview","Owlat follows a modern serverless architecture with real-time capabilities.",{"path":281,"title":282,"description":283},"\u002Fdeveloper\u002Fplatform-operations","Platform Operations","Operator reference for abuse status and the sending gate, the platform-admin roster, content review, org deletion, in-app self-update, dev endpoints, crons, and migrations.",{"path":285,"title":286,"description":287},"\u002Fdeveloper\u002Fscopes","Scopes","What each app and package in the Owlat monorepo is responsible for.",{"path":289,"title":290,"description":291},"\u002Fdeveloper\u002Fself-hosting","Self-Hosting","Deploy Owlat on your own infrastructure with Docker Compose. Complete guide from first boot to production.",{"path":293,"title":294,"description":295},"\u002Fdeveloper\u002Fself-hosting-config","Self-Hosting Configuration","Complete reference for Docker environment variables, Convex backend variables, service topology, and volume persistence.",{"path":297,"title":298,"description":299},"\u002Fdeveloper\u002Fself-hosting-dns-email","DNS & Email Setup","Configure DNS records, DKIM signing, SPF, DMARC, and bounce handling for reliable email delivery.",{"path":301,"title":302,"description":303},"\u002Fdeveloper\u002Fself-hosting-production","Production Deployment","Secure your self-hosted Owlat instance with TLS, firewall rules, backups, and monitoring.",{"path":305,"title":306,"description":307},"\u002Fdeveloper\u002Fself-hosting-maintenance","Maintenance & Updates","Keep your self-hosted Owlat instance up to date, manage backups, scale performance, and troubleshoot common issues.",{"path":309,"title":310,"description":311},"\u002Fdeveloper\u002Fself-hosting-desktop","Desktop Installer","Install Owlat on a bare Linux VPS straight from the desktop app over SSH — no terminal — with a live, animated provisioning timeline.",{"path":313,"title":314,"description":315},"\u002Fdeveloper\u002Fsetup-cli","Setup CLI & Installer","Operator reference for the Owlat self-host tooling: the install.sh one-liner, the owlat-setup CLI, the convex-deploy flow, and admin bootstrap.",{"path":317,"title":318,"description":319},"\u002Fdeveloper\u002Fconvex","Convex Backend","Owlat uses Convex as its serverless backend, providing real-time subscriptions, ACID transactions, and TypeScript-first development.",{"path":321,"title":202,"description":322},"\u002Fdeveloper\u002Fauthentication","Owlat uses BetterAuth with the Convex adapter for authentication and organization (team) management.",{"path":324,"title":325,"description":326},"\u002Fdeveloper\u002Femail-system","Email System","Owlat's email system consists of a visual editor, template management, and multi-provider sending infrastructure.",{"path":328,"title":329,"description":330},"\u002Fdeveloper\u002Femail-renderer","Email Renderer","The @owlat\u002Femail-renderer package converts editor JSON blocks into production-ready HTML emails with cross-client compatibility, CSS inlining, dark mode, and Outlook VML fallbacks.",{"path":332,"title":333,"description":334},"\u002Fdeveloper\u002Fenvironment-variables","Environment Variables","Reference for every environment variable Owlat reads across the Convex backend, web app, MTA, IMAP server, and mail-sync worker.",{"path":336,"title":337,"description":338},"\u002Fdeveloper\u002Fcomponents","Component Library","Reference for the reusable, auto-imported Vue UI components shipped in the packages\u002Fui layer.",{"path":340,"title":341,"description":342},"\u002Fdeveloper\u002Fdecisions","Architectural Decision Records","The architectural decision records for the Owlat project, each capturing the context, the decision, and the trade-offs involved.",{"path":344,"title":345,"description":346},"\u002Fdeveloper\u002Fdecisions\u002F009-model-routing","ADR-009: Task-Based Model Routing","Why Owlat supports per-task LLM model selection instead of using a single model for all pipeline steps.",{"path":348,"title":349,"description":350},"\u002Fdeveloper\u002Fdecisions\u002F010-listing-engine","ADR-010: Listing Engine","Why Owlat replaced four incompatible list-query contracts with one generic listing engine driven by per-entity descriptors.",{"path":352,"title":353,"description":354},"\u002Fdeveloper\u002Fdecisions\u002F001-custom-email-renderer","ADR-001: Custom Email Renderer Over MJML","Why Owlat built a custom table-based HTML email renderer instead of using MJML, gaining full control over VML, dark mode, and per-client rendering.",{"path":356,"title":357,"description":358},"\u002Fdeveloper\u002Fdecisions\u002F002-convex-backend","ADR-002: Convex as Backend","Why Owlat chose Convex over PostgreSQL and Firebase for real-time reactivity, co-located TypeScript logic, and zero-config scaling.",{"path":360,"title":361,"description":362},"\u002Fdeveloper\u002Fdecisions\u002F003-notion-like-builder","ADR-003: Notion-like Email Builder","Why Owlat replaced the traditional 3-panel email editor with a Notion-like single-column canvas for inline WYSIWYG editing.",{"path":364,"title":365,"description":366},"\u002Fdeveloper\u002Fdecisions\u002F004-monorepo-bun-workspaces","ADR-004: Monorepo with Bun Workspaces","Why Owlat uses a monorepo with Bun workspaces and Turborepo for fast installs, atomic cross-package changes, and cached CI.",{"path":368,"title":369,"description":370},"\u002Fdeveloper\u002Fdecisions\u002F005-custom-mta","ADR-005: Custom MTA","Why Owlat built a custom Mail Transfer Agent instead of relying solely on third-party email providers.",{"path":372,"title":373,"description":374},"\u002Fdeveloper\u002Fdecisions\u002F006-self-hosted-convex","ADR-006: Self-Hosted Convex","Why Owlat uses the open-source Convex backend for self-hosting instead of migrating to a different database.",{"path":376,"title":377,"description":378},"\u002Fdeveloper\u002Fdecisions\u002F007-pluggable-llm","ADR-007: Pluggable LLM Provider","Why Owlat uses the Vercel AI SDK with a provider abstraction layer instead of hardcoding a single LLM vendor.",{"path":380,"title":381,"description":382},"\u002Fdeveloper\u002Fdecisions\u002F008-process-architecture","ADR-008: Agent Process Architecture","Why Owlat processes inbound messages with a self-scheduling step walker plus a lifecycle coordinator instead of one sequential function.",{"path":384,"title":385,"description":386},"\u002Fexamples","Examples","Copy-pasteable integration patterns for common Owlat use cases.",{"path":388,"title":389,"description":390},"\u002Fexamples\u002Fwelcome-email","Welcome Email","Send a personalized welcome email when a new user signs up.",{"path":392,"title":393,"description":394},"\u002Fexamples\u002Fbilling-email","Billing Email","Send a billing receipt with an invoice PDF attached after a successful payment.",{"path":396,"title":397,"description":398},"\u002Fexamples\u002Fevent-automation","Event Automation","Trigger automations with custom events for trial lifecycle, feature adoption, and more.",{"path":400,"title":401,"description":402},"\u002Fexamples\u002Fcontact-sync","Contact Sync","Sync contacts from your database to Owlat using upsert patterns and bulk operations.",{"path":404,"title":405,"description":406},"\u002Fexamples\u002Fwebhook-handler","Webhook Handler","Handle Owlat delivery webhooks with signature verification and event routing.",{"path":408,"title":409,"description":410},"\u002Fexamples\u002Fmultilingual-email","Multilingual Email","Send emails in the recipient's preferred language using template translations.",{"path":412,"title":413,"description":414},"\u002Fvision","Vision","Where Owlat is heading — from email platform to unified communication intelligence powered by AI agents.",{"path":416,"title":417,"description":418},"\u002Fvision\u002Fself-hosting","Self-Hosting Architecture","How Owlat runs as a fully self-hosted stack using Docker Compose — open-source Convex backend, custom MTA, and a pluggable LLM provider.",{"path":420,"title":421,"description":422},"\u002Fvision\u002Fagent-pipeline","Agent Pipeline","Technical architecture for the inbound email agent pipeline — step modules, the walker, security scanning, threading, and human review.",{"path":424,"title":106,"description":425},"\u002Fvision\u002Fknowledge-graph","Technical architecture for Owlat's typed knowledge storage — how organizational knowledge is stored, searched, decayed, and maintained.",{"path":427,"title":428,"description":429},"\u002Fvision\u002Fmulti-channel","Multi-Channel & CRM","Technical architecture for channel adapters, unified messaging, contact identity unification, and the CRM hub.",{"path":431,"title":432,"description":433},"\u002Fvision\u002Ffile-system","Semantic File System","Technical architecture for Owlat's semantic file storage — version tracking with provenance today, plus the planned embedding-based retrieval and auto-tagging layer.",{"path":435,"title":436,"description":437},"\u002Fvision\u002Fdesktop-app","Desktop App & Advanced Agents","Architecture of the Owlat desktop shell, visualization agent, adaptive dashboard, agent health, graduated autonomy, and coding agents.",{"path":439,"title":440,"description":441},"\u002Fvision\u002Froadmap","Roadmap","What's planned next for Owlat — the documented-but-unbuilt pieces still being wired, and the enhancements on our radar.",{"id":443,"title":106,"body":444,"description":107,"extension":1353,"meta":1354,"navigation":1355,"path":105,"seo":1356,"stem":1357,"__hash__":1358},"content\u002F1.guide\u002F31.knowledge-graph.md",{"type":445,"value":446,"toc":1329},"minimark",[447,451,461,481,497,522,530,534,539,547,661,665,676,740,744,785,789,795,813,820,831,835,846,914,917,921,932,1005,1020,1056,1060,1071,1085,1088,1123,1138,1160,1163,1169,1191,1198,1201,1301,1314,1318,1322,1325],[448,449,450],"p",{},"The Knowledge Graph is Owlat's typed store of organizational knowledge — customer preferences, decisions, commitments, and relationships, captured as searchable entries that the AI agent can draw on. Instead of a write-only log, it's a living set of facts that each carry a confidence score, decay over time, and can be linked to contacts, conversation threads, and one another. You browse and search it from the dashboard, and you can add entries by hand.",[452,453,455,456,460],"h2",{"id":454},"what-the-knowledge-graph-is-and-the-aiknowledge-flag","What the Knowledge Graph is (and the ",[457,458,459],"code",{},"ai.knowledge"," flag)",[448,462,463,464,468,469,472,473,476,477,480],{},"Every entry is a small, typed piece of knowledge: a fact, a decision, an event, a preference, a goal, a relationship, or an action item. Each one records ",[465,466,467],"em",{},"what"," the knowledge is, ",[465,470,471],{},"where"," it came from, ",[465,474,475],{},"how confident"," Owlat is in it, and ",[465,478,479],{},"who or what"," it relates to.",[448,482,483,484,488,489,491,492,496],{},"The graph is both a ",[485,486,487],"strong",{},"browsing and authoring surface"," and a live input to drafting: the ",[485,490,106],{}," page in the dashboard is where you and your team search and review what Owlat knows, and where you add entries by hand. When the ",[493,494,495],"a",{"href":101},"AI agent"," drafts a reply, its context-retrieval step also searches the graph (contact-scoped) and injects the matching entries into the drafting prompt — so knowledge you capture is fed back into the agent's replies today.",[448,498,499,500,503,504,506,507,510,511,514,515,518,519,521],{},"The whole feature sits behind the ",[485,501,502],{},"Knowledge graph"," feature flag (",[457,505,459],{},"), which is ",[485,508,509],{},"off by default"," and depends on the master ",[485,512,513],{},"AI features"," flag (",[457,516,517],{},"ai","). Until an operator enables both, the knowledge search query returns nothing. See ",[493,520,70],{"href":69}," for how to turn them on (you'll need an LLM provider configured, since the backfill extraction and embeddings call your model).",[523,524,527],"callout",{"title":525,"type":526},"One graph per workspace","info",[448,528,529],{},"Owlat runs one organization per deployment, so there is a single knowledge graph for the whole workspace. There's no per-team or per-org partitioning — every entry belongs to this deployment.",[452,531,533],{"id":532},"entry-types-sources-confidence-and-tags","Entry types, sources, confidence and tags",[535,536,538],"h3",{"id":537},"the-seven-entry-types","The seven entry types",[448,540,541,542,546],{},"Each entry has exactly one type. The type controls its icon, its colour in the UI, and — importantly — how fast its confidence decays (see ",[493,543,545],{"href":544},"#confidence-decay-and-expiry","Confidence decay and expiry",").",[548,549,550,566],"table",{},[551,552,553],"thead",{},[554,555,556,560,563],"tr",{},[557,558,559],"th",{},"Type",[557,561,562],{},"What it captures",[557,564,565],{},"Example",[567,568,569,583,596,609,622,635,648],"tbody",{},[554,570,571,577,580],{},[572,573,574],"td",{},[485,575,576],{},"Fact",[572,578,579],{},"Verifiable information about a person, company, or thing",[572,581,582],{},"\"Acme Corp is on the Enterprise plan\"",[554,584,585,590,593],{},[572,586,587],{},[485,588,589],{},"Decision",[572,591,592],{},"A choice that was made, with reasoning",[572,594,595],{},"\"Extended Acme's trial by two weeks (approved by Sarah)\"",[554,597,598,603,606],{},[572,599,600],{},[485,601,602],{},"Event",[572,604,605],{},"Something that happened at a point in time",[572,607,608],{},"\"Met Acme's CTO at the conference on March 5\"",[554,610,611,616,619],{},[572,612,613],{},[485,614,615],{},"Preference",[572,617,618],{},"How someone likes things done",[572,620,621],{},"\"Acme prefers email over phone for support\"",[554,623,624,629,632],{},[572,625,626],{},[485,627,628],{},"Goal",[572,630,631],{},"An objective someone is working toward",[572,633,634],{},"\"Acme wants to launch their email program by September\"",[554,636,637,642,645],{},[572,638,639],{},[485,640,641],{},"Relationship",[572,643,644],{},"A connection between people",[572,646,647],{},"\"Alice at Acme reports to Bob\"",[554,649,650,655,658],{},[572,651,652],{},[485,653,654],{},"Action Item",[572,656,657],{},"A commitment or task mentioned in conversation",[572,659,660],{},"\"Send Acme the updated proposal by Friday\"",[535,662,664],{"id":663},"source-attribution","Source attribution",[448,666,667,668,671,672,675],{},"Every entry records where it came from. The source appears in the entry's detail sidebar, and when the source is a conversation thread you get a ",[485,669,670],{},"View source thread"," link straight into the ",[493,673,674],{"href":93},"inbox",".",[548,677,678,688],{},[551,679,680],{},[554,681,682,685],{},[557,683,684],{},"Source",[557,686,687],{},"Meaning",[567,689,690,700,710,720,730],{},[554,691,692,697],{},[572,693,694],{},[485,695,696],{},"Email",[572,698,699],{},"Captured from an email message",[554,701,702,707],{},[572,703,704],{},[485,705,706],{},"Chat",[572,708,709],{},"Captured from a chat message",[554,711,712,717],{},[572,713,714],{},[485,715,716],{},"Manual",[572,718,719],{},"Created by hand in the dashboard",[554,721,722,727],{},[572,723,724],{},[485,725,726],{},"File",[572,728,729],{},"Captured from a file",[554,731,732,737],{},[572,733,734],{},[485,735,736],{},"AI Extracted",[572,738,739],{},"Pulled out of a message by the extraction pipeline",[535,741,743],{"id":742},"confidence-and-tags","Confidence and tags",[745,746,747,754,771],"ul",{},[748,749,750,753],"li",{},[485,751,752],{},"Confidence"," is a 0–100% score of how reliable the knowledge is. It's shown as a coloured bar on the entry — green at 70%+, amber from 40%, red below — and it drifts down over time unless re-validated.",[748,755,756,759,760,763,764,763,767,770],{},[485,757,758],{},"Tags"," are free-form labels (for example ",[457,761,762],{},"important",", ",[457,765,766],{},"customer",[457,768,769],{},"q1-2026",") for grouping and skimming. They're shown as chips on the entry.",[748,772,773,774,777,778,781,782,675],{},"Entries can also be ",[485,775,776],{},"linked to contacts"," and to a ",[485,779,780],{},"conversation thread",". Linked contacts appear in the detail sidebar with links to each ",[493,783,784],{"href":177},"contact profile",[452,786,788],{"id":787},"browsing-and-searching-entries","Browsing and searching entries",[448,790,791,792,794],{},"Open ",[485,793,106],{}," from the dashboard. The page gives you a search box, a row of type tabs, and the entry list.",[745,796,797,807],{},[748,798,799,802,803,806],{},[485,800,801],{},"Type tabs"," — ",[485,804,805],{},"All"," plus one tab per entry type. Selecting a type filters the list to that type (newest first). The sidebar shows a legend of every type with its icon.",[748,808,809,812],{},[485,810,811],{},"Search"," — type into the search box and Owlat runs a full-text search over entry titles and content. The search respects the active type tab, so you can search within just facts, just decisions, and so on.",[448,814,815,816,675],{},"Click any entry to open its detail page, which shows the full content, tags, the confidence bar, source, created\u002Fupdated\u002Fexpiry dates, linked contacts, and any ",[493,817,819],{"href":818},"#relations-between-entries-typed-edges","relations",[523,821,824],{"title":822,"type":823},"Contact-scoped knowledge","tip",[448,825,826,827,830],{},"Knowledge entries linked to a contact also surface against that contact elsewhere in the product. That lookup goes through an indexed contact→entry junction, so it returns ",[485,828,829],{},"all"," entries for that contact — the complete history, not just the most recent — and stays efficient even on a very large graph.",[452,832,834],{"id":833},"creating-entries-manually","Creating entries manually",[448,836,837,838,841,842,845],{},"You don't have to wait for extraction — you can write entries yourself. Click ",[485,839,840],{},"Create Entry"," (top-right of the Knowledge Graph page, or ",[485,843,844],{},"Create First Entry"," from the empty state) and fill in the form:",[847,848,849,853,859,863,874,878,887,891,897,901],"steps",{},[535,850,852],{"id":851},"pick-a-type","Pick a type",[448,854,855,856,858],{},"Choose one of the seven entry types from the ",[485,857,559],{}," dropdown.",[535,860,862],{"id":861},"write-a-title-and-content","Write a title and content",[448,864,865,866,869,870,873],{},"Give the entry a short, descriptive ",[485,867,868],{},"Title"," and the detailed knowledge in ",[485,871,872],{},"Content",". Both are required.",[535,875,877],{"id":876},"set-the-source","Set the source",[448,879,880,881,883,884,886],{},"The ",[485,882,684],{}," defaults to ",[485,885,716],{}," for hand-authored entries; you can change it if you're recording where the knowledge actually originated.",[535,888,890],{"id":889},"set-confidence","Set confidence",[448,892,893,894,896],{},"Drag the ",[485,895,752],{}," slider (0–100%, default 80%) to reflect how sure you are.",[535,898,900],{"id":899},"add-tags-and-an-expiry-optional","Add tags and an expiry (optional)",[448,902,903,904,906,907,910,911,546],{},"Enter comma-separated ",[485,905,758],{},", and optionally set ",[485,908,909],{},"Expires in"," a number of days — after which the entry is cleaned up automatically (see ",[493,912,913],{"href":544},"expiry",[448,915,916],{},"Saving takes you straight to the new entry's detail page. Any signed-in member of the workspace can create entries.",[452,918,920],{"id":919},"relations-between-entries-typed-edges","Relations between entries (typed edges)",[448,922,923,924,927,928,931],{},"Entries can be connected by typed edges, and the entry detail page renders an entry's relations in both directions — ",[485,925,926],{},"incoming"," and ",[485,929,930],{},"outgoing",". The supported relation types are:",[548,933,934,943],{},[551,935,936],{},[554,937,938,941],{},[557,939,940],{},"Relation",[557,942,687],{},[567,944,945,955,965,975,985,995],{},[554,946,947,952],{},[572,948,949],{},[457,950,951],{},"supports",[572,953,954],{},"One entry provides evidence for another",[554,956,957,962],{},[572,958,959],{},[457,960,961],{},"contradicts",[572,963,964],{},"One entry conflicts with another",[554,966,967,972],{},[572,968,969],{},[457,970,971],{},"supersedes",[572,973,974],{},"One entry replaces another with newer information",[554,976,977,982],{},[572,978,979],{},[457,980,981],{},"relates_to",[572,983,984],{},"A general association",[554,986,987,992],{},[572,988,989],{},[457,990,991],{},"causes",[572,993,994],{},"A causal link",[554,996,997,1002],{},[572,998,999],{},[457,1000,1001],{},"blocks",[572,1003,1004],{},"One entry prevents another",[448,1006,1007,1008,1011,1012,1015,1016,1019],{},"To link two entries, open an entry's detail page, click ",[485,1009,1010],{},"Add relation"," in the ",[485,1013,1014],{},"Relations"," card, pick the edge type, search for the target entry, and save. The new edge appears immediately on both entries — outgoing on this one, incoming on the other. Hover any relation and click the ",[485,1017,1018],{},"×"," to remove it. Any signed-in member of the workspace can curate relations; a relation is automatically removed when either of its two entries is deleted or expires.",[523,1021,1024],{"title":1022,"type":1023},"Automatic relation authoring is still on the roadmap","note",[448,1025,1026,1027,1029,1030,1033,1034,1036,1037,1036,1039,1041,1042,1045,1046,1048,1049,1036,1051,1036,1053,1055],{},"You author the semantic relations by hand today, while generic ",[457,1028,981],{}," edges are generated automatically. The agent reasoning that would ",[465,1031,1032],{},"automatically"," infer ",[457,1035,951],{}," \u002F ",[457,1038,961],{},[457,1040,971],{}," edges from the content of new entries is part of the ",[493,1043,1044],{"href":424},"Knowledge Graph vision"," and is not yet wired up. The extraction pipeline already auto-creates generic ",[457,1047,981],{}," edges between entries from the same message or conversation thread (a deterministic structural linker); what is not yet wired up is the LLM reasoning that would infer the semantic ",[457,1050,951],{},[457,1052,961],{},[457,1054,971],{}," edges from entry content.",[452,1057,1059],{"id":1058},"how-knowledge-gets-extracted","How knowledge gets extracted",[448,1061,1062,1063,1066,1067,1070],{},"Extraction happens in two places: ",[485,1064,1065],{},"live, as inbound mail is processed",", and a one-time ",[485,1068,1069],{},"backfill"," that seeds the graph from your existing history.",[523,1072,1074],{"title":1073,"type":526},"Live per-message extraction",[448,1075,1076,1077,1080,1081,1084],{},"As each inbound message moves through the inbox processing lifecycle, once it's been classified Owlat mines it for organizational knowledge. The extraction fires exactly ",[485,1078,1079],{},"once per message",", is ",[485,1082,1083],{},"idempotent",", and runs best-effort (a failure on one message never blocks the message's own processing). New mail therefore grows the graph as it arrives.",[448,1086,1087],{},"The backfill is a first-run job that seeds the graph from your existing mail so the agent has historical context from day one:",[745,1089,1090,1108,1114,1120],{},[748,1091,1092,1093,1096,1097,1099,1100,1103,1104,1107],{},"It is triggered ",[485,1094,1095],{},"once",", on the first time the ",[493,1098,495],{"href":101}," is switched on (the ",[457,1101,1102],{},"false → true"," edge of the AI agent toggle). Turning the agent off and on again does ",[485,1105,1106],{},"not"," re-run it.",[748,1109,1110,1111,1113],{},"It walks the deployment's existing inbound messages in batches and runs each through the LLM extractor, which produces typed entries with ",[457,1112,736],{}," as their source.",[748,1115,1116,1117,1119],{},"It is ",[485,1118,1083],{},": a message that's already been extracted is skipped, so the job is safe to resume.",[748,1121,1122],{},"Very short messages and greetings are skipped, and extraction failures on individual messages are tolerated rather than aborting the whole run.",[448,1124,1125,1126,1129,1130,1133,1134,1137],{},"You watch and control the backfill from the ",[485,1127,1128],{},"AI Agent"," settings page (",[457,1131,1132],{},"apps\u002Fweb\u002Fapp\u002Fpages\u002Fdashboard\u002Fsettings\u002Fagent.vue","), which shows live progress — scanned, extracted, skipped, and error counts — and a ",[485,1135,1136],{},"Cancel"," action while it's running. Cancelling is admin-only and stops the run cleanly at the next batch.",[523,1139,1141],{"title":1140,"type":526},"What extraction does and doesn't do",[448,1142,1143,1144,1146,1147,1149,1150,1152,1153,1155,1156,1159],{},"The extractor makes a single structured LLM call per message, embeds each resulting entry, and stores it. It does ",[485,1145,1106],{}," itself deduplicate near-identical entries (a separate daily job handles that — see ",[493,1148,545],{"href":544},") or check for contradictions. It does hand the freshly-stored batch to a deterministic structural linker that auto-creates generic ",[457,1151,981],{}," edges (as noted under ",[493,1154,1014],{"href":818},"); the LLM-inferred semantic edges remain on the roadmap. Semantic (\"vector\") search over knowledge ",[485,1157,1158],{},"is"," live: the agent's contact-scoped knowledge retrieval runs hybrid vector + full-text search fused with reciprocal-rank fusion, returning true nearest-neighbour matches. Full-text search and browse-by-type remain the live retrieval paths in the dashboard UI.",[452,1161,545],{"id":1162},"confidence-decay-and-expiry",[448,1164,1165,1166,1168],{},"The graph is deliberately ",[465,1167,1106],{}," append-only. A scheduled maintenance job runs every 24 hours and does two things to every batch of entries it visits:",[1170,1171,1172,1185],"ol",{},[748,1173,1174,1177,1178,1181,1182,1184],{},[485,1175,1176],{},"Expiry cleanup"," — entries past their ",[457,1179,1180],{},"expiresAt"," date are deleted (along with their relations). This is how the optional ",[485,1183,909],{}," value you set on an entry takes effect.",[748,1186,1187,1190],{},[485,1188,1189],{},"Confidence decay"," — each entry's confidence is reduced based on how long it's been since it was last validated and a per-type decay rate. Frequently-recalled entries decay slightly slower (a usage-recency boost). Confidence never drops below a floor of 10%.",[448,1192,1193,1194,1197],{},"A ",[485,1195,1196],{},"second"," daily job dedup-merges near-identical entries for the same contact, keeping the graph from accumulating duplicates as new mail is mined.",[448,1199,1200],{},"Different knowledge ages at different speeds — a customer's plan changes far less often than a quarterly goal — so each type decays at its own rate:",[548,1202,1203,1215],{},[551,1204,1205],{},[554,1206,1207,1209,1212],{},[557,1208,559],{},[557,1210,1211],{},"Decay per day",[557,1213,1214],{},"Why",[567,1216,1217,1229,1241,1253,1265,1277,1289],{},[554,1218,1219,1223,1226],{},[572,1220,1221],{},[485,1222,576],{},[572,1224,1225],{},"0.5%",[572,1227,1228],{},"Facts change infrequently (~90-day half-life)",[554,1230,1231,1235,1238],{},[572,1232,1233],{},[485,1234,589],{},[572,1236,1237],{},"0.2%",[572,1239,1240],{},"Decisions persist unless explicitly reversed",[554,1242,1243,1247,1250],{},[572,1244,1245],{},[485,1246,602],{},[572,1248,1249],{},"None",[572,1251,1252],{},"Historical events don't become less true",[554,1254,1255,1259,1262],{},[572,1256,1257],{},[485,1258,615],{},[572,1260,1261],{},"1.5%",[572,1263,1264],{},"Preferences evolve over time (~30-day half-life)",[554,1266,1267,1271,1274],{},[572,1268,1269],{},[485,1270,628],{},[572,1272,1273],{},"3%",[572,1275,1276],{},"Goals have deadlines and shift (~14-day half-life)",[554,1278,1279,1283,1286],{},[572,1280,1281],{},[485,1282,641],{},[572,1284,1285],{},"1%",[572,1287,1288],{},"Org structures change",[554,1290,1291,1295,1298],{},[572,1292,1293],{},[485,1294,654],{},[572,1296,1297],{},"5%",[572,1299,1300],{},"Commitments resolve quickly (~7-day half-life)",[523,1302,1304],{"title":1303,"type":526},"Planned: validation boost",[448,1305,1306,1307,1310,1311,1313],{},"The intent is for confidence to be ",[465,1308,1309],{},"raised"," when knowledge is validated — for example when the agent uses an entry and a human approves the resulting reply. That boost isn't implemented yet, so today confidence only decays (or holds steady, for events). See the ",[493,1312,1044],{"href":424}," for the full picture.",[452,1315,1317],{"id":1316},"related","Related",[1319,1320],"link-card",{"description":1321,"title":102,"to":101},"Turn on the agent, set its confidence threshold, and trigger the knowledge backfill.",[1319,1323],{"description":1324,"title":178,"to":177},"Knowledge entries link to the contacts they're about.",[1319,1326],{"description":1327,"title":1328,"to":424},"The storage model, vector search, and the capabilities still on the roadmap.","Knowledge Graph (architecture & roadmap)",{"title":1330,"searchDepth":1331,"depth":1331,"links":1332},"",2,[1333,1335,1341,1342,1349,1350,1351,1352],{"id":454,"depth":1331,"text":1334},"What the Knowledge Graph is (and the ai.knowledge flag)",{"id":532,"depth":1331,"text":533,"children":1336},[1337,1339,1340],{"id":537,"depth":1338,"text":538},3,{"id":663,"depth":1338,"text":664},{"id":742,"depth":1338,"text":743},{"id":787,"depth":1331,"text":788},{"id":833,"depth":1331,"text":834,"children":1343},[1344,1345,1346,1347,1348],{"id":851,"depth":1338,"text":852},{"id":861,"depth":1338,"text":862},{"id":876,"depth":1338,"text":877},{"id":889,"depth":1338,"text":890},{"id":899,"depth":1338,"text":900},{"id":919,"depth":1331,"text":920},{"id":1058,"depth":1331,"text":1059},{"id":1162,"depth":1331,"text":545},{"id":1316,"depth":1331,"text":1317},"md",{},true,{"title":106,"description":107},"1.guide\u002F31.knowledge-graph","o1w0TKjKJy64-mRbYfh0jAbYuGlAvtF_bzdab_QuA_0",[1360,1362],{"title":102,"path":101,"stem":1361,"children":-1},"1.guide\u002F30.ai-agent",{"title":110,"path":109,"stem":1363,"children":-1},"1.guide\u002F32.files",1782846430860]