> For the complete documentation index, see [llms.txt](https://committees.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://committees.docs.intersectmbo.org/intersect-technical-steering-committee/tsc-budget-2026-2027/independent-technical-review-pilot.md).

# Independent Technical Review Pilot

WP3 — Technical Review in the TSC Support 2026 budget, a Cardano treasury grant administered by Intersect.

### Purpose

DReps are asked to fund complex technical work with little independent advice on whether it is sound. This pilot provides short, independent technical reviews of core infrastructure treasury proposals, published before the vote, so DReps can see what experienced engineers think of a proposal's feasibility, cost and risks.

2026 is the set-up year: building the review framework and the reviewer pool, so that the pilot is ready to review proposals in the 2027 budget cycle.

### Budget and limits

| Item                   | Detail                                                         |
| ---------------------- | -------------------------------------------------------------- |
| Budget                 | 105,000 ADA (≈ $26,250 at the proposal's $0.25 reference rate) |
| Proposals              | Up to 35 core infrastructure proposals                         |
| Reviewers per proposal | About 3, working independently                                 |
| Payment                | 1,000 ADA per review                                           |
| Settlement             | ADA                                                            |

### What gets reviewed

**Core infrastructure** means any proposal intended to directly affect the operation of the blockchain — including new features, maintenance, security or operations — or tooling that is essential for users to access the blockchain. This includes nodes, chain indexers, software and hardware wallets, block explorers, SDKs, and bridges.

Proposers request a review; the WP3 lead confirms eligibility. Reviews prioritise **open-source** offerings. If there are more requests than capacity, open-source proposals come first, then proposals are ordered by how soon their governance vote is.

### How a review works

1. **Request and eligibility check.**
2. **Conflict-of-interest check.** TSC members and representatives of affiliated organisations recuse from anything linked to them. Recusals are recorded and published.
3. **Assignment** of about three independent reviewers.
4. **Review** against the published review framework, each reviewer writing separately.
5. **Factual check.** The proposer has \[48 hours] to point out factual errors. Reviewers' judgements are not changed.
6. **Publication** of all reviews in full, before the governance voting deadline.

Reviews assess the proposal; they do not tell DReps how to vote.

### Reviewers

Recruited openly against \[published criteria]. The pool's membership and affiliations are published, and no single organisation holds a majority of reviewing capacity. Reviewer assignments are made by the WP3 lead.

The TSC Chair is not part of the reviewer pool; the Chair's role is limited to oversight of the process.

**Current reviewer pool:** \[to be recruited]

### Payment

1,000 ADA per review, paid in ADA once the review is published.

### Reporting

* **Interim review (end of February 2027):** review framework published and reviewer pool in place
* **Year-end review (end of August 2027):** portfolio review and quality assessment of the pilot

Both are published on this GitBook.

### Contact

Questions or review requests: \[contact]

Program lead: Leandros Holleman


---

# 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://committees.docs.intersectmbo.org/intersect-technical-steering-committee/tsc-budget-2026-2027/independent-technical-review-pilot.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.
