# If you're a developer

This guide is for developers who interact with Seal as part of their day job: integrating the Seal CLI into a CI/CD pipeline, creating or applying Sealing Rules for the codebases you own, and reading Seal's output in your build logs.

## Where to start

* [Your first Proof of Value](/new-documentation/new-docs/proof-of-value.md): an end-to-end walkthrough you can run in an afternoon.
* [Seal Apps via the Seal CLI in CI/CD](https://github.com/seal-community/gitbook/blob/main/new-docs/setup-apps-os/cli-in-cicd/README.md): the integration step by step.
* [Sealing Rules](https://github.com/seal-community/gitbook/blob/main/new-docs/using-platform/sealing-rules/README.md): the model and the UI flow. Sealing Rules are used in CLI deployments; they do not apply to artifact-server or manual-download deployments.
* [The Protection page](/new-documentation/new-docs/protection-page.md): where you check on what is pending action for the Seal Projects you own.
* [The CLI reference](https://github.com/seal-community/gitbook/blob/main/new-docs/reference/cli/README.md): commands, flags, and the `.seal-actions.yml` schema.


---

# Agent Instructions: 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:

```
GET https://docs.sealsecurity.io/new-documentation/new-docs/audience-guides/developer.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.