Request
Employee asks for real work
A launch brief request starts in normal business language inside OpenCode.
Guided operating view
From AI Request to Governed Receipt
Forge turns an employee’s OpenCode request into a governed path: preflighted before execution, routed by policy, returned as useful work, and recorded as a receipt the company can inspect.
Operating map
Scattered access becomes shared capability
The detailed system view belongs here, where the page explains how request, policy, execution, receipt, and review fit together.
01-04 / Request to receipt
The governed path stays visible at every step
The employee sees a normal work request; Forge handles preflight, routing, execution bounds, and receipts before the company scales.
Preflight
Forge checks the boundaries
Identity, skill, connector scope, budget, model route, and review rules are checked before execution.
Decision
Policy chooses the path
The request can run, pause for review, or stop with a clear reason.
Receipt
Evidence is recorded
The employee gets the work while admins get usage, cost, approval, and outcome evidence.
Request
An employee asks for normal OpenCode work while Forge captures the request as a governed work package before systems are touched.
Preflight
Forge checks identity, role, skill permission, connector scope, budget, model route, and review rules before the work runs.
Decision
The policy chooses whether the request runs now, pauses for human review, or stops with a clear reason.
Receipt
The employee gets the result in OpenCode while Forge Admin gets the receipt for usage, cost, approvals, outcomes, and exceptions.