> For the complete documentation index, see [llms.txt](https://docs.veedna.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.veedna.com/gold-open-source-gos/gold-packages/what-is-lineaje-gold-open-source-gos-artifactory-proxy/modes-of-operation.md).

# Modes of Operation

The Lineaje GOS Artifactory Proxy ships with two operating modes, allowing teams to adopt it incrementally without disrupting existing delivery pipelines. 

## Enforce Mode 

In Enforce mode, the proxy strictly blocks the download of any package that does not meet the GOS criteria or fails a custom policy check. The build receives an HTTP 4XX error response and the download is stopped. This is the recommended steady-state operating mode for production build pipelines where supply chain integrity is non-negotiable. 

* Build fails fast when a non-gold dependency is requested 
* Stops unsafe code before it can be compiled, tested, or deployed 
* Provides an immutable audit trail of every blocked attempt 
* Policy violation details are logged to the Lineaje platform and surfaced in build output 

## Observe Mode 

In Observe mode, all artifact downloads are permitted regardless of GOS status or policy violations. However, every non-compliant download is recorded, classified, and reported on the Lineaje GOS dashboard. Observe mode is ideal for: 

* Initial onboarding and baselining — understand your current open source risk posture before enforcing 
* Teams that need visibility without yet committing to hard enforcement 
* Audit and compliance reporting without disrupting existing build pipelines 
* Gradually building the organizational muscle to move toward Enforce mode 

{% hint style="danger" %}
Observe mode does not prevent unsafe packages from entering your build. It is a transitional tool. Lineaje recommends transitioning to Enforce mode within 90 days of initial deployment. 
{% endhint %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.veedna.com/gold-open-source-gos/gold-packages/what-is-lineaje-gold-open-source-gos-artifactory-proxy/modes-of-operation.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.