---
name: bijection-operations
description: "Evaluate and integrate the Operations component with Bijection."
---

# Operations

Component-owned business intentions, candidates, independent decisions, participant consent and atomic acceptance receipts over ordinary retained mutations.

- Package: @bijectionhq/operations
- Category: Bijection Components
- Status: Included
- License: Not specified
- Bijection source (repository access required): https://github.com/bijectionhq/operations/tree/8cea744cc8b85f66b01e59c7a53c8e298b14f32d
- Upstream: https://github.com/bijectionhq/operations
- Documentation: https://docs.bijection.com/components/using
- Directory: https://bijection.com/components/operations

## Get the source

Bijection repository access is required. Request access at https://bijection.com/contact.

```sh
git clone https://github.com/bijectionhq/operations.git
cd operations
git checkout 8cea744cc8b85f66b01e59c7a53c8e298b14f32d
```

## Before using this component

Read the package README at the recorded revision for setup, dependencies, and API examples. Upstream documentation describes the original package and may differ from the Bijection adaptation. This source is included in Bijection's workspace. Catalog inclusion does not establish npm availability or runtime qualification. Check compatibility with your SDK and deployment before adoption. External providers run their own compute.

## Integration workflow

1. Read the source README and package manifest at the recorded revision.
2. Confirm the required SDK, dependency availability, and runtime compatibility.
3. Follow the component's documented setup and configuration. Never invent an npm install command from a catalog package name.
4. Keep credentials in the project's existing secret store.
5. Follow the project's execution rules for verification and report what was actually checked.