Skip to content

Dave Thornton

Partner

Reference

Shared context layer

The spine of the hub. Every capability contributes to it, and every consumer, human or machine, draws from the same picture.

Board pack summaries

Periodic company narrative and key decisions, generated on every pack.

Extracted metrics

Time-series financial and operating data, with confidence and provenance attached.

News feeds

External market intelligence: company, industry, competitor and acquirer.

Notes and corrections

Human-added context, commitments and corrections that feed back into the picture.

The notes below are not real. There is no context_note table and none is scheduled, so nothing can be written, read or filtered. Everything else on this page is workshop documentation rather than data: the four sources, the user roster and the proposed API describe what the firm asked for, and those are as real as any decision record here.

Notes, commitments and corrections

What has been promised, and what needs following up.

No notes, and nowhere to put one. The vocabulary above is the one the workshop settled on, kept visible so the intended shape is legible; the table behind it does not exist.

Headless access

Proposed, not built. Claude first, then other API surfaces.

  • GET/v1/companies/{id}/context

    Chatbot

    The full shared context for a company: latest summary, current metrics, recent news and notes.

  • GET/v1/metrics/export

    Data warehouse

    Nightly pull of normalised metric values across the portfolio, with confidence and review status.

  • POST/v1/companies/{id}/notes

    Chatbot and UI

    Adds a context note that feeds back into the shared layer.

  • GET/v1/board-packs/{id}/summary

    Chatbot

    The latest approved summary for a board pack, with citations back to source pages.

Permissions

Raised at the workshop and still open.

All data for all users, or walls per team? The hub currently assumes a flat model where every partner and non-partner sees the whole portfolio. Company- or team-level access walls are an open design decision, and there is no authentication to enforce either answer yet.

Who is connected

Human surfaces and headless consumers, drawing on the same layer.

Partner investors

Full portfolio visibility, board meeting prep

  • Dave
  • Jeff
  • Lawrence
  • Jerry
  • Isabella
  • Kevin

Non-partner investors

Portfolio access; exact needs still being defined

  • Adam
  • Andrew
  • Ollie

Headless and service accounts

  • Data Warehouse

    Pulls extracted metrics nightly

  • Claude (MCP client)

    Conversational search over the shared layer

This roster is a record of who the firm said would use the hub. It is not an account list: there is no sign-in anywhere in this system yet.