CtrlK
BlogDocsLog inGet started
Tessl Logo

ainativedev/aidevcon-2026-ldn

AI Native DevCon 2026 London — all conference sessions as interactive skills

70

Quality

88%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

Overview
Quality
Evals
Security
Files

quote.mdtalk-maleix-collective-intelligence/

Topic-tagged verbatim quotes (with approximate transcript section). Speech-to-text artifacts preserved as-spoken; bracketed gloss added when meaning is unambiguous.

On the core problem (lessons evaporating)

  1. "All the small discoveries, all the tiny learnings, all the incidents that are inside the session. They rarely make it out of it. They just end up closed here. So correction evaporates." — The familiar obstacles
  2. "Agent work create lessons every day. Like you have those leisurely in the session, but the team is not learning." — What we actually need
  3. "What our agents learned yesterday that our team can use today or tomorrow and the days after." — Opening
  4. "What is your agents learned yesterday that your team still knows today?" — Closing (the inverted closing form of the opening question)

On rules / skills accumulation

  1. "We have lots of rule that buys up. Some skills, some project notes. And yeah, the dress pile up, same as your context below. It really gets crowded. And you barely can barely say when it's getting used, if it's still useful, if it became stale, and even if it gets activated when you expect it to be activated." — The familiar obstacles
  2. "The PR can show up green, like all test passes, … you can hardly, you cannot even tell actually what lessons shape that work." — The familiar obstacles

On accepting knowledge decay

  1. "You will let some of those guidance fail because some knowledge just decay. We have to accept that." — What we actually need
  2. "Instead of having. Static documentation, we have something that constantly move die the day after. Not a problem. Just need to accept that." — What we actually need

On identity (Act 1)

  1. "PR was really written, I think 95% by globally [Claude]. … And all the commits are under my name. They are even my GPT [GPG] signature." — The Testify PR anecdote
  2. "Give the agent an identity. That's the first primitive. … The identity gives us tier separate actor. It gives us some sign commits." — Identity primitive
  3. "It's even worse for the PR reviews. … you might have received some PR reviews. Authored by one of your teammates, but actually counter by global [Claude]." — The Testify PR anecdote

On the diary

  1. "The place where the stops being just the work and the lessons start being a four-way [forward] artifact." — The Diary primitive
  2. "If the work or decision matters, you need to lend it somewhere before it disappear." — The Diary primitive

On rendering with attribution

  1. "Every section can see points through given entry. … Keep the attribution live. So here you can see the source with the answer identifier. The human that was operating. And the agent identifier as well." — Render
  2. "Not have just the skill that says that's how you do things. It's more like that's how you do things because we got beaten somewhere that hurts and we don't want that to happen again." — Render

On the pipeline (Act 2 summary)

  1. "Interruption becomes an entry. The right entries become a pack. Then the pack becomes something the agent can read. And then in the end that one developer paid for … We counted team asset." — Act 2 summary
  2. "There is even a discipline. I did not hear the word yet today. It seemed to be called compound generating [engineering]." — Act 2 summary

On evals

  1. "Before you run an llm judge you are the judge. You do the work that the judge will do yourself." — Evals: Fidelity
  2. "For that go plan scenario without the pack we fail at 67 every time the go sdk was missing from the agent work. Whereas with the back it was always passing even after repeating the same task." — Evals: Usefulness

On autonomy

  1. "You as the human keep the goal, the judgment and the responsibility and the agents keep the continuity repetition." — Act 3
  2. "You just have agent with some set of capabilities. And any of those agents can fire a task if it matches its capability. So it pre-picks voluntarily." — Act 3 (voluntary task picking)

On curation (Q&A)

  1. "Every workflow before we should lend it to an llm. We need to master it as human because then you need to explain that llm how we issue two things and if you are not able to explain it how can we expect the length [LLM] to be for you." — Q&A on curation

talk-maleix-collective-intelligence

README.md

tile.json