> ## Documentation Index
> Fetch the complete documentation index at: https://docs.bugspray.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Organize your product catalog

> Give people and agents a shared description of the product.

Use the catalog to describe **what your product should do**, independently of how it is tested.

| Record | Example | Purpose |
| - | - | - |
| Product | Example Desk | The application whose expectations you maintain |
| Area | Views | A useful grouping within that product |
| Workflow | Save and reopen a view | A durable expected user behavior |
| Saved definition | The workflow text saved today | The exact expectation a later run can reference |

## Create a useful hierarchy

In **Products**, create a product with a short description. Open it and create an area named for a capability people recognize. In that area, add a workflow with a behavior and expected result. You can add prerequisites and ordered steps, but a reference video or test suite is not required.

Prefer “Save and reopen a view” over “Views tests.” A workflow should help a reviewer decide what to observe. Keep implementation details such as a test filename in the suite manifest, not the product expectation.

## Search and share

Search workflows within a product, optionally within an area. Search matches current names and behavior; open a result to read full expectations. Default list pages contain 20 records, with a maximum of 100 and continuation cursors. Search is a live read, so automated consumers should deduplicate stable IDs if records change during pagination.

Share the workflow's direct link. Its stable identity survives renaming and moves within its product. For an investigation or validation record, also retain the exact saved definition ID rather than assuming the current text is unchanged.

## Archive without losing context

Archive a workflow when it is no longer active. It disappears from ordinary active discovery, while direct detail and history remain readable. Archiving an area or product makes its descendants effectively inactive without overwriting their independent archive state.

Restore ancestors before restoring a descendant. Restoring a parent does not reactivate independently archived children. Active names must be unique within their parent; a restore may need a new name to resolve a collision. Archive is a lifecycle action, not deletion or a test result.

## Work with other editors

Read-only members browse. Reviewer-or-higher members and authorized automation can author. Saves use the last-read `expectedVersion`; concurrent edits require rereading and reconciling your draft. Retry an ambiguous save using the same `requestId` and content, rather than creating a second operation.

Continue with [workflow authoring and history](https://docs.bugspray.io/concepts/workflows.md) or [connect existing tests](https://docs.bugspray.io/concepts/test-suites.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.