Follow the activation lifecycle

Vector calls the pinned host’s agent.list() operation and maps its location into cwd and project.

When the builder declares runtimeConfig, Vector reads global then project JSON, merges the values, and validates the result once with the supplied Standard Schema. Without that option, it skips file discovery and supplies an empty Runtime Configuration object.

A builder with computeContext calls it once with the base location fields, then adds the returned properties to the Context shared by bound callbacks.

Vector calls the captured configuration build(context) callback. The callback selects reusable Extension Definitions and supported defaults.

Every selected Extension Definition other than an External Skill builds with the same Context. External Skill descriptors and ordered Instruction File sources remain in an internal candidate form.

Vector canonicalizes and reads each selected Instruction File once. A failure stops activation before any host transform registration.

Vector resolves Local Skills from canonical directories and Managed Skills from the shared user cache or their remote sources. A failure stops activation before any host transform registration.

Vector checks duplicate identities and required relationships across the complete concrete Snapshot before registration.

Vector always invokes agent.transform. That transform applies Vector Agent Definitions, appends Global Instructions to every returned agent system, and selects the default agent in that order. Vector registers each remaining host domain sequentially only when that domain has selected extensions or an applicable default.