> For the complete documentation index, see [llms.txt](https://docs.intersectmbo.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.intersectmbo.org/intersect-knowledge-base/archive/funding-administration-archive/intersect-administration-policies.md).

# Intersect Administration Policies

{% hint style="danger" %}
**ARCHIVED**

This page has been archived. It's content might be outdated.
{% endhint %}

* [**Administration Financial Audit Policy**](/intersect-knowledge-base/archive/funding-administration-archive/intersect-administration-policies/administration-financial-audit-policy.md)**:** To ensure a consistent understanding of Intersect’s policy regarding financial auditing, where Intersect is acting as an administrator for public proposals in accordance with the Cardano Constitution.
* [**Delivery Assurance Process and Best Practice Policy**](/intersect-knowledge-base/archive/funding-administration-archive/intersect-administration-policies/delivery-assurance-process-and-best-practice-policy.md)**:** To provide guidance to all beneficiaries working under contracts administered by Intersect, including smart contracts and legal contracts, to ensure delivery is executed transparently, with accountability, and in line with community expectations.
* [**Due Diligence Policy**](/intersect-knowledge-base/archive/funding-administration-archive/intersect-administration-policies/due-diligence-policy.md)**:** To establish a structured, comprehensive, and iterative framework for thoroughly investigating and verifying information before Intersect commits to new contractual relationships, transactions, or projects with new individuals or businesses.
* [**Technical Review Policy**](/intersect-knowledge-base/archive/funding-administration-archive/intersect-administration-policies/technical-review-policy.md)**:** To outline requirements, guidance where necessary, for review and technical audit of milestones (documents, designs, code, or other technical project artefacts) to ensure that the deliverables do not endanger the security, functionality, performance or long-term sustainability of the Cardano Blockchain.
* [**Wallet Address Change Policy**](broken://pages/1hLHlKRTZjoM9rs8ZflB)**:** To ensure the secure and verified update of wallet addresses listed in vendor contracts after contract execution. This policy protects against unauthorized changes and potential fraud by enforcing a standardized identity verification process prior to approving any wallet address modification.
* [**Committee Member Travel & Expense Policy**](/intersect-knowledge-base/archive/funding-administration-archive/intersect-administration-policies/committee-member-travel-and-expense-policy.md)**:** This policy provides clear guidance for Intersect Committee members and other approved external participants on travel and related expenses incurred on behalf of Intersect under contracts relating to Intersect Committees. It sets out rules for planning, booking, approvals, reimbursements, and per diem allowances to ensure fair, transparent, and cost-effective financial practices.


---

# 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.intersectmbo.org/intersect-knowledge-base/archive/funding-administration-archive/intersect-administration-policies.md?ask=<question>&goal=<user_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.