> For the complete documentation index, see [llms.txt](https://docs.fortemis.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fortemis.io/operations.md).

# Operations & reliability

## The nightly cycle (00:15 UTC)

Aggregate the day's spread observations → refresh independent data (CoinGecko) → fetch market data → strike the official run from the pre-midnight position snapshot → write reports and the immutable manifest → **re-derive yesterday's run and verify bit-for-bit** → reconcile positions. Any failure alarms; a silent night is impossible by construction (missing heartbeat data is itself treated as an alarm condition).

## Failure philosophy

* A **dangerous** input (a key that can trade) stops the platform.
* A **broken** input (an expired key, a missing price) degrades the affected slice visibly and loudly while everything else continues.
* A **suspect** output (content-hash mismatch, reproducibility failure) refuses to serve rather than serving something unverifiable.

## Monitoring the monitor

CloudWatch heartbeat alarms treat missing data as breaching; batch task failures page directly; the ops console shows per-tenant health where a stale row displays stale — never green.

## Deployments

Rolling deployments with health-gated cutover. The current architecture carries a brief switchover window on the live service; the web/compute split (in progress) removes client-visible downtime entirely, with the freshness machine bridging compute restarts honestly.


---

# 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.fortemis.io/operations.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.
