Built with rdy. Built for what's next.

Keep your intent
in the loop.

Agents move fast. Your decisions should travel with them. rdy keeps decisions and documentation connected as you design, change, and build.

Local-first · CLI + MCP · Public release in preparation

INTENT, WITH CONNECTIONSILLUSTRATIVE EXAMPLE
ACCEPTED DECISIONGuest links are read-only.

The rule behind the change stays in reach.

Sharing guideGOVERNED BY THIS DECISION
OnboardingLINKED CONTEXT
✓ Review the proposalYou decide what lands.
01rdy computes.
02Agents write.
03People decide.
The reason behind the work

A new session shouldn't mean a fresh start.

A decision changes. One page is updated. Another still carries the old rule. The next agent starts with an incomplete picture.

rdy gives decisions a durable place, links them to the content they govern, and brings that context into the editing workflow. The accepted design stays separate from work in progress.

From intent to accepted change

Context first.
Then a change you can review.

Explore a simple example. These panels explain the workflow; they are not product screenshots.

BRIEF BEFORE AN EDIT

“What governs guest sharing?”

The agent asks rdy for context. The briefing returns the recorded decision and linked material relevant to the change.

Request → governing decision → linked documentation
A tool you can build around

Your work. Your record.
Your decision.

Local-first by design

The core workflow runs on your machine. Use the CLI yourself or connect an agent through MCP.

Explicit connections

Typed blocks, recorded links, and version history make governing decisions and dependent content available to the workflow.

A human decision point

Agents propose changes in separate views. You review what becomes accepted, with the reasoning kept in the record.

rdy computes from recorded relationships. It does not guarantee every dependency has been captured or replace human judgment.

rdyhub

A home for intent.
Connected to where you build.

rdyhub is the upcoming service for individuals and teams using agentic workflows. Designs, decisions, and intent live together; integrations carry that context into implementation.

Built from a real need

rdy is being built on rdy.

Built to support a real agentic workflow.
Now being prepared for public release.