+ Pilot entry route

Request setup for one controlled OpenCode pilot.

We will qualify one team, one repeated workflow, 5-15 users, the sponsor/admin owner, the default guardrails, and the weekly evidence review needed for an expand, continue, or stop decision.

01 / Scope

Confirm the mission

Pick one repeated workflow such as a launch brief, support draft, implementation handoff, customer-success summary, analysis, checklist, or recommendation.

02 / Onboard

Set up the pilot path

Define users, sponsor/admin owner, approved skills, model aliases, connector boundaries, review gates, and budget limits.

03 / Run

Run through Forge

OpenCode requests move through the approved path; review-path work pauses; blocked work returns a reason.

04 / Review

Decide with evidence

Weekly receipts, usage, blocks, costs, exceptions, and outcomes support the expand, continue, or stop decision.