> For the complete documentation index, see [llms.txt](https://docs.nfh.global/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nfh.global/product-documentation/products/observability-audit.md). # Observability & Audit End-to-end transaction tracing and verifiable audit trails. The cryptographic record of what happened — across instances, across networks, across time. Every signed exchange leaves an anchor; every anchor is verifiable. ## What it gives you * **Commitment-chain anchors** — periodic hashes of each instance's state, published to NFH fabric. * **End-to-end traces** — span every hop of a transaction across services, instances, and adapters. * **Verifiable audit trails** — replayable, signed, and cryptographically grounded. * **Anchoring proofs** — BLAKE2 + chain-anchored proofs for any record. * **Selective disclosure** — share an audit slice without revealing private state. ## Where it sits * **Service NFH runs** — the anchor-acceptance and aggregation surface. * **Protocol NFH defines** — anchoring formats and audit-record schemas. ## Use it for * Regulators and auditors needing a tamper-evident trail. * Resolving disputes without surrendering private state. * Proving provenance, custody, and chain-of-events for any asset or transaction. * Compliance reporting with cryptographic guarantees. ## Standards alignment OpenTelemetry · BLAKE2 hashing · open anchoring protocols. *** This service is also NFH fabric's **signal-and-health surface** — network telemetry (flows, instance health, supply summaries) for operators and participants, alongside the cryptographic audit trail. --- # 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.nfh.global/product-documentation/products/observability-audit.md?ask=&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.