Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
24 changes: 24 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -87,6 +87,30 @@ what the tools do. Strip the analytics tools and wire your own: the inbox patter
the heartbeats, the self-review, and the zero-cost standby all come with the
harness. We made it an analyst. You can make it anything.

## The second skin

The harness claim needed proof, so we gave the same agent DoorDash. Through the
official [DoorDash CLI](https://github.com/doordash-oss/doordash-cli), on a

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Point the DoorDash CLI link at the actual repository

Readers following this link to obtain the CLI are sent to the nonexistent doordash-oss/doordash-cli repository. The deployment guide correctly identifies the official repository as https://github.com/door-dash/dd-cli, so this new README link should use that URL as well.

Useful? React with 👍 / 👎.

personal account, it browses restaurants, reads menus with the full modifier
tree, and builds a cart that renders as an instrument like any chart: steppers,
tip presets, delivery or pickup, the honest fee ladder, yours to touch without
the model in the loop.

Placing the order is a two-key ritual. The agent holds every tool including
submit, and it still cannot spend a cent alone: asking for approval freezes the
cart into a hash and emails a six-digit code to the owner's inbox and nowhere
else. The code is typed into the order card, never into the chat. The approval
is single-use, dies in fifteen minutes or after five wrong guesses, and any
change to the cart after the email, one more taco, a different tip, voids it.
Spend caps live below the agent. Safety here is structural, not a system prompt.

No new infrastructure appeared for any of this. The cards ride the same
transcript, the code entry wakes the agent through the same session inbox that
dataset loads use, and the whole capability is a few tool files plus
configuration: your own CLI token, your own approval inbox, your own caps
([docs/DEPLOYMENT.md](docs/DEPLOYMENT.md)). Delete four lines from the agent
file and it never existed. That is what "skin" means.

## How it compares

- BI tools (Tableau, Metabase) give you dashboards someone authored for you. Rendi
Expand Down
12 changes: 9 additions & 3 deletions brand/rendi-harness-dark.svg
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
12 changes: 9 additions & 3 deletions brand/rendi-harness.svg
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
2 changes: 1 addition & 1 deletion package.json
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
{
"name": "rendi",
"version": "0.1.0",
"version": "0.2.0",
"private": true,
"description": "Questions become interfaces: a chat agent whose answers are live, steerable instruments over ClickHouse, on Trigger.dev durable sessions.",
"license": "MIT",
Expand Down