Overview
Pragmos is built so people can feasibly plan their days, adapt schedules in real time, and get work done without the usual friction of coordination. It treats scheduling as a systems problem - not a series of emails and back-and-forths.
Instead of negotiating times person-to-person, you configure preferences and availability. Agents communicate on your behalf. Compatible slots emerge from what everyone already wants and when they are free. No more sending a message and waiting days for a reply just to book thirty minutes.
The goal is simple: eradicate the headache of scheduling so individuals and teams can focus on the work that actually moves things forward.
Core Philosophy
Traditional scheduling is time-based theater: propose, counter, wait, repeat. Pragmos flips that model. Preferences and availability become first-class inputs. Agent-to-agent communication does the matching.
You define how you work - preferred blocks, focus windows, meeting load, constraints. Others do the same. Schedules are established from those signals and live calendars, not from endless threads. The platform exists to make that coordination invisible and reliable.
Email threads, calendar links, timezone confusion, delayed replies, and meetings that still don’t fit.
Preferences in, compatible times out - agentically aligned schedules without the negotiation tax.
How Scheduling Works
Pragmos combines personal preference profiles with live availability. Agents negotiate and propose slots that respect everyone’s constraints. You approve or adjust; the system keeps learning what “good” looks like for you.
-
01
Configure preferences
Focus blocks, meeting density, preferred hours, buffers, and hard constraints - once, then refined over time.
-
02
Agent-to-agent coordination
When a meeting or shared block is needed, agents align on availabilities and preferences - not on who replies first.
-
03
Adapt continuously
Plans change. Pragmos rebalances schedules when priorities shift, conflicts appear, or you simply ask it to.
-
04
Execute with clarity
A day that already fits how you work - plus the hooks to hand work off to agents when you need focus elsewhere.
Voice-Native Control
Speak to Pragmos. Tell it to tighten focus time, protect mornings, push a block, or rethink the week. It reconfigures preferences, adapts the schedule, and surfaces recommendations - without forcing you back into a dense UI every time something changes.
Vocal interaction is for the moments when typing a preference or dragging events is the wrong interface: walking between meetings, mid-context-switch, or when you just want the system to “make this work.”
Capabilities
Preference-driven planning
Schedules shaped by how you actually work - not generic free/busy alone.
Agent-to-agent booking
Compatible times emerge from mutual availability and stated preferences.
Voice reconfiguration
Update preferences, shift blocks, and get recommendations by speaking.
Live schedule adaptation
When the day breaks, the plan re-forms around what still matters.
Task-aware days
Planning that accounts for work to do - not only meetings on the calendar.
Frictionless coordination
Replace email lag with structured, agentic alignment between people.
Ecosystem: Orrin & OrrinInfinity
Pragmos is not a standalone island. It sits inside the Stellr stack so scheduling becomes part of how you think, note, and delegate - not a separate chore.
Dispatch work to agents
Hand off tasks from your schedule so agents can run them while you stay on higher-leverage work. Pragmos keeps the day coherent; Orrin executes the pieces you shouldn’t have to babysit.
Schedules on the infinite canvas
Drop meetings, TODOs, and schedule blocks onto the infinite canvas. Build notes, schematics, and context around them - so planning and deep thinking live in one spatial workspace instead of fragmented apps.
Why It Matters
Scheduling is not “just logistics.” It is cognitive load, delayed decisions, and lost focus. Every round of “does Thursday work?” steals attention from the work the meeting was supposed to serve.
Pragmos is designed so schedules become compatible with one another agentically - preferences and availability as the protocol, agents as the negotiators. You get time back for judgment, craft, and the work only you can do.
The point
Streamline scheduling. Remove the headache. Make plans that fit real people and real constraints - so attention stays on what matters.
Plan · Adapt · Execute