demon hunter labs
Projects18
Every project, one jump awayChoose what you want to build.
Open the full Atlas

Foundation

Creation

Operations

Research

← Falcon manual

What it is / interactive architecture

Falcon: Multi-account Google desktop client for mail, calendars, and contacts

Falcon brings Gmail, Google Calendar, contacts, and daily planning from multiple Google accounts into one quiet Windows desktop application without losing account ownership. This diagram follows consent, provider data, normalization, isolated synchronization, local SQLite storage, and Falcon's mail, calendar, people, and Today workspaces.

CAST / 07

Falcon field guide

Cael VossThe Courier
Open complete manual
Multi-account Google desktop client for mail, calendars, and contactsREV 03
100%
SHAPE KEY
Multi-account Google desktop client for mail, calendars, and contactsFalcon brings Gmail, Google Calendar, contacts, and daily planning from multiple Google accounts into one quiet Windows desktop application without losing account ownership. This diagram follows consent, provider data, normalization, isolated synchronization, local SQLite storage, and Falcon's mail, calendar, people, and Today workspaces. Every station and route can be selected for more information.Settings asks the service for an authorization URL and opens browser consent.R01 / connect accountStored account credentials authorize the selected Google provider calls.R02 / bearer identityLive API requests and responses cross the WinHTTP transport boundary.R03 / HTTPS responsesGoogle JSON and encoded message bodies enter endpoint-specific normalizers.R04 / provider payloadNormalized records and provider cursors advance the correct account and area checkpoint.R05 / cursor + recordsBounded provider work updates normalized cache state and last-success metadata.R06 / transactional syncThe service serializes local accounts, folders, messages, events, contacts, suggestions, and capabilities for the client.R07 / bootstrap stateThe WebView client fetches bootstrap, status, message bodies, and action outcomes from 127.0.0.1.R08 / loopback JSONNavigation and account filters project cached mail into folder, list, and reading panes.R09 / mail modeShared search and account context project cached events into calendar and Today layouts.R10 / calendar modeAccount filters and search project official and suggested people into distinct surfaces.R11 / people modeArchive, delete, move, read, send, reply, forward, and body requests return to the local authority.R12 / mail actionsCreate, edit, delete, and email-to-event operations cross the same loopback API.R13 / event actionsAdd, edit, search, and promotion intents are routed through account-scoped service behavior.R14 / contact actionsSelected message context can seed a calendar event without leaving Falcon.R15 / message to eventPerson context links scoped contacts and suggestions back to relevant local messages.R16 / related messagesUpcoming meetings contribute participant context without promoting unverified contacts.R17 / attendee contextOAuth parsing, state validation, scope, credential targets, and config paths have local tests and release requirements.R18 / security gatesMigrations, sample synchronization, persistence, and account isolation are exercised through temporary SQLite databases.R19 / fixture round tripLoopback binding, logging, sanitization, CORS, and action routing define the security review surface.R20 / threat boundaryBrowser consent, loopback callback validation, token exchange, refresh, and Windows Credential Manager associate one Google identity with one Falcon account.APIN0101 / IDENTITYGOOGLE OAUTH+ CREDENTIALSIN 01BoundaryOUT 02Google profile, label, message, event, calendar-list, connection, search, and mutation endpoints provide the external account data and actions.INN0202 / PROVIDER INPUTGMAIL + CALENDAR+ PEOPLEGmail modify surfaceIN 01InputOUT 01WinHTTP transport, bearer authentication, form encoding, status classification, capability definitions, retry policy, and reauthorization decisions contain provider-specific network behavior.APIN0303 / TRANSPORTHTTPS CLIENT+ CAPABILITIESIN 01BoundaryOUT 01Provider response parsers translate Google-specific payloads into Falcon accounts, folders, messages, events, contacts, and cursor records with source ownership attached.FXN0404 / MODELNORMALIZE +ACCOUNT SCOPEGmail header and body normaliza...IN 01ProcessOUT 01The scheduler and sync planner create mail, calendar, and contacts work per account using independent credentials, checkpoints, batches, retries, and last-success state.FXN0505 / ORCHESTRATIONSYNC PLAN +BACKOFFAccount x area checkpointsIN 01ProcessOUT 01Three migrations and a data-access layer persist normalized accounts, mail, events, contacts, suggestions, capabilities, preferences, credential metadata, and sync cursors.DBN0606 / STATESQLITE WALLOCAL CACHEIN 01State storeOUT 02A Windows service process serves bootstrap state, health, capabilities, OAuth, sync, message, account, and mail-action routes on 127.0.0.1.APIN0707 / LOCAL BOUNDARYLOOPBACKHTTP SERVICEDefault port 8765IN 04BoundaryOUT 02The native host loads the local Falcon interface and coordinates navigation, search, account filtering, shared context, density, themes, and service availability.OUTN0808 / PRESENTATIONWEBVIEW2DESKTOP SHELLFresh WebView2-enabled buildIN 01OutputOUT 04Account folders, unified inbox, compact messages, safe reading, attachments, search, person context, and provider-backed actions form the primary mail workspace.OUTN0909 / WORKSPACEMAIL +READING PANEIN 02OutputOUT 02Month, week, day, agenda, and optional Today views keep events, account colors, reminders, attendees, and email context inside the shared shell.OUTN1010 / WORKSPACECALENDAR +TODAYCreate, edit, and delete flowsIN 02OutputOUT 02Official People records and separately inferred mail-history suggestions provide scoped search, detail, add, edit, related messages, and meeting context.OUTN1111 / WORKSPACECONTACTS +SUGGESTIONSIN 02OutputOUT 02Native unit checks, fixture integration, UI smoke, a credential-gated live smoke, build artifacts, screenshots, security docs, and unchecked acceptance gates define the current pre-release boundary.QAN1212 / EVIDENCETESTS +RELEASE GATES29-step fresh GNU buildIN 03EvidenceOUT 00DHL-VISUAL-PROGRAM / FALCON / REV 04VARIABLE NODES / DISTRIBUTED PORTS / INSPECTABLE CONTRACTS