# Getting Started

RECAP captures experimental provenance through resources, process templates, and process runs. Start with the local workflow, then use the remote workflow when a RECAP server owns the database.


# Find the right documentation

RECAP documentation is organized around four complementary ways to use the documentation:

- **Getting Started** provides guided lessons for learning RECAP by doing. Begin with [Complete Provenance Workflow](../../docs/getting-started/complete-provenance-workflow.md), then use the shorter [Quick Start: Create and Store Data Locally](../../docs/how-to/quick-start-create-and-store-data-locally.md) when you need a task recipe.
- **How-To Guides** provide focused procedures for users who need to complete a specific task. Use [How-To Guides](../../docs/how-to/index.md) for templates, servers, queries, authentication, and provenance operations.
- **Explanation** describes how RECAP works and why its architecture matters. Read [Explanation](../../docs/explanation/index.md) when you need concepts before choosing an implementation approach.
- **Tutorials** show complete domain workflows from setup through working code. Browse [Tutorials](../../docs/tutorials/index.md) when you want a guided path.
- **Reference** lists generated public APIs, schemas, query families, and builder methods. Browse [API Reference](../../reference/index.md) for exact signatures and model fields.


# Choose a workflow

- [Quick start: create and store data locally](../../docs/how-to/quick-start-create-and-store-data-locally.md) with SQLite.
- [Use a remote RECAP server](../../docs/how-to/setup-recap-server.md) with REST query/read and command transports. Requests use ordinary JSON; local and remote QueryDSL, canonical identity, and load-aware models remain aligned.