No description
  • Go 98.7%
  • Python 1.3%
Find a file
Repository files (latest commit first)
Filename Latest commit message Latest commit date
2026-05-25 23:03:01 -05:00
docs llm: use ollama openai embeddings endpoint 2026-05-25 22:24:57 -05:00
public Initialize agent-llm scaffold 2026-05-07 01:25:46 -05:00
scripts workflow: add checked manifest baseline 2026-05-13 21:16:26 -05:00
src llm: cover ollama embedding index mapping 2026-05-25 23:00:50 -05:00
templates Initialize agent-llm scaffold 2026-05-07 01:25:46 -05:00
workflow docs: clarify registry embed boundary 2026-05-25 23:03:01 -05:00
.gitignore workflow: decompose llm runtime features 2026-05-24 13:38:09 -05:00
go.mod cmd/agent-llm: serve substrate plugin lifecycle 2026-05-24 19:57:14 -05:00
go.sum cmd/agent-llm: serve substrate plugin lifecycle 2026-05-24 19:57:14 -05:00
README.md cmd/agent-llm: serve substrate plugin lifecycle 2026-05-24 19:57:14 -05:00
workflow.events.jsonl workflow: complete llm emitted tools ingestion 2026-05-24 15:35:43 -05:00
workflow.toml llm: add ollama embedding adapter 2026-05-25 22:10:05 -05:00

agent-llm

agent-llm is the LLM/model provider plugin for the agent system.

It talks to model providers and returns structured planning/model outputs. It does not own action authority.

Purpose

agent-llm owns model-provider integration:

  • provider API adapters such as OpenAI, Anthropic, local model gateways, or future model services
  • prompt/message formatting
  • response parsing
  • model/tool-call normalization into planning results
  • token/accounting metadata
  • provider retry/rate-limit behavior
  • model streaming transport, when supported
  • provider-specific errors and degradation behavior

Authority boundaries

agent-llm is not the action authority and not the credential authority.

  • agent-core-system owns action admission, approval, policy, audit, and execution envelopes.
  • rpc-plugin-system owns substrate runtime, transport, lifecycle, and plugin supervision.
  • agent-keyring owns model-provider credentials, API keys, OAuth/OIDC, service credentials, scoped leases, refresh, rotation, revocation, and credential audit metadata.
  • agent-network may own generic HTTP/transport adapters if that layer is used.
  • agent-llm owns model-provider semantics and model response normalization.

Model output is proposer data. Returned candidates remain untrusted until agent-core-system admits them.

LLM session model

agent-llm may own provider-native model session mechanics:

  • provider conversation/thread/response ids
  • model cache/session handles
  • streaming ids
  • provider-specific message context
  • token/accounting continuity

These are implementation details. agent-core-system owns canonical agent task/session state. Provider-native LLM session ids must be exposed to core only as opaque references when needed.

agent-keyring owns credential/session secrets, not model conversation state.

Non-goals

  • Do not store model API keys here.
  • Do not bypass agent-core-system admission.
  • Do not execute tools or provider operations directly.
  • Do not mint approval grants.
  • Do not treat model tool calls as executable authority.
  • Do not leak credentials into prompts, logs, responses, candidate payloads, or workflow evidence.

Current implementation status

The V1 runtime implements:

  • llm.plan request/response/candidate contracts and fail-closed validation
  • redaction, audit-safe accounting, fake authority mediation, provider sessions, streaming, retry/rate-limit handling
  • deterministic fake provider, CLI smoke wiring, and rpc-plugin-system substrate lifecycle service
  • OpenAI-compatible adapter behind mediated credential/network seams, with fake transport tests only
  • core-emitted tool/capability ingestion as bounded context packets, not executable authority

Verify the repo with:

python3 scripts/workflow-check.py
git diff --check
go test ./...
go test -cover ./...
go build ./...
go vet ./...