> For the complete documentation index, see [llms.txt](https://docs.wellcomecollection.org/request-for-comments-rfcs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.wellcomecollection.org/request-for-comments-rfcs/019-platform_reliability/reliability.md).

# Reliability

In order that we can be confident that what we deploy will behave as we expect we should look at:

## Pipeline reliability

In order to verify that pipeline deployments will behave and are behaving as expected we should:

* Test pipeline changes that require re-indexes before new indexes are promoted into production view.
* Test the pipeline is performing as expected when updates flow through it.

### Pipeline reindexing

In order that we can quickly test the behaviour of the catalogue pipeline, we should:

* Reduce reindex costs
* Reduce reindex time
* Couple reindexes with pipeline deployments (specifically model changes).

## Front-end reliability

In order to prevent regressions and errors in production we should:

* Provide acceptance tests that run before release to production.
* Provide component tests for individual UI components.


---

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.wellcomecollection.org/request-for-comments-rfcs/019-platform_reliability/reliability.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.