The threads

A thread is a theme tracked through time — a topic the group kept pulling on across meetings until it became a line you can follow. Fourteen threads hold the corpus. This is the map: each thread is a node, sized by how many ideas it carries; two threads are linked when they keep showing up in the same meeting. The themes index defines each one; this page shows how they connect.

The same map renders below as a graph you can read by type. Solid heavy links are the strongest co-occurrences; dotted links are weaker ties.

graph LR
  subgraph Build
    agentic(["agentic workflow<br/>143 ideas"])
    context(["context engineering<br/>97 ideas"])
    devprod(["developer productivity<br/>59 ideas"])
    signal(["signal harvesting<br/>40 ideas"])
    substrate(["project-state substrate<br/>8 ideas"])
    toolstack(["tool stack<br/>8 ideas"])
  end
  subgraph Method
    system(["system vs design thinking<br/>59 ideas"])
    cadence(["meta / meeting cadence<br/>54 ideas"])
  end
  subgraph Human
    education(["ai and education<br/>55 ideas"])
    people(["people and team<br/>24 ideas"])
  end
  subgraph Market
    product(["product and business<br/>61 ideas"])
  end
  subgraph Trust
    eval(["llm evaluation and trust<br/>14 ideas"])
    hiring(["hiring and authentication<br/>12 ideas"])
  end
  subgraph Philosophy
    future(["future and society<br/>15 ideas"])
  end
  agentic ==> context
  agentic ==> system
  agentic ==> product
  agentic ==> devprod
  context ==> devprod
  context ==> system
  agentic ==> cadence
  agentic ==> education
  context --> product
  product --> system
  devprod --> system
  education --> context
  context --> cadence
  context --> people
  devprod --> product
  cadence --> system
  cadence --> product
  agentic --> signal
  classDef Build fill:#9c4a2f,stroke:#2b2622,color:#fff;
  class agentic,context,devprod,signal,substrate,toolstack Build;
  classDef Method fill:#4a6b8a,stroke:#2b2622,color:#fff;
  class system,cadence Method;
  classDef Human fill:#5b8a4a,stroke:#2b2622,color:#fff;
  class education,people Human;
  classDef Market fill:#b58a2f,stroke:#2b2622,color:#fff;
  class product Market;
  classDef Trust fill:#7a4a8a,stroke:#2b2622,color:#fff;
  class eval,hiring Trust;
  classDef Philosophy fill:#6b6b6b,stroke:#2b2622,color:#fff;
  class future Philosophy;

---

thread types

Every thread falls into one of six kinds. The type tells you what the thread is for.

Build — building the thing — agents, context, tooling, the substrate underneath.
threads: agentic workflow, context engineering, developer productivity, signal harvesting, project-state substrate, tool stack

Method — how the work is structured — system thinking and the meeting cadence itself.
threads: system vs design thinking, meta / meeting cadence

Human — the people layer — teams, teaching, the social ground AI lands on.
threads: ai and education, people and team

Market — where value is captured — product, process, access.
threads: product and business

Trust — how you know — evaluation, authentication, the integrity questions.
threads: llm evaluation and trust, hiring and authentication

Philosophy — the long view — the human after the tools.
threads: future and society

---

every thread, described

thread	type	ideas	meetings	span	trajectory	closest thread
agentic workflow	Build	143	68	2024-04-17 → 2026-06-17	steady	context engineering
context engineering	Build	97	54	2024-04-24 → 2026-06-24	steady	agentic workflow
product and business	Market	61	42	2024-06-05 → 2026-06-10	fading	agentic workflow
developer productivity	Build	59	37	2024-08-28 → 2026-06-10	steady	agentic workflow
system vs design thinking	Method	59	43	2024-07-31 → 2026-06-24	steady	agentic workflow
ai and education	Human	55	28	2024-06-26 → 2026-06-24	rising	agentic workflow
meta / meeting cadence	Method	54	37	2024-05-15 → 2026-06-24	fading	agentic workflow
signal harvesting	Build	40	23	2024-08-14 → 2026-06-24	rising	agentic workflow
people and team	Human	24	21	2024-08-14 → 2026-06-24	rising	context engineering
future and society	Philosophy	15	15	2024-08-07 → 2026-06-03	steady	agentic workflow
llm evaluation and trust	Trust	14	11	2024-08-28 → 2026-06-24	steady	context engineering
hiring and authentication	Trust	12	11	2024-07-31 → 2026-06-17	rising	context engineering
project-state substrate	Build	8	8	2025-06-25 → 2026-06-10	rising	product and business
tool stack	Build	8	7	2024-09-11 → 2025-10-22	fading	agentic workflow

Trajectory compares each thread's share of recent (2026) ideas against the corpus baseline: rising threads are pulling more weight lately, fading ones less, steady ones holding.

---

reading the map

• agentic workflow is the hub — it shares more meetings with other threads than any other, which is why it sits in the middle of the graph. The build work touches everything.
• The tightest single tie is agentic workflow ↔ context engineering (35 shared meetings). They are almost the same conversation.
• Rising lately: ai and education, signal harvesting, people and team, hiring and authentication, project-state substrate. These are where the recent meetings keep going.
• Fading: product and business, meta / meeting cadence, tool stack. Early-corpus threads that have quieted, not closed.

The graph is generated from the records, not drawn by hand. Re-running the pipeline redraws it: nodes resize as threads grow, edges thicken as threads converge. The map is a view of the substrate, and the substrate is the meetings.