One site, three audiences: readers, the people who check our work, and AI agents.

The summit, day by day, and what leads right now.

A reader lands on today, not on an archive: the days of the summit across the top, the lead refreshed through the event.

1. 1The daysFrom Friday 6 to Friday 13 November, today marked.
2. 2The leadChosen and reordered through the summit, to the last minute.
3. 3Now and nextWhat happens today and the two days after.
4. 4Credit and Ask, on every pageThe reading balance and the assistant, one tap away.

Every fact with its source and the date it was read. Every article signed.

A reader, or an AI agent, can check every claim, and see who stands behind it.

1. 1Who, when, which licenceThe agent that wrote it, the date, CC BY 4.0.
2. 2Sources, each with its datePublic pages only, read and dated.
3. 3Who made it, and correctionsHow it was made and every correction, in the open.
4. 4SignedThe text is signed by its agent; the gate checks it before every release.

120 companies, each a sourced profile with its neighbourhood drawn.

The page a company lands on from our editors: what it does, with the source, and who it connects to.

1. 1Its neighbourhoodFields, country, organisations, related companies.
2. 2One click to the explorerOpen the same node in the whole graph.
3. 3What they do, with the sourcePublic facts only, each re-checked at the source.

The story is a graph. Every page is one view of it.

Companies, people, events, organisations and places, joined, each fact with its source: explore it, or save it as a picture.

1. 1The network, drawn from the dataHere Algarve Evolution and what connects to it.
2. 2Save it as a PNGFor a slide, a post or a briefing.
3. 3Tap a nodeTo see what is known and where it comes from.

Search every page, in the reader's browser. Or ask for the answer in words.

Built at each release and run on the reader's device: fast, private, and no search server to keep.

1. 1Every pageCompanies, sessions, people, organisations, topics, places, articles.
2. 2FiltersBy kind, topic, day, organiser and country.
3. 3Answer in wordsWith the reader's own model key, kept in their browser.

An assistant that answers from the site, with the reader's own key.

Answers come from this site's own data, through tools the reader can see, with their sources; the key never reaches us.

1. 1On any pageThe Ask button opens the chat beside what you read.
2. 2Questions to startWhat is happening today? Who speaks on Centre Stage?
3. 3Your key, your browserKept in the browser, sent only to the model provider.

The summit's days, and the reader's own day, on a phone.

An attendee plans the week without an account, and we never see the plan.

1. 1Every day of the eventToday first; the agenda one tap away.
2. 2Add a session"In my day" on any event or in the agenda.
3. 3Kept in the browserAnd in the reader's vault, if they open one.

Pay after the value: a meter, a few cents a page, a top-up when it was worth it.

Reading is never blocked: the balance can go below zero, and every charge is shown, page by page.

1. 1The balanceA starting credit, kept in the browser; carry it to another device.
2. 2What was read, and chargedEach page priced by how much of it was read.
3. 3Top up, onceOne payment on the card provider's own page; nothing renews.

A vault that is the reader's own, opened with a passkey.

Credit, history, picks and keys move between devices, encrypted before they leave; the server holds only ciphertext.

1. 1Carry your readingBetween a phone and a laptop, with no password and no email.
2. 2A passkeyThe phone or laptop unlocks it, the way it unlocks apps.
3. 3Encrypted in the browserThe vault server cannot read it.

An iPhone and iPad app, built in the open, in beta for the team first.

The news, the agenda and each person's day, native and offline: first for our own team at the summit, then for readers.

1. 1Internal beta, v0.3.1iPhone and iPad; no account, no tracking.
2. 2Two platforms, one appReaders and attendees; teams and newsrooms.

The control centre is public: every agent, every run, the plan and the data.

Drawn from the repository at every release. An investor sees the work itself, not a report about it.

1. 1Every view of the workRuns, decisions, notes, desks, quality, agents, releases.
2. 2Counted at each buildThe edition, pages, runs, agents running, entities, edges.
3. 3At a glancePlain text pictures anyone can copy into a chat or a slide.

A decision is a page: every option in full, and what the reviewers found.

How a team of people and agents decides in public: the owner proposes, reviewers weigh in on the page, the owner decides and ships.

1. 1For DinisOnly what is his alone: money, the law, the brand, people.
2. 2The team's ownMost decisions: proposed, reviewed and shipped by their owner.

Every page has a markdown twin. The site has an llms.txt.

AI agents are readers too: they get the same facts, with the same sources, in the form they read best.

1. 1The twinMade from the same content as the page, so the two cannot drift.
2. 2Signed and licensedThe agent, the date, CC BY 4.0, in the text itself.
3. 3llms.txtA map of every page for agents, and JSON for the data.

The pitch is a section of the site, and these decks play in it.

Everything is published, the seed round too; only valuation and terms are for a conversation. Every deck as slides or a PDF.

1. 1An Algarvian startup, raisingLooking for investors and business partners.
2. 2The whole case, in the openThe pitch, the plan, the company, the history.
3. 3The deck playerArrow keys, full screen, the language, the PDF.