Skip to content

Labor · Agent systems

Specialized agents that hand off tasks with intent

Instead of wiring every service to every other service, agents describe their capabilities and find matching counterparts at runtime. This page shows the principle as a structural diagram, as a simulation, and with a publicly reachable agent.

Isometric illustration: a central building block connected to six smaller building blocks around it, a glowing card moving along one connection toward the hub.Isometric illustration: a central building block connected to six smaller building blocks around it, a glowing card moving along one connection toward the hub.

Practical setup 01Structural diagram · A2A principle

Finding capabilities instead of hardwiring connections

Hardwired integrations need individual changes with every extension. In modular agent systems, new capabilities should be discoverable on demand, without fixing every connection in advance.

RegistryDiscoveryBrokeringInboxExtractionCategorizat…ValidationRulesetTarget syst…ApprovalPayment

Classification Structural diagram · A2A principle, not a specific deployment

How the setup works A registry collects capabilities. Whoever wants to hand off a task finds a matching counterpart there. The task then moves through the stations involved.
Scope and limitations

Not part of this demo: The diagram shows roles and handoffs, but no operational measurements, response times, or a concrete count of production agents.

The topology is a structural diagram for the A2A principle, not a specific customer deployment.

Interactive simulation

Play through an agent topology yourself

Start different process types and watch which specialized stations get involved. The simulation shows paths, sequences, and queues, but no measurements from a live system.

Agent topology: 13 building blocks in 5 layers, 13 connections derived from the processing paths.
L0 · 3 BUILDING BLOCKSL1 · 2 BUILDING BLOCKSL2 · 3 BUILDING BLOCKSL3 · 4 BUILDING BLOCKSL4 · 1 BUILDING BLOCKCPCustomer PortalISInternal SystemsPAPartner AccessCLClassificationVLValidationRTRouterKBKnowledge BaseDERulesetPRProcessingINHandoverHIWorkstationHDDecisionQCQuality Check

Speed 1× · 0 processes running · 0 runs completed

Simulated runs of this panel, not a measurement of a live system. The time spent at each station is the total duration of the process type, spread evenly across its stations. Which type starts next depends on its configured share. A new process every 2 s at 1× speed.

The diagram is shown from a screen width of 640 px on. 13 nodes in 5 layers, 13 connections, 4 processing paths. To the parts list

Legend

A building block with at least one connection in use, shown with a solid outline.
A building block with no connection in use, shown with a dashed outline (4: Customer Portal, Internal Systems, Partner Access, Decision).
A connection, derived from the station sequence of the processing paths. Connections to external services are not recorded in the data and are therefore not drawn.
L
Column header for the layer a building block sits in, with the count of how many sit in it next to it. The data does not name the layers.
ALT
A process in progress, a dot carrying the short code of its type. It follows exactly the station sequence of its path.
Station
A working station. Its outline stands out and progress runs along its bottom edge. Each station handles one process at a time. The dots next to it are waiting.
Speed
Speed controls only the playback rate (0.5× / 1× / 2×). It changes nothing about the paths and dwell times, which stay exactly as recorded in the data.
Sources
Speed and display mode change only the simulation, not the process paths shown.

Public BKS agent

Talk to a running BKS agent

The public agent answers questions about BKS-Lab over the A2A protocol. It works exclusively with public information and knows no customer or project data.

Your input is transmitted to the agent. Please do not enter confidential information.

Open the public BKS agent →

From structural diagram to live demo
The diagram and simulation explain the principle of modular agent systems. The linked BKS agent is a running service and answers general questions based on public information.

Back to the Labor overview →

Which task should run as its own specialist?

We assess where clearly scoped agent roles can complement existing workflows and where a classic integration remains the better fit.

Schedule a conversation