From 36a562146ca7b9de3a5c65f68923ca32b05a6033 Mon Sep 17 00:00:00 2001 From: Muhammad Ahmed Cheema Date: Tue, 11 Aug 2026 11:11:04 -0700 Subject: [PATCH 1/2] The second skin, in the front door The README's harness section now has its payoff: the DoorDash capability told in three paragraphs, cart as instrument, the two-key ritual, and the fact that it shipped as tool files plus configuration on unchanged machinery. Version to 0.2.0. --- README.md | 24 ++++++++++++++++++++++++ package.json | 2 +- 2 files changed, 25 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 2b37b4c..9bb086a 100644 --- a/README.md +++ b/README.md @@ -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 +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 diff --git a/package.json b/package.json index 94e8b47..9a24ce3 100644 --- a/package.json +++ b/package.json @@ -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", From 82f7a53ccc8252834bf891ec6dda30d3bc6a65ff Mon Sep 17 00:00:00 2001 From: Muhammad Ahmed Cheema Date: Tue, 11 Aug 2026 11:20:07 -0700 Subject: [PATCH 2/2] The harness diagram learns about orders A fourth output box joins instruments, the canvas, and email: orders, wearing the DoorDash mark the way the session card wears the Trigger triangle. Both themes, mocked on GitHub's real backgrounds before committing. --- brand/rendi-harness-dark.svg | 12 +++++++++--- brand/rendi-harness.svg | 12 +++++++++--- 2 files changed, 18 insertions(+), 6 deletions(-) diff --git a/brand/rendi-harness-dark.svg b/brand/rendi-harness-dark.svg index d6adc15..4eda453 100644 --- a/brand/rendi-harness-dark.svg +++ b/brand/rendi-harness-dark.svg @@ -1,4 +1,4 @@ - + @@ -55,6 +55,7 @@ + @@ -66,14 +67,19 @@ email + share links + + + + + orders - + - datasets · telemetry · its own app state + datasets · telemetry · its own app state diff --git a/brand/rendi-harness.svg b/brand/rendi-harness.svg index 01bdb73..1c1432b 100644 --- a/brand/rendi-harness.svg +++ b/brand/rendi-harness.svg @@ -1,4 +1,4 @@ - + @@ -55,6 +55,7 @@ + @@ -66,14 +67,19 @@ email + share links + + + + + orders - + - datasets · telemetry · its own app state + datasets · telemetry · its own app state