📘 Concept guide · Development / integration concept

OpenCode by Rose: a guide to the proposed workflow

These steps describe the intended integration. They do not dispatch a job by themselves.

Before you begin

Status: Development / integration concept. Use only an authorized workflow for the owning Project. Preserve its ownership, dependencies and approval gates. This guide does not grant queue access or make an unapproved job eligible.

A proposed job flow

Create or reconcile the work in the Project that owns it, with a clear scope and acceptance criteria.
Resolve dependencies and preserve any human, security or other approval gates.
Use the authorized P/EX process to prepare and admit only eligible work.
Let the existing Windows LANES Idle Refill service handle READY jobs; do not create a competing dispatcher.
Use Rose Super Admin or the authorized status view to understand lane state, without treating a status label as proof of completion.
Check the canonical SQLite result receipt for the job. A claimed or RUNNING state is not the same as a verified DONE receipt.

Reading outcomes carefully

READY means queued and eligible for the existing workflow; it does not prove a worker has started.
WORKING or RUNNING means the job is in progress, not done.
Only the canonical result receipt and its matching job evidence establish completion.
Lane count or a demonstration of concurrent lanes does not establish sustained throughput.
Do not replay a completed job or bypass a blocker; keep the owner and exact blocker visible.

Back to the OpenCode by Rose overview →

Installation, compatibility and availability

Release status: Development / integration concept · unreleased / availability unverified. No installation steps or supported platform are provided unless a verified release is announced. This guide records the intended workflow, not an available control.

Setup: no verified installer, prerequisites, configuration or permission flow is documented here. Do not follow speculative installation steps.

Compatibility and requirements: not verified.

Troubleshooting

No release-specific faults or recovery steps are verified while this Petal remains unreleased. Check its availability first; if you think this page is wrong, contact support.

Frequently asked questions

Can I use this Petal now?

Availability is not verified; the status above describes the current evidence.

Does this page promise a release date?

No. It records the intended workflow and known evidence gaps.

Privacy, permissions and safety

Do not provide secrets or sensitive data to a concept workflow. Data handling, storage and permissions must be confirmed from an implemented build before release.

Release status and evidence

Status: Development / integration concept · unreleased / availability unverified. This guide is not release evidence. Confirm availability on the Petal overview; no supported release is asserted here.

Support and feedback

Send a question, correction or suggestion to support@kingding.co.uk.

Return to the OpenCode by Rose overview.