Independent research initiative · Europe

Autonomous agents
already act.
Nobody agreed how.

Elendil is a research initiative and an open community of researchers working out how autonomous AI agents should be governed. We are not a vendor and not a lobby. We take four questions — who is acting, by what authority, who answers for the consequences, which rule actually works — and try to settle them with evidence anyone can check.

Independent

No vendor, ministry, or lab owns our conclusions. Funding is disclosed; findings are not negotiated.

Open by default

Methods, data, code, and the experiments that failed — published, so the work can be checked rather than believed.

Evidence before opinion

If no measurement could change our answer, we call it an opinion and label it as one.

The problem

Deployment compounds. Rules arrive in steps.

Agentic systems are shipped continuously and copied instantly. Governance instruments — registries, thresholds, audits, liability rules — arrive one negotiated step at a time. The distance between the two curves is where the harm lives, and it is widening.

Closing it is not only a legislative problem. Most proposed rules for autonomous agents have never been tested against a system that acts continuously, at scale, and across borders. Some of them cannot be enforced at all. Finding out which ones is research, and that is the work we do.

AUTONOMY DEPLOYEDINSTRUMENTS IN FORCETHE GOVERNANCE GAPTIME →SCHEMATIC · NOT MEASURED DATAREACH

Research tracks

Four questions, asked properly.

Governing an autonomous agent means answering four things in order. Each is a standing track, with open questions, published evidence, and a working group anyone competent can join.

01

Who is acting?

Attribution & evidence

A rule that cannot be attached to an actor cannot be enforced. We study how to tell an agent from a person, one fleet from another, and a delegated action from an unauthorised one — from behaviour and content, without relying on voluntary labels or watermarks.

  • Agent-vs-human discrimination in the wild
  • Fleet and operator attribution
  • Evidence that survives a hearing
02

By what authority?

Mandate & delegated authority

Every autonomous action is exercised on someone's behalf. We work on how a mandate is granted, carried, checked, narrowed, and revoked at machine speed — and what it means for an agent to act outside the envelope it was given.

  • Scoped delegation & role-conditioned attestation
  • Revocation and expiry under automation
  • Detecting off-mandate behaviour
03

Who answers when it goes wrong?

Accountability & redress

Harm caused by an autonomous system still lands on a person. We study the record-keeping, audit, incident reporting, and liability arrangements that let an affected party find out what happened and obtain a remedy.

  • Records of decision & auditability
  • Incident reporting thresholds
  • Liability allocation and redress routes
04

Which rule actually works?

Instruments & institutions

Governance is written in instruments: registries, licences, thresholds, audits, standards, sandboxes. We test which of them survive contact with agents that act continuously, at scale, and across borders — and say plainly which do not.

  • Mapping existing law onto agentic systems
  • Registries, thresholds & conformity assessment
  • Systemic risk in multi-agent settings

How we work

From an argument to something you can check.

Agent governance is full of confident positions and thin evidence. Our method is the correction: every claim we make has to be attached to something a stranger could reproduce or refute.

01

Frame the question

Turn a governance argument into a question that evidence can settle. If no measurement could change our answer, it is an opinion, and we label it as one.

02

Build the evidence

Assemble datasets, benchmarks, and reproducible experiments — evaluated out-of-time, with uncertainty stated and the failed attempts published alongside the results.

03

Prototype the instrument

Build the smallest working artefact that shows whether a proposed rule is enforceable at all: a detector, a registry schema, an attestation format, an audit procedure.

04

Publish & convene

Put the finding in front of regulators, labs, and operators — in the open, in language a non-specialist can check — and revise it in public when someone shows us we are wrong.

// agenda.questionopen
questionQ-02

Can a mandate be revoked faster than an agent can act on it?

[track]Mandate & delegated authority
[evidence]2 experiments · 1 negative result
[status]Contested — no accepted benchmark
[settles]A revocation-latency benchmark across runtimes

Latest

What we have published.

Working notes, benchmarks, and negative results. Written to be checked, not to persuade.

All publications
RN-004

Catching the agent that turns: detecting AI gone rogue

An autonomous agent, given the wrong instruction, starts probing and attacking a system it was never authorised to touch. We detect it two independent ways — the offensive kill-chain in its behaviour, and attack tooling in its content — and the content detector reaches 0.993 AUROC, catching 97% of payloads clean and 98% obfuscated at a 0.4% false-positive rate, where a regex WAF sees a third. Two independent signals, each one explained.

9 min read →
RN-003

Coordinated agent fleets share a config, not a clock

We built a detector for coordinated AI fleets on two signals — shared behavioural fingerprint and synchronised timing — and it scored 0.97 precision in simulation. On 1,677 real GitHub instances it scored 0.00. The timing signal is at chance for agent fleets and works for humans: coding agents are demand-driven, so they share a config but no clock. What we changed, and why the failure was more useful than the success.

9 min read →
RN-002

How we hunt financial crime — including the experiments that failed

Our detection strategy in five decisions: think in networks, layer five detectors that cover each other's blind spots, validate on external ground truth, and chase the representation instead of the model — the move that took an interpretable, dependency-free forest from 0.70 to 0.956 on IBM AMLSim, matching published GNN results, at 81% precision on a top-0.1% review budget.

11 min read →

The community

A think tank is only as good as the people arguing inside it.

Elendil is deliberately plural: machine-learning researchers, lawyers, security engineers, and public-sector practitioners, because no single discipline can answer these questions alone. Working groups form around a track, publish under their own names, and are free to disagree with each other in print.

The initiative is young, and most of the seats are still open — affiliated researchers, working-group members, reviewers, students looking for a thesis subject, and institutions willing to put a hard question to us.

How to take part
IndependentNo vendor, no capture
Open by defaultMethods, data, code
PublishedIncluding what failed
EuropeBase and jurisdiction

The rules for autonomous agents are being written right now.

They should be written by people who have tested them. Bring a question, a dataset, a disagreement, or a chapter you want to work on — and help us settle it in public.