> For the complete documentation index, see [llms.txt](https://docs.concurrence.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.concurrence.com/developer-guide/guides/build-and-prove.md).
# Build and Prove
Configure a Platform service, verify its behavior with a bounded test, and promote reviewed versions with evidence and a recovery plan.
Use this path to turn an agent configuration into a service you can test and deliberately promote. Start with a test workspace, permitted synthetic data, and an implementation owner who can confirm the required tools and channels are enabled.
Promotion is an explicit decision based on reviewed evidence; recovery also checks external effects.
## Build
Console groups authoring under **Build**: Agents, Context Graphs, Tools, Services, and Channels. Visibility and permissions depend on the workspace. Use the corresponding contracts when automating the same task.
1. Confirm [credentials and workspace access](/developer-guide/getting-started/credentials.md).
2. Configure the [agent](/developer-guide/platform-api/workspaces/agents.md) and [Context Graph](https://docs.concurrence.com/agent/context-graphs). Identify which tools can read data or change an external system; use test targets for the first run.
3. Bind the agent and graph in a [service](/developer-guide/platform-api/workspaces/services.md). Read back the selected versions and field-specific configuration. A service version set does not isolate all data or external effects.
4. Choose the supported [conversation path](/developer-guide/platform-api/conversations.md). Managed channels additionally require their [provisioned binding](/developer-guide/platform-api/workspaces/use-cases.md).
If a tool needs an application value supplied when the conversation starts, follow [Pass Context to Tool Parameters](/developer-guide/guides/conversation-context.md) to declare the service schema and bind the parameter in the graph. Keep that input separate from identity bindings and choose the tool's result-retention policy deliberately.
## Prove
Console's **Prove** area includes Playground and Simulations. Choose your first check:
* [First Console Conversation](/developer-guide/guides/first-console-conversation.md) walks through a browser text session with your configured service, including readiness errors and inspection controls.
* [First Verified Conversation](/developer-guide/guides/first-verified-conversation.md) provides a runnable SDK project, durable-answer verification, a rejected-request exercise, and cleanup. Start locally without credentials, then use its provisioned mode to test your service.
For a graph or channel change, use [Playground](https://docs.concurrence.com/testing/testing/playground) and the applicable [simulation workflow](https://docs.concurrence.com/testing/testing/simulations). Record the configuration, input, expected outcome, observed result, and failures. Verify an external effect separately with [Verify an Integration Action](/developer-guide/guides/verify-an-integration-action.md). Simulation success does not establish production delivery or deterministic future output.
## Promote and Recover
Use [Version Sets & Promotion](/developer-guide/operations/devops/version-sets-best-practices.md) to compare the candidate with the current release and retain the previous selection for rollback. Prefer explicit component versions for a reproducible release; an unpinned version can resolve newer configuration later.
Before promotion, record who reviewed the evidence, which channel and integration checks ran, and how to recover if the new behavior fails. After promotion, inspect a permitted test run through [Runs](/developer-guide/platform-api/conversations/runs.md). Rolling back configuration does not undo external mutations that already completed; reconcile those through the owning integration.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.concurrence.com/developer-guide/guides/build-and-prove.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
