Gonçalo Pereira Rebeca, AI Systems Architect. I design AI systems, then I build them and keep them running.
A-02 · How I work
Every company already has a way of working.
People, tools and habits that move work from room to room. Some of it flows. Some of it waits for someone to do it by hand.
A-02 · How I work
I start by learning yours.
Every room, every tool, every hand-off. Where the work actually moves, and where it waits.
The question I always ask
“What needs to change to 10x your revenue?”
A-02 · How I work
Then I find what breaks at 10x.
Work re-typed between tools. Requests lost in an inbox. Reports rebuilt by hand. That is where the system goes.
A-02 · How I work
Then I design the AI around it.
Your team keeps its rooms and its tools. I draw one new layer through the building, right where the work gets stuck.
A-02 · How I work
It goes live where your team already works.
In the CRM, the inbox and the chat your team already uses. The queues clear, and nobody has to learn a new app.
A-02 · How I work
Map. Deploy. Compound.
- MapI learn how work moves, find where it breaks, and draw the system.
- DeployI build it inside your stack, with your team in the room.
- CompoundIt learns from every week it runs.
I work forward deployed: inside the team, until the system runs without me.
A-03 · Work
Systems in production.
Eight builds, one at a time. Each one started as a drawing.
A-04 · Inside a build
Every system is a building.
Cut one open and you can see how it goes together, floor by floor.
A-04 · Inside a build
AI employees
DONE · Agents in production
Agents hired into roles across the company, all on one brain. Six floors, from the roof down.
Roof · Manager
A manager agent that reports to your team.
It watches every role and tells the team how each area is going: every morning, or whenever someone asks.
L4 · Roles
Every hire is a role, not a new system.
Front desk, sales, collections, recruiting. Each role is a brief, a test pack and a config on the same brain.
L3 · Brain
It reads every message and decides what happens next.
A booking, a payment, a question, a complaint. Each one is read and weighed, and the next step is chosen: reply, act in your tools, follow up later, or bring in a person.
L2 · Guards
The rules that can't bend live in code.
Prices come from the price list, opt-outs are final, and anything sensitive goes to a person. No prompt can talk its way past them.
L1 · Memory
It remembers every conversation.
Every customer's history and state, read before each reply and updated after it. Nobody gets asked the same thing twice.
Foundation · Exam
Nothing ships until it passes the exam.
Ten real scenarios, including the ones that go wrong, run before every release. When all ten pass, the building goes live.
A-04 · Inside a build
Six floors, one brain.
A new hire is a new role on the fourth floor. Everything under it is already built, tested and running.
A-05 · Research and development
I also write the building code.
Every system I ship teaches me something. I write it down as a principle, test it on the next build, and keep what holds.
§ 01
Judgment lives in the prompt. Mechanics live in code.
Anything that must never go wrong, like a price, a permission or a payment, is enforced in code. Anything that needs judgment, like tone, priority or when to escalate, lives in the prompt, where it can be tuned without a release.
§ 02
An adversary reads every plan before anything gets built.
Before an agent writes or sends anything, a second agent tries to break the plan: missing edge cases, conflicting tasks, scope too big for one run. Minutes of review save days of cleanup.
§ 03
Every run teaches the next one.
Agents that write down their mistakes stop repeating them. First-pass approval climbs week after week as that memory grows.
§ 04
The harness is the product.
Same model underneath: one product feels like a demo, the other like a coworker. The gap is memory, permissions and checks, not intelligence.
A-05 · In the lab
What I'm building next.
A video system: films cut from real photos, and films rendered entirely in code.
A lead engine for one niche market. More once it has proven itself.
Linking the vaults of a whole team. Two runs so far, a benchmark paper in draft.
An agent that sources and screens IT talent for staffing firms.
A-06 · Foundations
What shaped how I build.
Five layers, from the bedrock up. Every one of them is still load-bearing.
Bedrock · Research
Trained in molecular genetics.
What it gave meForm a hypothesis, test it, keep what survives.
Three research fellowships · two publications
Layer 2 · Marketing · 2013 to 2023
A decade in digital marketing, from e-commerce to Web3.
What it gave meI know where revenue actually comes from.
PARFOIS · Sonae · then Web3 gaming
Layer 3 · Teaching · 2015 to 2023
1,500+ students in digital business and web analytics.
What it gave meI can explain a system until a team actually uses it.
Porto Business School · ISAG · EDIT · FLAG
Layer 4 · Business · 2016 to 2023
Co-founded a consumer brand and a digital agency.
What it gave meI know how a company runs from the inside: stock, clients, payroll.
Top floor · AI systems · 2022 to now
AI systems that do real work, and get better at it.
Where it all landsEvery layer below, working in one system.
Myosin · DONE · my own lab