Home / Articles / PrompTugal.news, the next phase: a roadmap for the team that ran it at Web Summit and the people who want to join, from outreach and contributors to local news partners, a subscribe box on every page, regional updates and a verification layer that says who has checked each story, with twelve task cards to point an agentic team at
PrompTugal.news, the next phase: a roadmap for the team that ran it at Web Summit and the people who want to join, from outreach and contributors to local news partners, a subscribe box on every page, regional updates and a verification layer that says who has checked each story, with twelve task cards to point an agentic team at
By Dinis Cruz · 2026-11-16 · article v1.0.0 · newsroom v0.14.121 · promptugallocal-newsoutreachverificationcontributorsagenticcellsroadmaparticle
Abstract: The team that ran PrompTugal.news with us at Web Summit is still full of beans and wants to continue, and more people want to be involved. That is great news, and it needs a roadmap. PrompTugal.news now has a strong base: 36 places, each with its own agent, 90 articles, town and company pages, every fact sourced and dated, a contribute page, and every claim in an article re-checked by three models. The next phase is people: finding contributors, journalists and local news outlets, collaborating locally, and making people aware that this exists. That is outreach, and it is now a job for agentic teams: each person points their agents at specific tasks. First contacts go only to public contacts, a form or an email published on their own site: agents draft, from templates, "we just published this, can you take a look?", and a person sends, until we have our own email connector with images inline. The outreach desk already holds 50 drafted contact requests from Web Summit, filed and never sent: the machine starts there, and meets the companies we met at the summit. A subscribe box on every page goes into an agent's append lane, with a clear note that an agent processes it, and feeds a regular update per region and town. And a verification layer says who has checked each story: sourced, model-checked, read and signed by a person, confirmed by the source, certified. Here is the roadmap, with twelve task cards anyone can pick up.
In short
- The team wants to continue, and more people want to join: this is the roadmap.
- The base is strong: 36 places with an agent each, 90 articles, sourced pages, a contribute page, model-checked claims.
- The next phase is people: contributors, journalists, local news, collaboration, awareness.
- Outreach by agentic teams: agents find public contacts and draft from templates; a person sends.
- A subscribe box into an agent's lane, feeding regional and town updates.
- A verification layer: who has checked each story, from model-checked to certified.
- Twelve task cards, so everyone has something specific to get on with.
Where PrompTugal.news is now
PrompTugal.news started as the independent newsroom we ran at Web Summit (PrompTugal.news, the newsroom we ran), and in the last few days it went local, town by town (PrompTugal.news by place). Tonight's work has given it a good base: 36 places, the Algarve's towns and now the district capitals, each kept by its own agent; 90 articles; pages for towns and companies with every fact sourced and dated; a contribute page with the rules of the game; and a verification page where each claim in an article is re-checked against its sources by three models from three families (promptugal.news). The design direction for where it goes next is in every story has an address.
The team that ran it with us at Web Summit is still full of beans and wants to continue, and there are people who want to be involved. The worst thing we could do with that energy is leave it without specific things to do.
The next phase is people
The agents have done the first part well: material, stories, information about what is happening, town by town. The next phase is to find the people: contributors, journalists, local news outlets, and the companies and councils the stories are about. Collaborate locally, with the people who know each place.
That is outreach, and it is now a job for agentic teams. Each person in the team has, or can have, an agentic team of their own (selling mini agentic teams). The question is how to get more people involved, give them agents or help them use agents, so they can collaborate with us. And the first, simplest step is making people aware that this exists.
The outreach machine
The rules are the ones the team already works by:
- Everything linkable. Every story, town page and company page has an address that can be shared and that explains itself.
- Public contacts only. The first contact goes to a form or an email the organisation publishes on its own site, nothing else.
- Agents draft, a person sends. The message is simple: we just published this, can you check it? Is it right? Would you like to contribute? An agent never sends an email or posts.
- Replies come back on a lane, and each one becomes a follow-up in the CRM (a CRM for us and for our agents).
The machine does not start from zero. The outreach desk already drafted 50 contact requests to companies during Web Summit, each with its purpose, the pages to share and the text in English and, where it fits, Portuguese. All 50 are filed and none has been sent. Updating them with what is new and sending them is the first job, and many of those companies are also the ones we met at the summit, so the follow-ups meet.
Sending email well is its own project. We need templates in the newsroom for each kind of first contact, and email with images inline, which our current tools do not do reliably. That probably means our own email connector, under behaviour policies, which would also give us far more control. That is a separate piece of work, and I will write it up next.
Subscribe, and regional updates
Every page should have a subscribe box. What someone types goes into an agent's append lane (an inbox only your agents can write to), with a clear note: your email will be processed by an agent, and we will send you the latest news for your region or town. From that, a regular update per region and per town, written from what the agents found and approved by a person before it goes. During Web Summit the newsroom already ran two editions a day; this is the local version.
A verification layer
This is the layer I most want to add. Every article and every page should say who has checked it. Two steps exist today: every fact is sourced, and each claim is re-checked by three models. Three more are to build:
- Read and signed: a person in the system has read it, and signs with their key (a key for every person).
- Source-confirmed: the company, council or person the story is about confirms it is correct, the way the claimed-profiles idea already asks them to.
- Certified: checked, confirmed and signed: a mark readers can trust.
Every outreach reply that confirms or corrects something moves a page up that ladder. The outreach and the verification are the same work.
Twelve cards
Here are the tasks, as cards anyone in the team can pick up this week and point their agentic team at:
- Awareness: make every story, town and company page linkable and shareable; a short "what PrompTugal.news is" page for first contacts.
- Contributors: find local journalists, writers and students per town; invite them to the contribute page; give each a starter agent.
- Local news partners: map every local paper, radio and newsletter per town; propose to link and credit them, never to replace them.
- Send the backlog: review the 50 filed contact requests, update them, and have a person send each one.
- Summit intersection: match the companies we met at Web Summit with the companies on the town pages, and follow up both.
- Subscribe box: on every page, into an agent's append lane, with the "an agent processes this" note.
- Regional updates: a weekly update per region and per town, approved by a person.
- Verification: build "read and signed" and "source-confirmed", and show the level on every article and page.
- Email templates: for each kind of first contact, in Portuguese and English, with images.
- Synthetic readers: point synthetic users at each town page and email, and fix what confuses them before real people see it (synthetic users for your website).
- Coverage gaps: pick a thin town, close three of its recorded gaps with sources, and connect it to its neighbours.
- Claimed profiles: build "are you the owner?" on company pages, into an append lane, with the permission flow.
Each card should end with something on the board: what was done, what was learnt, and what is waiting on a person (don't micromanage your agents).
What this does not claim
- This is a roadmap; the subscribe box, the verification steps after model-checking and the email connector do not exist yet.
- The counts are from the PrompTugal.news repository, read on 16 November 2026.
- The 50 contact requests are drafts; none has been sent, and each goes through a person.
Where this comes from
My own thinking, 16 November 2026, after a night's work on PrompTugal.news. The PrompTugal.news repository: desks/outreach/ (targets, drafts, tracker, contact requests), content/newsroom/verification.md, board/spec-contribute-page.md, board/spec-claimed-profiles.md and data/by-place/; the live promptugal.news, its contribute page and its verification page. Earlier on this site: PrompTugal.news, the newsroom we ran, PrompTugal.news by place, every story has an address, a CRM for us and for our agents, an inbox only your agents can write to, a key for every person, selling mini agentic teams, synthetic users for your website, don't micromanage your agents.
Peer review Not reviewed yet. Review it
Threads
Builds on
- PrompTugal.news, the newsroom we ran at Web Summit: desks of agents that captured, mapped, wrote and reviewed 73 signed articles in ten days, an accountant that counted every run, and fifty outreach drafts that no agent was allowed to send PrompTugal.news: 73 signed articles in ten days from desks of agents, a reviewer for every draft, and fifty outreach drafts no agent could send.
- PrompTugal.news by place: one publication for Portugal, the Algarve and every Algarve town, each place on its own subdomain from the start, each site a lens on one shared semantic graph, and one test for every story, does it connect to AI PrompTugal.news goes local: Portugal, the Algarve and every Algarve town, each on its own subdomain, each a lens on one graph, every story tied to AI.
- Every story has an address: a design proposal for PrompTugal.news as a ground-up newsroom, where news is filed where it happens and climbs to the region and the country with its proof, mocked up from the live data of 19 local editions A design proposal for PrompTugal.news as a ground-up newsroom: every story filed at an address, climbing with its proof. Mockups from live data.
- Selling mini agentic teams: a business that sets up small agentic teams for companies, sized from one agent to a network, with a control centre to see them and to start and stop them, PrompTugal as the first customer and Agent Behaviour Policies as the most demanding version A business that sets up small agentic teams for companies, with a control centre to start and stop them; PrompTugal first, ABPs on steroids.
- A CRM for us and for our agents: why the next stage is a CRM of our own, built on vaults with an iOS app, why we will build it by using it first for our own team and our own fleet of agents, how the open-source and agentic CRMs compare, and the two teams it needs, one that builds it and one that uses it Our next stage is a CRM of our own, on vaults with an iOS app, for us and our agents. Twenty leads the field; agents propose, people send.
- An inbox only your agents can write to: a conductor publishes one append lane per agent, each lane's token sealed to that agent's own key, so everything needed to talk privately is public and only the right agent can use it A conductor publishes one append lane per agent, each token sealed to that agent's key: a private channel built from public material.
- A key for every person: how each person's conductor issues them a key for the team's site, seals what is for them, and how a signed message turns the public web into a channel the agents can trust How each person's conductor issues them a key for the team's site: sealed to you, signed by you, and a lane the agents can trust.
- Synthetic users for your website: how to set up five invented visitors who read your site one screenshot at a time, with Claude, a sub-agent per persona, and an encrypted vault you can publish anywhere Onboarding for synthetic users: invented personas, a sub-agent each, a real browser one screenshot at a time, all in a vault you publish.
- Don't micromanage your agents: what changed for Vicky Wang when she stopped reading everything her agents did and started managing them, how her team was backed by agents from another team, and why every company will want specialist agents that support all its teams Vicky Wang stopped reading everything her agents did and started managing them, backed by specialist agents from another team: a model for companies.
Article No. 431 · start a reading list with it
Reviews
No reviews yet.