Portugal Startups
The Portuguese startup ecosystem — companies, founders, investors, institutions and the events where they meet — mapped on a graph built from primary sources that are frozen and hashed. The first beat is Startup Summit Lisbon 2026, which opens in 4 days. Every claim on this section walks back to a hashed copy of somebody else’s page.
Beta, agent-produced, human-reviewed. The research, extraction and drafting are done by software agents. Dinis Cruz is the named editor of record and reads every page before it publishes. That is a person taking responsibility, not a legal opinion — there has been no legal review.
Every claim here walks back to bytes we hold. Each source page was fetched, frozen to a dated snapshot in this repository and hashed with SHA-256. We do not read the live site at publish time, so a page cannot change under a claim without the change showing up as a new hash.
We report what others have published. This publication originates no facts about any company or person, makes no assessment of anybody, and does not explain why a name appears or disappears from somebody else’s list. The full limits →
If you are named on this site — what is held about you, why, and how to have it removed without giving a reason: your data →
The wire
Five names arrived and one left
Between 8 and 13 September the published speaker list for Startup Summit Lisbon 2026 went from 60 to 64. We have both copies and both hashes, which is the only reason anyone can now say that.
2026-09-13 · 3 sources · primary
Two names for three stages
The agenda calls them the Unicorn Stage and the Impact Stage. The AI-summary page calls them the Main Stage and the Startup Stage. Both are published by the same event on the same site today.
2026-09-13 · 4 sources · primary
What this is
A publication mapping the Portuguese startup ecosystem — companies, founders, investors, institutions, events — on a graph built from primary sources that have been frozen and hashed. It is scoped the way the 12 May 2026 brief argued a first instance should be:
An event is that criterion in miniature. A conference that publishes its own speaker list has a closeable entity graph: you can name every speaker, every organisation behind them, every stage and every session, and then keep that map current as it moves. So the first beat is one event, and the map is finished rather than sampled.
What is different here
This site already runs The Governance Wire, and the two publications are deliberately not the same shape:
| The Governance Wire | Portugal Startups | |
|---|---|---|
| Sources | secondary nothing frozen or hashed | primary every page frozen and hashed |
| Human review | None — deliberately | Dinis Cruz, named editor of record |
| Subjects | Regulatory texts and bodies | Named people and named companies — which is why the review exists |
| The blocked door | frozen — never passed by anything |
Open. This is the ingestion path that section specifies and cannot run |
The second row is the important one. A publication that names individuals in a small ecosystem, where everyone will read what is written about them and many will be in the same room, should not publish unread. Open question 5 of the original brief — who is the editor of record — is answered here →
The list is moving
Between the two snapshots this section holds, the published speaker list went from 60 to 64: 5 names added and 1 removed, in 4 days before the doors open. Both copies are in this repository and both are hashed, so the diff is checkable rather than asserted. What changed, name by name →
For an agent
A publication about the Portuguese startup ecosystem, first beat Startup Summit Lisbon 2026. Sources here are primary: every page was fetched, frozen to /portugal/sources/frozen/<date>/ and hashed with SHA-256, and the register at /portugal/data/sources.json carries every hash. Machine surfaces: people.json, orgs.json, event.json, changes.json, checks.json. This publication reports what the event has published about itself and does not assess it. Speaker biographies are deliberately NOT reproduced — follow the speaker page link on each node.