QUORUM

Private alpha · Desktop v0.1.0-alpha.1

Your AI should sit in the room. Not above the rules.

Quorum turns team conversation into governed action: inspectable plans, explicit authority, human approvals, durable automations, and exact external results—all in the thread where the work began.

Download the desktop alpha Talk to HiperFusion
  • No trackers
  • Private server
  • Windows + Linux
WORKFLOW / RESPONSE + REVIEWLIVE
Dependency graph resolved
01Read mailcomplete
02Resolve contactWassim Nahle
03Send responseapproval
04Schedule reviewapproval
05Create remindernext run visible
RECEIPT Exact provider references return to chat
AI in the conversationZoho workplaceApproval boundariesDurable automationsAction receiptsKeycloak SSO

THE DEMONSTRATION

One important email.
Seven visible moves.

Most assistants hide the leap between “I understood” and “I did it.” Quorum makes that leap the product: each dependency, authority decision, approval, result, and future run stays inspectable.

  1. 01
    Important mail arrives.

    The mailbox monitor notices a new message after its baseline is established.

  2. 02
    Quorum brings context to the owner.

    A summary lands in the owner’s private AI conversation with its source reference intact.

  3. 03
    The user asks once.

    “Find Wass’s address, send the response, schedule a review, and remind me Friday.”

  4. 04
    The plan becomes inspectable.

    Quorum shows the ordered graph and resolves dependent parameters before approval.

  5. 05
    Authority decides the boundary.

    Permitted reads can run; sensitive sends and calendar writes pause on their exact payloads.

  6. 06
    Receipts close the loop.

    Confirmed outcomes and provider references return to the conversation—not a vague “done.”

  7. 07
    The reminder becomes durable.

    It appears enabled in Automations with status, run history, and its next run visible.

Quorum AI · private conversationGOVERNED
AI
IMPORTANT MAIL · ZOHO MAILResponse requested before the Friday review

Summary preserved with source mailbox and message reference.

ET

Find Wass’s address, send the revised response, schedule our review, and remind me Friday.

INSPECTABLE DEPENDENCY GRAPH4 STEPS
01 · SAFE READResolve contactWass → unique match
02 · APPROVALSend responseresolved payload visible
03 · APPROVALSchedule reviewattendee + time visible
04 · QUORUMCreate reminderenabled · next run set
EXACT ACTION RECEIPTConfirmed externally

Provider reference attached · audit identity preserved

Illustrative workflow. Automatic versus approval-bound execution follows the owner’s configured authority policy.

THE CONTROL PLANE IS THE CONVERSATION

AI that can act.
Authority you can see.

01 / PARTICIPATION

AI lives where the work is discussed.

Ask in a room or continue privately with Quorum AI. Important mail can arrive as context, while decisions, proposed actions, and execution results remain attached to the human conversation.

ETUse the revised response and make the Friday review happen.
AII found four dependent steps. Two need your approval.
02 / AUTHORITY

Permission is specific, not vibes.

Set authority per tool: disabled, approval-bound, or automatic. Then constrain recipients, domains, bulk thresholds, and automatic recipient counts.

Mail readsAutomatic
External sendsApproval
Calendar changesApproval
Destructive workAlways gated
03 / WORKPLACE

One Zoho connection. Real office work.

Quorum’s current Zoho surface covers mail, calendar, tasks, notes, and contacts—including ambiguity-safe contact-to-email resolution.

  • ZMMail
  • ZCCalendar
  • ZTTasks
  • ZNNotes
  • Z+Contacts
04 / AUTOMATION

Automations don’t disappear into a settings page.

Reminders and action chains are durable server objects with retries, status, last and next run, history, enable/disable, and Run now.

ϟ
Friday review follow-upEnabled · one-time reminder
NEXT RUNFri · 14:00 UTC
05 / PROVENANCE

“Done” is not a receipt.

Quorum records the tool invocation, actor, approval history, terminal result, and external provider reference. Failed prerequisites cancel dependent work.

STATUSSUCCEEDEDPROVIDERZoho MailREFERENCEattached to action
06 / COLLABORATION

Private space stays private.

Private rooms and direct conversations enforce membership across messages, search, live delivery, file upload, and authenticated file download. File bytes never become public links.

# private-room@ direct-message↧ governed-file

PRIVATE BY ARCHITECTURE

Your collaboration server is not a public SaaS tenant.

Quorum Desktop connects over HTTPS/WSS to a separately provided, private Quorum server. The server owns identity mapping, authorization, room membership, AI observation, action policy, execution, files, and durable history.

  • Keycloak SSOBrowser-based OpenID Connect with PKCE; passwords never enter the client.
  • Server-side secretsProvider credentials and refresh material stay off the desktop.
  • Isolated capability processTools receive scoped execution context—not conversational authority.
  • Codex-powered at HiperFusionThe HiperFusion deployment runs its AI through an ephemeral, server-side Codex process.
WINDOWS / LINUXQuorum Desktopconversation + approvals
HTTPS / WSS
YOUR PRIVATE DEPLOYMENTQuorum Serveridentity · policy · history
KeycloakSSO
CodexAI
Zohoworkplace

Deployment shape shown for the HiperFusion-hosted offering. AI and provider choices are server configuration decisions.

DESKTOP CLIENT · v0.1.0-alpha.1

Take the client.
Bring an authorized server.

ALPHA

Early access software for authorized Quorum deployments. The server is licensed and provided separately.

⊞
WINDOWS x64

Quorum Desktop

Self-contained ZIP bundle. No separate .NET installation required.

Version
0.1.0-alpha.1
Package
68.4 MiB
Format
.zip
Download for Windows
Install + verify
  1. Download the ZIP and checksum file.
  2. Verify the SHA-256 value in PowerShell.
  3. Extract the ZIP, then run Run-Quorum.cmd.
Get-FileHash .\quorum-desktop-0.1.0-alpha.1-win-x64.zip -Algorithm SHA256
$
LINUX x64

Quorum Desktop

Self-contained tarball for a graphical Linux desktop. No separate .NET installation required.

Version
0.1.0-alpha.1
Package
44.3 MiB
Format
.tar.gz
Download for Linux
Install + verify
  1. Download the tarball and checksum file.
  2. Verify the SHA-256 value.
  3. Extract, enter the folder, and launch.
sha256sum quorum-desktop-0.1.0-alpha.1-linux-x64.tar.gztar -xzf quorum-desktop-0.1.0-alpha.1-linux-x64.tar.gz
cd quorum-desktop-0.1.0-alpha.1-linux-x64
./run-quorum.sh
#
RELEASE INTEGRITY

SHA-256 checksums

Download checksum file ↓
Linux x64ecbd954035373949e5a6135075282667e80e5baf60f125b8607f4b807629a62d
Windows x64bd5cfe052a9b68461fa857452f1e869dc5c060849cdd0c216121600744b24a7d

What is in the download? Only the native desktop client and its private runtime dependencies. No Quorum server, database, connector key, OAuth material, model credential, or provider secret is included. The launcher defaults to the HiperFusion Quorum service; alternate servers must be authorized deployments.

BRING YOUR TEAM. KEEP YOUR BOUNDARIES.

Want a private Quorum deployment?

ernie.teem@hiperfusion.com