> For the complete documentation index, see [llms.txt](https://cifer.gitbook.io/cifer-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cifer.gitbook.io/cifer-docs/documentation/cifer-sdk/web3-integration/high-level-flows.md).

# High-level flows

The `flows` namespace combines repeated lower-level operations into coherent plans. It is useful for secret creation, readiness checks, encryption, storage, retrieval, and decryption workflows.

## Plan and execute

A flow can separate planning from execution. Planning lets an application inspect the required reads, signatures, transactions, and waits. Execution runs those steps through a context containing the signer, read client, Blackbox URL, chain, transaction executor, and optional logger.

## Recommended use

* Use lower-level namespaces when your product needs precise control over each step.
* Use flows when the workflow is standard and you want consistent retries and sequencing.
* Surface every wallet transaction to the user before execution.
* Persist resumable state for steps that wait on confirmations, secret readiness, or file jobs.
* Pass a logger only to a controlled telemetry function; the SDK does not log by default.

Flows do not remove the need for product-level cancellation, timeouts, idempotency, or error messages.


---

# 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://cifer.gitbook.io/cifer-docs/documentation/cifer-sdk/web3-integration/high-level-flows.md?ask=<question>&goal=<endgoal>
```

`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.