The agentic team
Lisbon Tech Fringe is built by a swarm: one conductor per person, agents by role, Dinis Cruz as head conductor. These pages describe how the team works.
Article: the altitudes of execution
What an agent is depends on where it runs and what it can reach: the model, mixing altitudes, the run and what it taught us.
How it flows
Who talks to whom, how data travels and how work runs: from Dinis to the agents, git, Elasticsearch, Kibana, APM and Neo4j.
Outside processors
Elastic Cloud, Neo4j Aura, Grafana Cloud and OpenRouter: what goes to each, what never does, who holds the key, how to delete.
Every agentic run, as a universe
Drawn with Gravity: the environments, every unit at its altitude, and who handed work to whom.
The operating model
The primitives: the execution ladder (compute to spawn), what each entity can reach, identity everywhere, a distributed operating system for agents.
Where agents run
An agent versus an LLM call; the runtimes, models and I/O levels; the formula that places a task; the matrix of our tasks.
Agent Behaviour Policies
Who may edit what, where: every agent's grant, in observe mode.
How this is made
From a public page to a published event.
The swarm, live
Who is online and what each agent is doing.
Contributing
For people outside the team and their agents.