Dear Peter,

We've done a few things below, across four tabs. This document (the first tab) explains what we're thinking and what we need from you. The second tab is a draft of what a profile could look like. The third is some working notes. The fourth is just a first start on what a basic site idea could look like, until we talk it through properly.

Good to be working with you. Before anything goes out under your name anywhere, we run the same verification pass on every named contributor across our sites. Here's what came back, and a few things we'd like your steer on.

What your byline sits on

You're a genuine co-author when you write with us, not a name attached to something we've written elsewhere. That's a stronger position than a "reviewed by" credit, and it's the honest one when the words are actually yours. It also means the same standard applies as everywhere else on our sites: everything under your name has to hold up if someone, or something, checks it.

We've already done the checking

Companies House confirms you as Director of Meridian Risk Solutions Limited (04259588), 15 March 2019 to 30 April 2021, dates matching what you have on LinkedIn. We also found two directorships that aren't on your LinkedIn at all: Blu Niche Risk Services Limited (December 2021 to March 2026) and Eminence Risk Services Limited, trading as Nivante (March 2024 until it dissolved in May 2025). Press coverage independently ties Nivante to NuVenture's second MGA launch, in the care sector, which if anything backs up the "helped launch three MGAs" story rather than needing it. One small correction: the register shows Argenta Holdings Limited, not "plc" as it reads on LinkedIn, an easy fix. Nothing adverse anywhere: no disqualifications, no insolvency notices, no CCJs, clean throughout.

"Agile Risk Consulting" isn't a registered company, which lines up exactly with what you told Adam: your own trading name as a sole trader for the interim FD and CFO work, not a separate firm. One thing we couldn't settle either way: the FCA-approved-person status. The public register only publishes Senior Manager Functions, and Certification Regime roles (which is plausibly what yours was) never appear on it at all, so this needs your own reference number before we'd state it as fact rather than paraphrase it.

We also found the Risk Code Hub. It's genuinely good: real structure, honest sourcing, a confidence-tiering system most AI-built sites don't bother with. Right now it's basically invisible (zero stars on the repo) purely because nothing points to it yet, which is a shame given the reach the LinkedIn post about it got.

And we've now read "It isn't tokens times a number," the Arkai-Optrix piece. It's genuinely excellent: prompt caching and the KV cache explained properly, worked through a software sprint and a Big Four deal room, well sourced throughout. It's also finance and AI economics, nothing to do with insurance, which fits: on the site we're building, Agile Risk Consulting leads as your main practice, and Arkai-Optrix sits underneath it for the data, research and programmes side, not equal billing. Currently sitting at 0 followers on the LinkedIn company page, which undersells it badly. Correct us if that structure's wrong, but that's what we're building to.

Two things worth having in any bio that aren't there yet: your CIMA qualification (corroborated on BluNiche's own team page, though we'd want your preferred letters, ACMA or FCMA), and Loughborough University, which your LinkedIn skill endorsements point to but never states outright.

One more thing we'd pulled from your own LinkedIn "About" section but hadn't used yet: your own framing of your specialism as businesses under £10m turnover and corporate-VC-backed startups, plus the working capital and MGA-sale achievements. If we're going to put you in front of an SME and mid-market audience rather than an insurance one, that's the material that actually does the work, not the Lloyd's-market detail. Worth building the bio around that rather than leaving it as a LinkedIn-only line.

What we'd like from you

1. Your FCA reference number, if you have one. The only way we can state "FCA-approved" as a checked fact rather than a paraphrase.
2. A steer on Eminence Risk Services / Nivante. Worth including, or was leaving it off LinkedIn deliberate?
3. Whether ChainThat is worth naming directly in a bio, or better left out.
4. A headshot, and however you'd like the Agile Risk Consulting years described.
5. FD or CFO, pick one as the phrase to use everywhere. FD is the one that's actually on the record (the Meridian directorship), CFO reads bigger but isn't a title you've held. Worth settling on one and using it consistently rather than the two interchangeably.
6. Loughborough: degree, subject and year. Your LinkedIn skill endorsements point at it (Corporate Strategy, Programming, Databases, Corporate Finance, Project Management) but never state it directly, and confirm ACMA or FCMA for the CIMA letters.

Everything else (the writing, the pages, the linking, the upkeep) is our work, not yours. That said, the door is always open: if anything has your name on it anywhere (press quotes, company posts, talks, awards, committee work, memberships, training you've delivered, courses beyond the IBM ones above) send it over, however minor it seems, and let us judge. We would far rather sift through fifty things and use ten than miss the one that matters. No deadline and no homework, whenever it's easy.

Why any of this matters

Google, and now ChatGPT, Perplexity and the other AI assistants, increasingly decide who to recommend based on whether a real, checkable person stands behind the content, not just what the content says. That's what's usually called E-E-A-T (experience, expertise, authoritativeness, trustworthiness), and it's become the main thing that separates a generic-sounding page from one these systems will actually cite.

The mechanism is simpler than it sounds. Underneath the visible page, there's a bit of code (technically called sameAs) that explicitly tells search engines and AI models "this LinkedIn, this GitHub, this ORCID, this Crunchbase page are all the same person." Right now your profiles exist but don't reference each other, so nothing ties them together. The point isn't tidiness for its own sake, it's connecting someone with real authority and linking it all together properly, so a search for "Peter Horncastle" resolves to one verified, consistent entity rather than a handful of disconnected pages. The same thing applies to anything else you've done or do in future, a podcast appearance, a YouTube interview, a conference talk, all of it links back the same way.

Building the record to match it

Don't do anything on the below yet. This is early brainstorming on our side, not a request, just where our thinking's at on how a public record could eventually match what you've actually done:

Where	Worth doing
LinkedIn (personal)	The Argenta plc/Ltd fix above, and maybe a line making clear Agile Risk Consulting is you trading solo, not a firm with staff, your call on the framing.
LinkedIn (Agile Risk Consulting)	No LinkedIn Company Page exists yet for the Agile Risk Consulting trading name (checked, nothing there to fix, just missing). Arkai-Optrix already has one, so LinkedIn's fine with a page for a trading name, not just an incorporated firm. When we build Arkai-Optrix, this is the same work again just pointed at the trading name rather than you personally, and it'd be ours to set up alongside the site, not yours to do separately.
ORCID	Free, five minutes, name's clear (no existing "Peter Horncastle" to clash with). Becomes the anchor if the Risk Code Hub ever turns into a proper citable paper.
GitHub	Already genuinely good. Pin Risk Code Hub, triangle-library and loss-ratio-cascade on your profile so it's not invisible unless someone already has the link.
Crunchbase	No existing page, quick to set up, the kind of thing AI models cross-reference for a professional bio.
Wikidata	Skip. Not worth the effort next to the above.

One more thing worth doing going forward: whatever you put out under your own name (GitHub projects, newsletter pieces, wherever), a consistent sign-off line back to who you are helps it all read as one person building a track record, rather than scattered anonymous work.

Private draft prepared for Peter Horncastle, August 2026.