> For the complete documentation index, see [llms.txt](https://board.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://board.docs.intersectmbo.org/intersect-board-meetings/2024-board-minutes/31-jan-2024-intersect-board-meeting.md).

# 31 Jan 2024 - Intersect board meeting

Minutes: 1000GMT 31 January 2024

## Attendees

<table><thead><tr><th width="72">#</th><th width="139">Board Seat</th><th>Designator</th><th>Alternative</th><th>Observer</th></tr></thead><tbody><tr><td>1</td><td>IOG</td><td>Tim Harrison </td><td><br></td><td>Tamara Haasen</td></tr><tr><td>2</td><td>EMURGO</td><td>Nikhil Joshi </td><td>Amar Singh</td><td><br></td></tr><tr><td>3</td><td><br></td><td><br></td><td><br></td><td>Steve Lupien </td></tr><tr><td>4</td><td>Intersect</td><td>Nigel Hemsley</td><td><br></td><td><br></td></tr><tr><td><br></td><td>Secretary</td><td>Lawrence Clark</td><td><br></td><td><br></td></tr><tr><td><br></td><td>Treasure</td><td>Dan Singleman</td><td><br></td><td><br></td></tr></tbody></table>

There were no absentees.

As noted in the Intersect Bylaws, for a board meeting to be a quorum, at least the greater of one-third (1/3) of the then-serving Directors or two (2) Directors shall constitute a quorum for the transaction of business at any meeting of the Board of Directors. If less than a majority of the Directors are present at said meeting, a Director present may adjourn the meeting from time to time without further notice.

Was a quorum established? Yes.

***

## **Proceedings**

The meeting was called to order by the Chair Nikhil Joshi on the 31 January 2024 at 10:00 UTC.

All cameras were on, and all participants confirmed their adherence to the Directors' Conflict of Interest policy.&#x20;

The secretary noted the agenda and proceeded with the meeting.

### Review of business plan updates following the January team workshop

Nigel Hemsley, COO, provided an update to the board on the team workshop and his organization of the company to the Intersect Business Plan.  Areas covered include:

* Intersect Operational areas and their plans for 2024
* Intersect Budget&#x20;
* DevTrust Budget

Motion taken by unanimous decision to approve the Business Plan&#x20;

### Finance Review

Dan Singleman provided an overview of the DevTrust and Intersect financial accounts. All remain within agreed levels.

### Update on Educational Board member

It was noted that Steve Lupien was onboarding as an Intersect Board Member and will have full voting rights for the February board meeting.

### Director Remuneration

The research was carried out to validate the 8th December 2024 agreed sum for director remuneration. &#x20;

Motion taken by unanimous decision to proceed with cirector remuneration&#x20;

### Director and Officers Insurance

An update was provided to the board on finding a supplier for D\&O Insurance. Action remains with the Secretary to find a supply by the February board meeting.&#x20;

### Non-Executive Director (NED) Training

An update was provided to the board on finding a company that could provide Non-Executive Training to the Intersect board. It was agreed that training should be around and booked by the February board meeting.

### Commercial Adoption

A discussion was held around providing Intersect the mandate to coordinate certain commercial activities on behalf of the ecosystem.

Motion taken by unanimous decision to proceed with a Commercial Adoption working group.

**The Chair brought the meeting to a close at 11:10 UTC on 31 January 2024.**


---

# 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://board.docs.intersectmbo.org/intersect-board-meetings/2024-board-minutes/31-jan-2024-intersect-board-meeting.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.