Turn one customer request into a governed delivery system.
Start with a valuable job, not an autonomous-agent promise. Define the authority, build the workflow, verify the result, and keep the repository and operating knowledge.
The reference desk runs in your browser and sends nothing. It produces a scoping artifact, not a price, contract, customer message, or income prediction.
Four stages. Four reviewable artifacts.
Each stage makes the next decision easier to inspect, repeat, and improve.
- 01
Define the request
Capture the customer job, current process, success condition, constraints, and authority boundary before choosing tools.
Artifact · Request brief - 02
Design the system
Map the agent work, human decisions, evidence, failure path, and customer handoff as one bounded outcome pack.
Artifact · Income system contract - 03
Implement the path
Build the workflow and customer surface in a repository the principal owns. Keep production actions behind approval.
Artifact · Git-backed preview - 04
Verify the outcome
Run acceptance checks, record limitations, and hand over the operating decision instead of declaring success from a demo.
Artifact · Evidence bundle
Request-to-Quote Desk.
A local-service or B2B request becomes a complete brief before an agent is allowed to propose customer-facing scope.
Inspect the open reference contract- Customer input
- A structured request with explicit success and non-goals.
- Agent work
- Triage, missing-information detection, scope draft, and quote brief.
- Human decision
- Approve scope, pricing, contractual language, and any customer-facing send.
- Evidence
- Inputs, versions, checks, decision log, preview, and delivery receipt.
Agents prepare. An authorized principal commits.
Research, triage, drafts, tests, and evidence gathering can run automatically. Pricing, contracts, public income claims, production promotion, customer sends, credential grants, and movement of money require explicit authority and an auditable approval.