> 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/cip-editors-stipend.md).

# CIP Editors Stipend

Part of WP2 — Protocol Governance and Evolution in the TSC Support 2026 budget, a Cardano treasury grant administered by Intersect.

### Purpose

Every Cardano Improvement Proposal goes through the CIPs repository, and the speed and care of review there decides how quickly good ideas become standards. This programme funds two CIP editors so that reviews stay frequent and thorough, particularly as Dijkstra hard fork work increases the load.

### Budget and limits

| Item         | Detail                                                         |
| ------------ | -------------------------------------------------------------- |
| Budget       | 384,000 ADA (≈ $96,000 at the proposal's $0.25 reference rate) |
| Seats        | 2 funded editors                                               |
| Compensation | 16,000 ADA per editor per month                                |
| Settlement   | ADA                                                            |

Compensation is fixed in ADA and does not track the USD price.

### The role

* Responsive at least five days a week; otherwise hours are flexible
* Fortnightly CIP review meetings are mandatory
* The two editors share review topics as evenly as possible
* Each editor publishes a short monthly report on their work
* Expect around 10–12 hours a week, more around review meetings

### Who can take part

The role suits people who already know the CIPs repository. Editors need:

* Fluency with GitHub pull requests, in the browser and locally (git or gh)
* Experience writing or reviewing CIPs or CPSs
* Working knowledge of Cardano's main development areas, and willingness to learn the rest
* The ability to discuss proposals critically in English without AI assistance, record others' views fairly, and judge when consensus has been reached

Seats are non-exclusive: there is no forced rotation, but any vacancy is filled through open recruitment against these criteria, and editors are reconfirmed at the interim review.

### Selection

Recruitment for this period is complete.

**Current editors:** [Robert Phair](https://github.com/rphair), [Adam Dean](https://github.com/crypto2099)

Current Editor List: [CIPs README](https://github.com/cardano-foundation/CIPs#:~:text=back%20to%20life.-,Editors,-Name)

### Conflict of interest

Editors disclose relevant affiliations on appointment and refresh the disclosure at the interim review, and recuse themselves from CIPs where they have a conflict.

### Payment

Paid monthly in ADA against evidence of active participation that month — the editor's monthly report, review meeting attendance, and documented reviews.

### Outputs

* Reviews of CIPs and CPSs in the [CIPs repository](https://github.com/cardano-foundation/CIPs)
* A monthly report from each editor, published \[location]

### Reporting

* **Interim review:** \[date, \~Month 6]
* **Year-end review:** Month 12 delivery and accountability report

Both are published on this GitBook.

### Contact

Questions: [Email TSC](mailto:technical-steering-committee@intersectmbo.org)  Subject: "CIP Editors".

Program lead: Kevin Hammond (TSC Chair)


---

# 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/cip-editors-stipend.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.
