The concepts
Ten ideas the market is hiring for, in reading order. Each one is stated so it is useful anywhere, then shown working in one orchestrator, then costed. Read them in order or start where your problem is.
- Concept 1Agentic engineering
The engineering is not in the agent. It is in the loop around it.
- Concept 2Multi-agent orchestration
The plural is in the roles, not in the fleet.
- Concept 3Context engineering
Deciding what an agent is allowed to know, and paying for it.
- Concept 4Token economics and context budgets
A session's cost is not its length. It is roughly its length squared, and that changes every decision about it.
- Concept 5Evals, gates and acceptance
A gate is a command and an exit code. Everything else is an opinion with a schedule.
- Concept 6Independent verification
The thing that checks cannot be the thing that did it, and a prompt is not a separation.
- Concept 7Durable execution and resumability
If the work is longer than the thing doing it, the work has to live somewhere the worker does not.
- Concept 8Human in the loop
Oversight is not somebody watching. It is a place the machine stops, one that names what it is waiting for and exactly what clears it.
- Concept 9Agent observability
The question is not whether it is logging. It is whether you can ask something nobody planned for and get an answer.
- Concept 10Agent memory
Everything a session works out dies with it unless something writes it down, and everything written down is paid for by every session after it.