Architecture

The application owns configuration, credentials, storage, and deployment. Forge libraries supply contracts and reusable execution components.

Request path

Application input
  -> model messages and generation options
  -> concrete language model
  -> model output or proposed tool calls
  -> schema validation, capability policy, approval
  -> tool executor
  -> correlated result messages
  -> next model step or final output

Core defines shared types. Generation wraps model operations. Tools define and execute operations. Agents combine them with bounded loops, workflows and lifecycle state.

Authority and observation

Identity binds a principal. Auth expresses and checks capability scopes. Telemetry records spans and audit information. They are separate concerns: carrying an identity does not grant authority, and a telemetry event does not prove a remote action succeeded.

Integration boundaries

The SDK aggregate re-exports selected crates. Extended runtimes and provider adapters remain separate libraries, with feature and target restrictions in their manifests. The six language SDKs implement related contracts but differ in lifecycle APIs, defaults and available adapters. Use the language-specific references.

Release status

ANVIL defines expectations. Conformance fixtures define test inputs. A passing build, a generated source index, and a deployed runtime are separate evidence. This documentation release does not certify an on-chain agent deployment or all-language conformance.