Made-up example. Cinco Chaminés is an invented company: the homes, prices, availability and bookings are simulated, and the pictures are AI-generated. The weather, sea, UV and events are real, read live from data.promptugal.news. What is this site?

Cinco Chaminésholiday homes in the Algarve (a made-up example)

Behind the scenes

This site is made by an agent team of the AgentiCCells account, started at Dinis Cruz's word on 18 November 2026, as a demonstration of the site factory and its conductors. Everything on these pages is read from the site's own repository each time the site is built: the workflow, each role's files, the round reports and the git history.

What is this site?

A made-up example. Cinco Chaminés ("five chimneys") is an invented company with five invented holiday homes in the Algarve. The homes, their descriptions, prices, availability and bookings are simulated; the pictures of the homes are AI-generated and show houses that do not exist. The booking flow keeps and sends nothing and ends in "This is a demonstration: nothing was booked, nothing was sent, nothing was charged". The agent is scripted: pre-written answers matched in your browser, with no live model.

What is real: the weather forecast, warnings, sea and UV from IPMA, Instituto Português do Mar e da Atmosfera, and the events from the towns' own agendas, read live in your browser from data.promptugal.news, with the source, the read time and the terms beside every figure. See Use the data for how to read the same files yourself.

Why: to show what a small business could build on public data with an agent team, and how the team works, step by step, below.

About the pictures

Every picture on this site is AI-generated: none is a photograph. The team's designer made them on 18 November 2026 with an image model (Google Gemini 3.1 Flash Image, through OpenRouter), asking for each invented house outside, inside, and once somewhere it could never be (on a salt heap, up a carob tree, on a sea stack), plus four pictures of the Algarve. The houses do not exist; no picture shows a real house, business or person. 19 pictures were chosen from 22 made; the prompts, the cost of each call, what was rejected and why, and the alt text are in the designer's picture log. Each picture is served at 800 and 1264 px wide from /assets/img/, under CC BY 4.0 like the site's other text and pictures. The house drawings, the site's first pictures, are still used on the cameras map and in the agent's answers.

In Dinis's words

Dinis Cruz, 2026-11-18, about 16:10 UTC, in the cells@AgentiCCells.dinis session: "in fact, I started all of this by wanting to create a website for a sort of a real estate agency. In fact, why don't you do that too? ... you should be able to see the availability, book it, kind of add an agent to it. Why don't you simulate an agent with a bunch of actions that are already pre-scripted, maybe with a little bit of that intelligence that we can try to predict what they say."

Same message, on the budget: "we also need to make sure that we have a budget for each one, even like maybe we only do 5 design rounds or 5 full rounds, right? And again, it's very important that you capture all the sequence, because part of the exercise of these websites is to explain how this works, explain what we do, but also explain how to use the raw data that we collect."

Same message, on the billboard and the cameras: "See if you can find what I've published before about the idea of creating some billboard ads in London with data, live data from the Algarve, even live stream of cameras ... we probably need to map the live stream of cameras to show what it looks like, because they're all public cameras, right? So in fact, why don't we experiment here?"

The brief, its data sources and the rules: requests/2026-11-18__algarve-holiday-homes/brief.md in AgentiCCells/AgentiCCells__Site__Factory (branch dev). This cell was started by cells@AgentiCCells.dinis on 2026-11-18 at Dinis's word, with the model of the IPMA data cell (AgentiCCells/AgentiCCells__Site__IPMA-Data): a team with a policy per role, rounds, five designs and a behind-the-scenes section.

The site, https://algarve-holiday-homes.agenticcells.site, is a made-up example: an invented small company with five holiday homes in the Algarve, simulated availability and a booking flow that ends in "This is a demonstration: nothing was booked, nothing was sent, nothing was charged", a scripted agent with no live model (labelled simulation), live IPMA forecasts, warnings, sea and UV and events-pt events read from data.promptugal.news, "Live from the Algarve" (public live cameras, also published as /data/cameras.json), the proposal "A London billboard, live from the Algarve", five designs under /d/, behind the scenes, Use the data and Use with AI.

From team/WORKFLOW.md.

The team

6 roles, each a sub-agent of the conductor's session, briefed with two files: ROLE.md (what it is for) and POLICY.md (its Agent Behaviour Policy). Which paths each role may change is set in team/scopes.json, and a gate fails a release that breaks it.

The flow of a round

Each round runs these steps; each step writes files in the repository, so the next step, and these pages, can read them.

The flow of one round, in six steps Top to bottom: 1, Brief, by the conductor, writes team/rounds/N.md (the aim). 2, Research and design, by the researcher, designer, writes team/rounds/N/research/, cameras.json team/rounds/N/design/PROPOSAL.md. 3, Build and words, by the developer, writer, writes src/, team/rounds/N/build/ team/rounds/N/copy/. 4, Review, by the reviewer, writes team/rounds/N/review/ a failure goes back to step 3. 5, Release, by the conductor, writes scripts/release.sh: gates, push to dev; CI tags v0.1.N. 6, Report, by the conductor, writes team/rounds/N.md (what changed) one line to cells@. If the review fails, the round goes back to step 3. The steps are also written out next to this diagram. 1 Brief conductor team/rounds/N.md (the aim) 2 Research and design researcher, designer team/rounds/N/research/, cameras.json team/rounds/N/design/PROPOSAL.md 3 Build and words developer, writer src/, team/rounds/N/build/ team/rounds/N/copy/ 4 Review reviewer team/rounds/N/review/ a failure goes back to step 3 5 Release conductor scripts/release.sh: gates, push to dev; CI tags v0.1.N 6 Report conductor team/rounds/N.md (what changed) one line to cells@
A summary of the loop in team/WORKFLOW.md, drawn by the generator; the paths are from that file and team/scopes.json.

The loop, as team/WORKFLOW.md writes it

  1. Brief. The conductor writes the round's aim at the top of team/rounds/N.md.
  2. Research and design. The researcher reads the live files and cards and checks the name and the cameras, writing team/rounds/N/research/ (and src/data/cameras.json); the designer reads them and writes team/rounds/N/design/PROPOSAL.md with mock-ups.
  3. Build and words. The developer builds the proposal and the writer writes the words and the agent's intents and answers, in separate files; each runs the build and the validator locally. Neither pushes.
  4. Review. The reviewer checks the build against the brief's rules in team/rounds/N/review/: "made-up example" on every page; the demonstration statement at the end of the booking flow; forms keep and send nothing; IPMA named with the read time and terms beside every figure; events with their source and link; no booking-platform brand names; the camera rules; nothing invented that a visitor could take for real; failure states (missing, stale, slow); 390 and 1366 px; keyboard; contrast; no em dashes or hype words. A failure goes back to step 3 in the same round.
  5. Release. The conductor reads the diff and runs scripts/release.sh (build, validate, leak scan, check-commits, role-scope, abp-check, then rebase and push to dev, which deploys; CI tags v0.1.N).
  6. Report. The conductor completes team/rounds/N.md (what the round was spent on, what changed, the reviewer's verdict, what is open, what Dinis must decide) and sends one line to cells@AgentiCCells.dinis (session id 018yvwtNtj31quYqCxxywEUo, written without its session_ prefix): round, live version, what changed, anything Dinis must decide.

Rounds

Latest commits

All 76 commits, by day, with a count per role

More

Ask the agent (a simulation: pre-written answers, no live model)