Gentle Queue
Personal priority system Private pilot

Your work arrives everywhere. Your attention shouldn’t have to.

Gentle Queue keeps a private record of your promises, deadlines, and people—then shows you the one thing worth doing now, with the reason beside it.

See the decision See what stays under your control

Read-only to start · No autonomous sending

Do this now

Reply to Maya about the venue change.

You promised an answer by 3:00. Two people are waiting, and your next meeting begins in 25 minutes.

8 minutes 3 sources checked
Where your day already happens
  • Telegram
  • Gmail
  • Google Calendar

01 / The recommendation

One answer.
Show your work.

A priority should never feel like a guess. Gentle Queue places the evidence, the decision, and the proposed follow-through in one clear line.

Evidence 3 items

This message contains a direct request and a same-day promise.

Do this now 8 min

Reply to Maya about the venue change

You promised an answer by 3:00. Two people are waiting. Your next meeting starts in 25 minutes.

Promise
Due now
Consequence
2 people blocked
Fit
Before next meeting
Follow-through Nothing sent

Draft ready

To
Maya Kapoor
Subject
Re: Venue update
Hi Maya—yes, the venue change works. I’ll update the team before the partner review this afternoon.

Recipient and wording must be approved together.

02 / The daily rhythm

A rhythm,
not another feed.

Gentle Queue meets you at a few useful moments. It does not ask you to monitor one more dashboard all day.

  1. Morning brief

    Three commitments worth seeing before the noise begins.

    Scheduled
  2. Any time

    “What now?”

    One feasible next action, its reason, and the source it came from.

    On demand
  3. Only if needed

    A selective interruption

    Only when waiting would create a consequence you asked to avoid.

    Rule-bound

  4. Evening closure

    What moved, what remains, and what can safely wait until tomorrow.

    Scheduled

03 / Learns your judgment

Your priorities become the rulebook.

Gentle Queue starts with a short interview, then learns from each correction. You can see and change every rule it uses.

Priority constitution Version 07
  1. 01

    Keep promises visible. A commitment made to another person stays above unscheduled work.

  2. 02

    Protect focus time. Interrupt only for a same-day consequence or a named VIP.

  3. 03

    Prefer finishable work. Recommend something that fits the time and energy available now.

  4. 04

    Learn from “wrong priority.” Ask one short question, recalculate, and remember the correction.

04 / The control line

The part that talks is not the part that acts.

Gentle Queue can prepare a reply or calendar change. A separate control layer checks the exact recipient, content, permission, and expiry before anything can happen.

01 Prepare

A draft is created from the evidence.

02 Review

You see the exact action before it can run.

03 Approve

An edit cancels the approval and asks again.

04 Record

The result and its source stay inspectable.

05 / Private by structure

Your data gets its own home.

One person.

One database.

One set of keys.

Every customer gets a separate data system, credentials, backups, and assistant runtime. We share tested product code—not a customer-content database.

Conversation
Can explain and prepare. It cannot send on its own.
Memory
Promises, rules, and corrections live outside the chat and remain inspectable.
Connections
Begin read-only. Each can be revoked without dismantling the rest.
Deletion
Built to support inspection, export, disconnection, and deletion.

06 / Starts where work is

No new inbox to babysit.

Daily interface

Telegram

Ask “What now?”, correct a priority, or review a prepared draft.

Work signals

Gmail

Read-only first, looking for requests, promises, and follow-ups.

Time reality

Google Calendar

Understands fixed commitments and what can actually fit next.

WhatsApp is added only through an official, permitted route. The pilot will not scrape a personal inbox.

Private pilot / 2026

Give Gentle Queue one noisy week.

We are beginning with one person, read-only. The first week is about learning how they actually choose—not asking them to adapt to another system.

See the pilot outline
  1. 01 Map real commitments and priority rules.
  2. 02 Run recommendations in shadow mode.
  3. 03 Compare each recommendation with the user’s real choice.
  4. 04 Add drafts only after the priority quality is proven.

No autonomous sending. Disconnect and delete at any time. Wider applications open after the first design-partner pilot.