> 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/governance.md).

# Governance & auditability

## Maker–checker, enforced by the database

Risk parameters, limit thresholds, haircuts and instrument mappings change only through versioned configuration proposals approved by a *different* administrator. Self-approval is refused by a database constraint — not a UI rule. Every version records who proposed, who approved, the change note and the effective date; every run records which versions governed it.

## The audit trail

Every mutation — config changes, NAV entries, user invitations, role changes, key operations, position attestations, even every ops-console view of tenant data — writes an audit record with actor, action, before and after. The trail is insert-only and visible in the app to the auditor role.

## Reproducibility as a nightly control

Each official run writes an immutable manifest: input hashes, configuration version ids, code commit, data-quality findings. Every night the platform re-derives its own latest run and compares bit-for-bit; a mismatch raises an incident alert. This is the product's core claim, tested daily against itself.

## Roles

| Role         | Can                                                                                    |
| ------------ | -------------------------------------------------------------------------------------- |
| Viewer       | Read the panel and reports                                                             |
| Auditor      | Viewer + the full audit trail and configuration history                                |
| Risk manager | Propose configuration changes, acknowledge breaches, enter NAV and off-venue positions |
| Admin        | All of the above + approve others' proposals, manage users and venue keys              |

Nobody can change their own role. Approval rights and proposal rights are deliberately separable.

## Disclosed limitations

Where the platform uses judgment in place of measurement (today: the liquidity-cost tiers; proxy price series where noted), the limitation is stated in the data model, the manifest, the model documentation and on the face of every affected report — with the remediation path and its trigger.


---

# 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/governance.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.