> For the complete documentation index, see [llms.txt](https://visi-digital-internasional.gitbook.io/geo-prospector/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://visi-digital-internasional.gitbook.io/geo-prospector/updates-and-security/build-integrity.md).

# Release integrity

Official builds use a Security Anchor to validate product identity and protected application files.

## Manifest identity

* Product: `geo_prospector`
* Edition: `established`
* Batch: `0`
* Version: `6.7.15.1`
* Public-key fingerprint: `67B64034CD77BE4018EC8102D36F8469548EE0DDCFE87CC322D26DDCFE036A35`

## Required security-anchor files

The installed application directory includes:

* `security_anchor_manifest.json`
* `security_anchor_manifest.sig`

The signed manifest contains protected file identities and SHA-256 hashes. The signature is verified with the embedded Ed25519 public key.

## Protected release components

* Product and edition identity
* Application version identity
* Signed manifest
* Ed25519 signature
* Public-key fingerprint
* SHA-256 file inventory
* Main executable and protected runtime files

A release-integrity warning can appear when files are missing, modified, mismatched, or copied incompletely.

## Recovery

1. Close Geo Prospector.
2. Download the official installer.
3. Reinstall the complete application.
4. Do not replace individual files.
5. Reopen the application and verify the installed version.

{% hint style="danger" %}
The private signing key and private seed are not distributed with Geo Prospector and must never be shared.
{% 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 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://visi-digital-internasional.gitbook.io/geo-prospector/updates-and-security/build-integrity.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.