Intent-based System

Normally, you tell a computer exactly what to do: first this, then that, then the other thing. An intent-based system turns this around. You only describe the desired outcome, and the software figures out for itself which steps are needed to achieve it. The English word “intent” refers to exactly this desired outcome. An example: Instead of configuring twenty devices one by one, you say “all computers on the school network should have internet access, but not access to the administration server”. The system translates this sentence into concrete settings and keeps an eye on them.

Why goals are more robust than command lists

The big advantage lies in the fact that a goal remains valid longer than a set of instructions. A step-by-step instruction becomes outdated as soon as something changes in the environment. If a new device is added, someone has to manually adjust the list. A goal like “no one from outside may access this data”, on the other hand, continues to apply, even if everything else changes.

On top of that, complex systems are barely manageable for humans anymore. A larger corporate network consists of thousands of rules that influence each other. Many outages are not caused by attacks, but by human configuration errors. Those who only need to formulate goals can make fewer detail-level mistakes.

However, one misunderstanding should be avoided: intent-based does not mean that the machine decides what is good. The intent still comes from the human. Only the path to get there is automated. If the goal is poorly formulated, the system will reliably implement something wrong.

From wish sentence to ongoing monitoring

The process usually consists of four stages. First, the system takes in the intent, often in plain language or via a form. Then it translates it into technical rules that the devices or programs involved can understand. These rules are then rolled out, meaning actually configured.

The fourth stage is the most important and distinguishes such systems from simple automation. The system continuously measures whether the current state still matches the goal. If something deviates, it either corrects itself or reports the problem. Experts call this a control loop: measure, compare, adjust, measure again.

You can imagine it like a thermostat. You set 21 degrees, not when and how strongly the heating should run. The thermostat measures the temperature and adjusts when someone opens a window. Modern systems increasingly use language models—that is, AI programs that can process human sentences—to translate the goal. But that is exactly where the weak point lies: an ambiguous sentence can be misinterpreted, which is why there is usually a human confirmation step before rollout.

Networks, cloud, and AI assistants

The term is best known in network technology, where it is called Intent-based Networking. Vendors like Cisco or Juniper sell software that controls large corporate networks through goal specifications rather than individual device commands. The cloud, meaning rented computing power in remote data centers, works similarly: there, you describe the desired end state in a file, and a tool creates it.

In everyday life, you encounter this principle with voice assistants and AI agents. The sentence “book me a cheap train to Hamburg on Friday morning” is an intent. Which search mask is opened and which connection is compared is decided by the program itself. Smart home systems also work this way when you specify a desired climate instead of individual switching commands.

In the news, the term usually appears in connection with automation and cost reduction. Companies expect less personnel effort and shorter downtimes. The question of responsibility remains critical: if a system implements an intent differently than intended, the error is harder to find than in a clear list of commands.