Ro · email · browser
Keep work coherent over time.
Ro keeps Tasks, Notes, relationships, responsibilities, waiting, decisions, and delegated results connected. The few things that need your judgment return with context.
Product direction · Ro is under active development
Attention means something deserves you now.
Responsibilities and possible Commitments describe what must remain true. Waiting explains what cannot move. When Ro or a delegated executor can safely handle a condition within existing authority, it should do so before consuming your attention.
Three things need you.
Friday, 19 September
MatterWhy nowNext action
Customer proposalCommitment
Draft is ready; promised outcome needs approval
Review proposalOnboarding issueResponsibility
Recovery exhausted; release authority required
Decide on fixSupplier agreementWaiting
Follow-up threshold passed; no automatic authority
Approve follow-upA calm day can say “Nothing needs you right now.” That is a product outcome, not an empty state failure.
One organizational model, whoever does the work.
You, other people, automations, and agents can all discharge responsibility. Ro cares about intended state, authority, outcomes, evidence, and meaningful divergence.
What must remain true?
Responsibility · Commitment if validated · Waiting · Decision · Authority
Their chosen tools
Schedules · provider systems
External execution state
Responsibility and attention outlive the executorQuiet unless judgment is required
Agent use is an accelerator, not a prerequisite. The organizational record must earn its place before the first agent is configured.
Specialist artifacts stay in their natural systems.
Source control owns code. Mail owns messages. Accounting owns the ledger. Ro owns ordinary work and keeps the responsibility, promise, decision, accepted outcome, risk, and evidence reference connected.
Ro
Tasks, notes, discussions, relationships
Source control
Code, issues, changes, checks
Mail and calendar
Messages, delivery, appointments
Specialist systems
Ro keeps the work and its organizational meaning connected.Accounting, payments, workflows, agent execution
Adapters stay bounded: reference, observe, resolve, command, report, and reconcile. No universal ingestion layer and no full provider copy.
Today
5 matters across your work
In motion
Review supplier proposalAlex · Operations
Call Morgan at AcmeRenewal · Follow up
Decide launch scopePlanning discussion · Conclusion needed
Returned
Proposal waiting for clientMorgan replied this morning
Investigate production failureOperations · Agent result ready
Native local workspaceSearch / Capture c Go g
A first-class native workspace
Tasks, Projects, Notes, relationship records, Discussions, Capture, and Views are where ordinary work can happen. Specialist workflows remain external when their systems are the better home.
Keep the operating scope around the outcome.
A Project gives work a security and operational boundary while external tools remain authoritative for their detail.
Northstar launch
Prepare the new service for its first customer rollout.
- Owner
- Alex
- Open Tasks
- 8
- Waiting
- 2
- Needs attention
- 3
Work now
Finish onboarding checklistAlex · In progress
Review import behaviorSam · Review
Confirm rollout groupWaiting for two replies
Knowledge and decisions
Release approachNote · Updated yesterday
Scope the first releaseDiscussion · Concluded
Acceptance scenariosNote · 4 related Tasks
Northstar launch / 18 related recordsHistory available
Finite work carries its organizational context.
A Task can hold assignment, blockers, waiting, review, Project context, related records, and attributable history without becoming a copy of the execution system.
Prepare Acme renewal proposal
- Status
- In progress
- Assigned
- Alex
- Project
- Northstar renewal
- Review
- Sam
Prepare the commercial proposal for Acme’s annual renewal. Reflect the agreed scope, confirm the service period, and leave the final offer ready for review.
The Task carries its business context without turning the people, opportunity, or source material into attachments inside a generic record.
Related business context
Acme OrganizationMorgan Lee PersonAnnual renewal OpportunityPricing rationale NoteTask T-209 / 4 related records8 attributable changes
Use Ro Tasks for ordinary work. Keep an External Reference when source control, mail, accounting, or another specialist system should retain the canonical artifact.
Keep the decision and its grounds.
Notes hold authored context. Discussions preserve deliberation and an explicit conclusion. Neither must replace the specialist source which produced the evidence.
Release approach
The first release should support a complete local-only workflow for one owner before synchronized collaboration expands the surface.
What this means
Capture, Tasks, Notes, relationships, Attention, CLI access, and local agent work must form a coherent daily system without an account or server.
Cloud collaboration follows the same domain and history. It should extend the product rather than redefine the local product as a trial.
Note updated from Discussion conclusionHistory available
Keep the relationship, not a second inbox.
People, Organizations, Opportunities, and Interactions retain business significance and references without turning Ro into a full mail client or heavyweight sales suite.
Acme
Software infrastructure company · Client since 2024
- Relationship
- Client
- Account lead
- Alex
- Open opportunity
- Annual renewal · €48k
- Next commitment
- Proposal by 25 Sep
People
MLMorgan LeeVP Operations · Primary contact→Current work
Prepare Acme renewal proposalTask · Alex · In progress→Acme / 1 Person / 1 Opportunity / 6 InteractionsFollow-up due today
Native and local-first by default.
The complete local product works without a mandatory account or server and remains useful through its GUI, CLI, capture surfaces, agents, and integrations. Add synchronization when the work needs shared authority.
The complete local authority lives here.
- Authority
- This Mac
- Account
- Not required
- Availability
- Offline
- Access
- Native app · CLI · local API
- Capture
- Global shortcut · links · files
Organizational state and any first-party records remain available without a Ro server.
WHEN THE WORKSPACE NEEDS TO TRAVEL
Add synchronization without changing what the work means.
Use Ro Cloud or a self-hosted Ro Server when people, devices, or remote workers need one shared authority. Native clients keep authorized work locally available.
Native desktopWorkspace authorityOther people, devices, and workers
Ro is under active development.
These concept surfaces communicate the intended product and operating model, not a claim that every capability ships today.
Follow development →Keep the work moving without watching every step.
Join early access and help test whether Ro can make unnecessary attention disappear.