Files

T

steve dcd004289f feat: foundations — canonical types, Parse grammar, env DSNs, health, chains

Phase 1 of the majordomo build:
- llm/ canonical contract (messages, parts, tools, capabilities, streaming,
  Model/Provider, error classification)
- health/ clock-injected tracker (threshold bench, exponential capped
  cooldown, reset-on-success)
- root Registry + Parse (verbatim model ids, inline recursive alias
  expansion with cycle detection, chain dedup), LLM_* env-DSN providers
  (go-llm parity: lazy fallback + eager LoadEnv), health-aware chain
  executor behind the Model interface
- provider/fake scriptable test provider; hermetic test suite incl. the
  trailing-thinking chain and foreman:// env loading
- ADRs 0001-0008, CLAUDE.md, README (honest matrix), CI workflow,
  docs/phase-1-design.md

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

2026-06-10 12:35:34 +02:00

1.7 KiB

Raw Permalink Blame History

ADR-0005: Provider interface and the capabilities model

Status: Accepted — 2026-06-10

Context

Each provider — and some individual models — imposes different limits (image dimensions/bytes/MIME/count, tools, structured output, streaming, context size). Callers must not need to know them; the library must normalize or clearly reject.

Decision

Provider is minimal: Name() and Model(id, opts...) (Model, error). Model ids pass through verbatim; providers never validate ids against a catalog (models churn weekly; catalogs rot).
Capabilities is a plain struct declared per provider with per-model overrides via WithCapabilities (a ModelOption). Zero values mean: MaxImagesPerReq == 0 → images unsupported; MaxImageBytes/MaxImageDimension/ContextWindow == 0 → no declared limit; empty AllowedImageMIME → any type.
Providers construct without error even when credentials are missing; the failure surfaces as an auth error at request time (and a chain can fail over past it). Construction-time validation would make New() fragile.
Until a provider's implementation phase lands, built-ins register as stubs: they resolve in Parse (so chains, aliases, and env DSNs are fully functional) and return a clear "not implemented yet" error on use.

Consequences

The media pipeline (Phase 3, ADR to follow) can normalize against any target uniformly.
Adding a provider is additive: implement two methods + declare capabilities.

Alternatives considered

Capability methods on Model with provider-specific logic — pushes limits knowledge into every caller. Rejected.
Model catalogs with validation — stale within weeks, breaks pass-through targets like foreman. Rejected.

1.7 KiB Raw Permalink Blame History