Legend
The words, and how much they are worth.
42 terms from agentic coding, defined the way a working engineer would accept. Where a term is mostly a rebrand, the entry says so — and says which claim it is grading.
- established
- Settled. Documented by a primary source and not seriously disputed.
- emerging
- Real practice, thin evidence. Mostly vendor-stated or reported rather than measured.
- contested
- Practitioners actively disagree. Anyone claiming it is settled is selling something.
- thin
- The named claim does not hold up. The entry says which claim.
The window
Everything here exists because the window is fixed and nothing in it survives the session.
3 termsDocuments an agent reads
A document an agent reads is a lever on its behaviour, not prose. These are the parts that move it.
7 terms- Context pointeremerging
A reference the agent holds, naming material it does not — plus when to go get it.
- Leading wordemerging
A pretrained concept the agent thinks with — frontier, fog, tracer bullet, lane.
- Context load / cognitive loademerging
Two budgets most writing collapses into one. Only the first should be minimised.
- No-opemerging
An instruction the model already obeys. It pays load to say nothing.
- Completion criterionemerging
What tells an agent the work is finished. Vague bounds invite premature completion.
- AGENTS.mdestablished
A README for agents. Plain markdown, no schema, closest thing to a neutral convention.
- Agent Skill (SKILL.md)established
A folder of instructions an agent loads on demand. The portability is real.
The harness
Everything around the model: what it can call, what it may do, and what it costs.
7 terms- Subagentestablished
A delegated worker in its own window, returning a summary rather than its transcript.
- MCP (Model Context Protocol)established
Open standard for connecting agents to external systems. The window cost is real.
- Hookestablished
A shell command the harness runs at a fixed point. Exit codes are the interface.
- Permission levelestablished
How much the agent may do without asking. A blast-radius control, not a correctness one.
- Prompt cachingestablished
Reuse of a processed prefix. Makes the front of a context expensive to change.
- Prompt injectionestablished
Agents compromised through the content they exist to process. No malware required.
- Agentic search vs. semantic indexcontested
Grep on demand or embed the repo. Genuinely unsettled — treat certainty as a tell.
How work is arranged
Decomposition, ownership, and who is allowed to touch which file at the same time as whom.
10 terms- Task graph (dependency graph)established
Nodes and edges recording what blocks what. The useful part is the edge, not the diagram.
- Frontierestablished
The nodes whose prerequisites are all satisfied — the edge of what is takeable now.
- Fogemerging
Work whose open questions gate each other. Density picks the instrument.
- Tracer bulletestablished
A thin slice all the way through, not a layer that goes nowhere alone.
- Issue-as-specemerging
The work item's body is the spec. Ready means a stranger could take it.
- Laneemerging
One session, one workspace, one branch, exactly one work item.
- Teammate (agent teams)emerging
The vendor word for a lane, with the mechanics shipped. Guidance is three to five.
- Claim (read-before-write)emerging
Record ownership before touching anything, in a form a machine can read.
- Orchestratoremerging
Routes work, audits results, owns integration, never implements.
- Worktree isolationestablished
Separate directories over one object store. Not a security boundary.
Handing off
Getting a session's state out of a window and into something that outlives it.
2 termsVerification and authority
Telling done from claimed-done, and naming who decides when the two disagree.
8 terms- Verification gateestablished
A check the model cannot argue past, because the harness enforces it.
- Oracleestablished
An independent source of truth about correctness. Its presence predicts more than topology.
- Self-reported greenestablished
A claim that verification passed, offered instead of evidence. Re-run it.
- LLM-as-judgeestablished
A model grading a model. Standard, biased, and worst exactly when candidates are close.
- Adversarial reviewemerging
Several reviewers with different lenses, rather than one working sequentially.
- Echo riskemerging
Agreement between models is not automatically evidence.
- Couldn't-verifyemerging
An explicit bucket for what a review leaned on but did not check.
- The decideremerging
The named person who adjudicates. Always asked, never inferred.
Unsurveyed water
Terms in motion. Some name real practice, some name a naming event. The band says which.
5 terms- Graph engineeringthin
A 2026 name for task-graph orchestration. The patterns predate it by 19 months.
- Loop engineeringemerging
Designing the system that prompts the agent, instead of prompting it yourself.
- Agentic engineeringemerging
Directing fallible agents under human oversight. Automates what you can verify.
- Code knowledge graphemerging
Index the repo as symbols and relationships. Building it is the easy half.
- Spec-driven developmentemerging
Write the spec first and generate from it. Real tooling; oversold as executable.