Work items the owner has requested, taken in order, highest first.
The owner edits this file to steer the section; agents append ? for tom: bullets and mark items done, nothing else.
- Build the research index (standing) - create research notes per the AGENTS.md format, one category at a time, each category seeded with the tools practitioners actually meet. Seed categories, in rough order:
- Harnesses: Claude Code, Codex, Gemini CLI/Antigravity, OpenCode, aider, Crush, Amp, Junie.
- Surfaces: Cursor, VS Code + Copilot, Windsurf, JetBrains/Junie, Zed.
- Orchestration: parallel-agent dashboards and worktree managers (Conductor, dmux, Emdash, and neighbors).
- Protocols: MCP, ACP, AGENTS.md, A2A.
- Context engines: code search and context packing for agents.
- Skills: skill formats, registries, and marketplaces.
- Retrieval: RAG patterns and tooling for code and knowledge bases.
- Memory: agent memory systems, from file-based notes to knowledge graphs and session archives.
- Executions: scheduled and event-based agent runs (cron-style tasks, triggers, webhooks).
- Hybrid execution: deterministic components orchestrating LLM steps for intelligence and structured outputs (tool calling, schema/JSON outputs, validation and retry loops).
- People and publications: the people and websites shaping the domain (Karpathy, swyx/Latent Space, Willison, Yegge, Orosz/Pragmatic Engineer).
Done:
Agentic coding tools landscape- done 2026-08-22, published as agentic-coding-tools-landscape; becomes the essay layer over the harness/surface/orchestration notes, cross-link as notes appear.Model selection for coding tasks- done 2026-08-24, published as model-selection-for-coding-tasks.Context management patterns- done 2026-08-24, published as context-management-patterns.People and publications category- done 2026-08-29, seeded at the owner’s request with five notes (Karpathy, Latent Space, Willison, Yegge, Orosz/Pragmatic Engineer) plus the companion people-and-publications-feature-matrix.
? for tom: The 2026-10-01 banned-term sweep reworded “real” section headings in the main corpus but left this section’s roughly 330 “real” uses (mostly “real-world” compounds and contrastive uses like “adoption is real, stability is not”) in place, and the daily verification has been treating them as the most-appropriate-term exceptions since. Should the section get the same rewording treatment, or is the corpus-only scope the intent? Rewording at this scale needs its own directed run with Changes bullets per touched note, so I have not done it inside a daily refresh.