Read-only operating queue for a one-person company. It gathers Recued-native work signals from tasks, commitments, projects, notes, mail, calendar, and contact rollups into one view so the owner can see where attention is leaking before opening separate desks.
Solo Work Queue
Pick this if you want one prioritized list instead of separate cards: a single work queue that automatically pulls inbound email, calendar activity, and contact follow-ups into tasks, commitments, and reminders, so everything needing attention shows up in one place. It is the queue-first way to start the back office — add external CRM, billing, GitHub, and approval lanes with sibling capability packs. Prefer a dashboard of separate daily cards (today, commitments, stalled projects, notes)? Choose Solo Command Center or Solo Discipline Loop instead.
What this pack installs
Included recipes
7 pinned recipes
This pack installs the complete recipe workflow together. 5 supporting recipes run as background automation.
Classify each inbound email into urgent_action / awaiting_response / fyi / promotional / spam and send an in-app notification for urgent_action + awaiting_response (subject, sender, suggested next action). Promotional / spam classify silently — no notification noise on bulk mail. Fires automatically on inbound mail; the classifier model sees only PII-aliased text, never the raw sender.
Extract commitments from an inbound email into Recued's commitment tracker — who promised what to whom, with optional deadline and monetary amount. Thread-aware: a reply like 'yes, please send that by Friday' binds to the prior message, not the reply. Fires automatically on each inbound message; records only extractions above the confidence floor (default 0.7), resolves the counterparty to a known contact when possible, and the extractor model sees only PII-aliased text, never the raw sender.
Extract action items from an inbound email into Recued's task tracker — title, due date, and priority (low / medium / high). Thread-aware; fires automatically on each inbound message; records only extractions above the confidence floor (default 0.7). A task is assigned to a contact only when the mail explicitly delegates it to a named third party — otherwise it lands unassigned. The extractor model sees only PII-aliased text, never the raw sender.
Record a per-contact meeting-reschedule pattern whenever an event's start time actually changes (title-only edits don't fire) — the behavioral signal time-alert-before-event reads for its briefs.
Reactive silent producer. Listens to calendar.created + calendar.updated events; for each fired event builds the cheap pre-summarized rollup the alert recipe consumes. Writes calendar_event_rollup keyed on event_id with a deterministic brief (event summary + attendee count + start_at) plus the canonical attendee list. Dependent policy means deletion of the underlying event cascades the rollup automatically. The full attendee-pattern fold (which would walk timeline-read for each participant) deepens in D-124 housekeeping; this v1 producer keeps the rollup fresh for every newly-created or modified event.
Show all 7 recipes
Reactive silent producer. Listens to mail.created events; extracts the sender's email and stamps a contact_timeline_rollup enrichment with the latest interaction signal. Aggregate-policy upsert keyed on contact email. D-122 ships the cheap deterministic fields only — interaction_count seeded at 1, last_interaction set, recent_subjects single-element. The fuller fold (rolling window, attendee co-occurrence, thread-aware subject deduplication) ships in D-124 housekeeping once timeline-read becomes the producer's primary input. Calendar-side contact contributions also defer to the housekeeping pass.
Builds on
Trust & control
What installing this whole pack would let it do. Recued grants these permissions at install — review them there before approving.