Skip to content

This page defines the shared naming model used across the repository so runtime does not mean both “the execution system” and “the thing being executed.”

Short version:

Agent Engine runs an Agent Runtime and extends it with Agent Spec.

If you want the system map that shows how these concepts fit together, continue with:

TermRoleMeaning
Agent EngineExecution systemLoads, schedules, executes, recovers, audits, and exposes API / SSE.
Agent RuntimePrimary runnable unitA runnable unit that carries agent / action / hook definitions. Formerly called blueprint.
Agent SpecUser extension layerExtra user-authored inputs layered onto a runtime, mainly AGENTS.md, .openharness/memory/MEMORY.md, and extra loaded model / tool / skill.
  • Engine: how it runs
  • Runtime: what runs
  • Spec: what the user adds

These concepts belong to Runtime and should not be renamed as another kind of spec:

  • agent definitions
  • action definitions
  • hook definitions
  • runtime-owned default behavior and capability composition
  • runnable units under runtimes/

Avoid:

  • agent spec
  • hook spec
  • runtime spec

Spec is not the whole runtime structure. It is the user-authored extension layer added on top of a runtime. It mainly includes:

  • project-root AGENTS.md
  • .openharness/memory/MEMORY.md and .openharness/memory/*.md topic files
  • extra loaded model
  • extra loaded tool
  • extra loaded skill

When the meaning is about execution flow rather than the primary runnable unit, prefer:

  • engine
  • run
  • session
  • execution
  • engine state

So use names like:

  • EngineLogger
  • engine.log
  • engine state paths