Skip to content

Specification · RFC

RFC-0008: Agent Plugin Distribution

Version: 0.4.0 | Status: normative | Phase: test Owners: @Zihua Wu


[RFC-0008:C-SUMMARY] Summary (Informative)

Section titled “[RFC-0008:C-SUMMARY] Summary (Informative) ”

This RFC governs distribution of the operator agent plugin: the repo-shipped plugin package and the CLI surface that installs, updates, uninstalls, and diagnoses it across supported agent runtimes. RFC-0001 holds the specification overview and the authority map.

Since: v0.1.0


[RFC-0008:C-AGENT-PLUGIN] Agent Plugin Distribution (Normative)

Section titled “[RFC-0008:C-AGENT-PLUGIN] Agent Plugin Distribution (Normative) ”

The public CLI MUST provide agent plugin install, update, uninstall, and doctor operations for the supported agent runtimes, operating on the plugin package shipped at the repository root (the per-runtime marketplace manifests and the package under plugins/inferlab/).

The shipped plugin package MUST carry the workspace-authoring reference set defined by RFC-0011:C-CONTENT-AUTHORITY. Its skill entry MUST link to the carried workspace-authoring.md index. The package MUST NOT carry an independently editable concatenated workspace-authoring copy.

Install MUST default to that package as carried by the running CLI binary, at the same version as the binary, without requiring the operator to supply a path or reach a network location. Install MUST also accept an explicit local checkout or unpacked release tarball path from the operator, and when given, MUST operate on that content instead of the carried package.

Install MUST validate the selected package’s required members before any native agent CLI is invoked, regardless of source. A required member that is missing, corrupted, or otherwise unreadable MUST fail the operation loudly, naming the runtime and the affected member.

Agent plugin operations MUST NOT read workspace facts, local bindings, or execution records, and MUST NOT write records.

Each agent plugin operation MUST emit exactly one machine-readable JSON report of the per-runtime outcomes and, per runtime, every native command it ran in execution order — readiness probes included. An operation that fails before, during, or after native commands MUST still emit the report ahead of its loud non-zero exit, carrying the failure on the affected runtime’s row; a runtime not attempted because a preceding gate failed MUST appear with a skipped outcome.

Rationale: Distribution tooling parallels the measurement-toolchain surface (RFC-0004:C-INFERLAB-TOOLCHAIN): the CLI owns installing what it ships. Carrying the same task-focused authoring authority used by the public documentation keeps an installed version self-contained without introducing an aggregate copy. Defaulting to the package the binary carries removes the checkout requirement the original design left standing and keeps the CLI and the plugin it installs at the same version by construction; the explicit override remains for operators validating a package the binary doesn’t yet carry. Validating the package before driving a native CLI turns a broken source into a precise error instead of a half-configured agent, whichever source is in use, and the isolation requirement keeps the experiment contract untouched by distribution concerns; the accompanying architecture decision records why this shape won.

Since: v0.1.0