🌹 Petal · Development / integration concept
OpenCode by Rose
A development concept for connecting eligible Rose Project work with the existing OpenCode worker lanes, while keeping project ownership and completion evidence clear.
🌹 Rose & Etta · Development started · not released
See whether OpenCode by Rose fits your workflow
OpenCode by Rose is a development and integration concept for sending eligible Rose Project jobs to existing OpenCode worker lanes and checking canonical completion receipts.
What it aims to address
When work is prepared for worker lanes, a simple status such as READY or RUNNING can be mistaken for completion. Projects also need their own ownership, dependencies and approval gates to remain clear.
Scope being explored
- Keep each job attached to its owning Project.
- Prepare only jobs eligible under the existing authorized P/EX workflow.
- Use the existing LANES infrastructure for READY work.
This page separates documented scope from release claims. Check the status, evidence, privacy notes and limitations below; development progress alone does not mean the Petal is available.
🌧️ The problem
- When work is prepared for worker lanes, a simple status such as READY or RUNNING can be mistaken for completion. Projects also need their own ownership, dependencies and approval gates to remain clear.
📘 Read the OpenCode by Rose guide →
🌱 What the concept explores
OpenCode by Rose (also described as OpenCode Worker Lanes by Rose) explores a governed flow for an owning Project to prepare eligible jobs, let the existing Windows LANES Idle Refill service handle READY work, and check canonical SQLite receipts for actual completion.
- Keep each job with its owning Project and preserve dependencies and approval gates.
- Use the existing authorized P/EX workflow and the existing LANES worker infrastructure.
- Use canonical queue receipts to distinguish admitted or running work from a verified DONE result.
- Do not create a second dispatcher or treat configured lanes as proof of sustained capacity.
🛠️ Availability
Development / integration concept. This page describes a proposed integration, not a released customer product or a self-serve dispatch service. A job being claimed or marked RUNNING is not a DONE receipt; lane configuration is not proof of sustained throughput.
The described use depends on the existing authorized project and worker workflows. This page does not grant access to a queue, authorize a dispatch, or claim that every Project or job is eligible.
Continue to the OpenCode by Rose guide →
Petal information
Availability: Development / integration concept · unreleased / availability unverified. Check this project page; availability is not independently verified.
- How-to and intended usage
- Installation and setup — planned or unavailable while this Petal remains unreleased.
- Troubleshooting — no release-specific fixes verified.
- FAQ — no additional verified answers recorded.
- Compatibility and requirements — not verified.
- Privacy, permissions, and safety — consult the source page; implementation details unverified.
- Release status and evidence — no release evidence is asserted by this index.
- Support and feedback — support@kingding.co.uk.
🌱 Help shape Rose & Etta
Interested in OpenCode by Rose?
Beta enrolment is not open yet. Use the early adopter details below to register interest by email and follow the product as it develops. This records interest only; it does not reserve access or start a subscription.
See early adopter details ↓