Rose & Etta, by King Ding
Rose & Etta is the customer-facing brand under which these products are presented. TemuPrime is the business/account name and trades as KingDing. John Daly is the legal owner and operates as a sole trader. The website domain is KingDing.co.uk.
What this site shows
A project garden: product ideas, supporting projects, and source-backed status notes. A project progress percentage is not the same as a release date or a statement that a product is ready.
Rose & Etta is preparing monthly and annual subscription options. Current plan prices, the early-adopter offer and its terms are listed on the Pricing & Early Access page. Paid checkout is not open yet; registering interest does not start a paid subscription.
Rose, Etta and the Petal model
Rose is the customer-facing control: a person describes a goal, and the system is intended to select a suitable Petal within its scope, request required approvals and report what it actually verified. This is the product direction, not a claim that every part is released.
Etta is the technical software side: the engineering foundation, integrations, systems and product development behind the Rose & Etta experience.
A Petal is a plugin. Petals are named for practical capabilities that grew from problems encountered while working on projects.
Why I started making Petals
“I kept hitting little obstacles while building my own projects with ChatGPT: blocked calls, repetitive work, disconnected plugins and subscriptions everywhere. So I began creating my own tools. I call them Petals — plugins built to work together.”
The problem is that a straightforward task can become a maze of separate extensions, limits, lost context and manual steps. Rose & Etta is the answer John is working toward: practical tools for real problems, with authorised automation and human approval where needed.
The long-term ambition is to make compatible tools for other AI assistants where their APIs and permissions allow it. The goal is for the same subscription to cover compatible Petal versions as they launch, rather than charging again for each assistant; this is a development goal, not a current compatibility promise. Many Petals remain in development; their individual pages show verified status and limits.
John’s personal biography is still awaiting his final review before publication. Read the My Story status.
Where the flower and Petal model came from
“Imagine Rose is the Flower that controls all petals. Users don't talk to the petals. They talk to Rose.”
This product-design line appears in a preserved conversation dated 11 October 2026. That record supports the flower-and-Petals model; it does not establish the first moment the names “Rose” or “Petals” were coined.
From the KD Bridge to permission-aware work
The early KD Bridge explored a read-only view of work states and a handoff to the main controller. Two anonymised historical snapshots show that status counts changed over time. They illustrate a prototype visibility goal, not current production reliability, verified completion, or proof of today’s ROSE API and RDC behaviour.
The later ROSE/RDC direction keeps the useful aim: clear, permission-aware work with verifiable receipts.
Ideas, projects and published Petal pages
The public Rose Petal index contains 48 canonical Petals, with aliases combined under their canonical entries. A Petal page does not mean a released or installable product; each page shows the available status, evidence and setup guidance. Meet Etta remains available as a story page.
Other ideas remain in development or internal records and are added to the public catalogue only when identity and status are source-backed.
John’s personal story
The fuller autobiographical account will appear after John has reviewed and approved its final wording. See the My Story page.
First Four roadmap · OpenCode Worker Lanes · 100% Clarity · Community